
The short version: Sync stuck at 99%, "conflicted copy" files piling up, and full-storage warnings almost always come down to three things: too many changes queued over too little bandwidth, a sync client that lost track of file state and needs a clean re-index, or storage genuinely full with no easy cleanup tools handy while you're away from your main computer. We fix the sync engine, set up selective sync so it stops choking your connection, and clean up duplicates without deleting anything you actually need.
Sync clients like Google Drive Desktop, Dropbox, and OneDrive are built assuming a fairly constant, reasonably fast connection. On hotel, hostel, or coworking WiFi with shared bandwidth, data caps, or frequent drop-outs, the client can lose track of its own "delta" changes, retry the same upload endlessly, or leave a file half-uploaded and stuck in limbo.
Switching networks several times a day, hotel WiFi in the morning, a café in the afternoon, a mobile hotspot in the evening, is completely normal for remote workers and digital nomads, but it's exactly the pattern these clients handle worst, since each switch can interrupt an in-progress sync cycle. Add in large files, photos, screen recordings, project exports, queued for backup, and a connection that can't keep up compounds the problem fast. None of this means your files are gone, it usually means the sync client's local state needs a reset, which we can do without touching the files themselves.
This is one of the most common tickets we see. Usual causes: one specific file with a character in its name the sync service can't handle, a file that's open or locked by another application, a corrupted local sync cache or database, or antivirus software scanning the sync folder and interfering with file handles mid-transfer.
The fix sequence is straightforward once you know what to look for: pause and resume the sync to clear a stuck retry loop, clear the local sync cache (every major service has a reset-sync or clear-cache option buried in settings), identify and rename or move the specific file that's blocking progress, and restart the client with logging enabled if the culprit isn't obvious. This is exactly the kind of thing that's slow and frustrating to self-diagnose over a shaky hotel connection, checking settings menus you've never opened, but fast for a technician watching your screen live who's seen the same three or four root causes dozens of times.
These pile up when the same file gets edited on two devices while one was offline, or when a sync interruption mid-upload causes the service to keep both versions rather than guess which one is correct. Dropbox names them something like "filename (conflicted copy from [device] [date]).ext", Google Drive appends a "(1)" suffix, and OneDrive tags the file with the device name it came from.
Prevention is mostly about discipline while traveling: know which device is your "master" copy at any given time, be careful with "keep on this device only" flags, and avoid editing the same file offline on two devices before either has synced. When conflicts have already piled up, the cleanup itself is the risky part to do alone, it's easy to delete the wrong version. A technician can compare file contents and timestamps side by side and merge or remove the extras safely, keeping the version you actually want.
A full-storage warning is a bad time to be downloading multi-gigabyte folders over slow hotel WiFi just to figure out what's safe to delete. The better approach is using each service's built-in storage manager, Google One's storage manager or Dropbox's "space used" breakdown, both let you see and remove large or old files directly from the cloud without downloading them first.
Beyond one-time cleanup, setting up selective sync keeps bulky folders like old photo backups or archived projects cloud-only so they stop filling your local disk. Automatic phone photo backup is usually the single biggest storage consumer while traveling, since every photo and video from a trip queues up automatically, and it's worth switching that to WiFi-only or scheduled uploads rather than letting it run constantly on a metered connection.
A few settings changes make a real difference on a slow connection. Set folders to sync only when on WiFi rather than over mobile data, exclude genuinely large folders (old Downloads, archived projects) from automatic sync entirely, and use the client's built-in bandwidth limit setting so sync doesn't eat 100% of a shared connection right when you're on a call.
Scheduling large syncs for overnight, when the connection is otherwise idle and no one else in the property is streaming, is a simple habit that avoids most day-to-day slowdowns. If sync keeps competing with your video calls specifically, that overlaps with bandwidth prioritization more broadly, see our video call setup guide for the router and app-level settings that stop the two from fighting over the same connection.
Shared drives and folders often break specifically for remote or international team members, and it's rarely obvious why from the error message alone. Common causes: domain-restricted sharing settings that quietly block external or personal accounts, permission inheritance breaking when a folder gets moved or reorganized, and company IT policies that restrict access by country for compliance reasons.
The fix starts with auditing the actual sharing settings rather than guessing, checking whether access was granted at the file, folder, or drive level, and whether it's tied to a specific account versus a link anyone can use. We'll also walk through the difference between "can view," "can comment," and "can edit" permissions, since a document unexpectedly opening as read-only is one of the most common, and most confusing, versions of this problem for distributed teams.
This distinction matters more than most people realize. Sync mirrors changes across your devices and the cloud in real time, including deletions and overwrites. If you accidentally delete or corrupt a file on one device, sync happily deletes or corrupts it everywhere else too, including the cloud copy. Most services keep a version history or trash bin, but it's time-limited, often around 30 days, after which the change is permanent.
Backup is a separate, deliberate practice: a one-way snapshot copy that doesn't automatically mirror deletions, built specifically for disaster recovery rather than convenience. Sync tools are great for keeping files accessible across devices, but they're not a substitute for an actual backup, especially before international travel, when the risk of a device being lost, stolen, or damaged goes up. See our pre-trip backup guide for setting up real backup alongside your existing sync.
Cloud sync problems are almost always faster to fix with someone looking at your actual screen than by guessing your way through settings menus over a slow connection. We'll diagnose the stuck file, clean up conflicts safely, and set up selective sync so it stops happening again.
We'll fix it live over screen-share, without deleting anything you didn't approve first.
Book a remote fix — $149.99No, our process is diagnose-first. We identify the specific stuck file or conflict before touching anything, and we always confirm with you before removing any duplicates.
Yes, we control your screen remotely at whatever bandwidth you have, and the diagnosis itself uses very little data even if your sync backlog is large.
No, and this trips up a lot of people. Sync mirrors changes both ways, including deletions; backup is a separate one-way snapshot for disaster recovery. See our backup vs. sync section above for the full explanation.
We can clean up cloud storage remotely from any device with a browser, using each service's built-in storage manager to find and remove large or old files without needing your original computer.
That's a sync conflict, usually caused by editing offline on two devices or an interrupted upload. We can identify which copy is current and safely merge or remove the extras.
Yes, we set bandwidth limits and scheduling in your sync client so large syncs don't compete with calls. See our video call setup guide for the full call-quality setup.