When Google Drive sync stalls, restart the desktop app, free storage, and remove network or filename limits to resume updates.
If your desktop client stops updating files, don’t panic. Sync hiccups usually come down to one of five buckets: storage limits, app glitches, connection rules, file naming or path length, and account scope. This guide gives you fast checks first, then deeper fixes for Windows and macOS, with a clean layout you can follow step by step.
Google Drive Sync Not Working — Quick Checks
Start with the basics. These take a minute and resolve a large share of stuck queues without touching advanced settings.
- Confirm the desktop client is running. On Windows, look for the Drive icon in the taskbar corner. On macOS, check the menu bar. If missing, launch “Google Drive” from the Start menu or Applications.
- Pause and resume. Open the Drive menu → click the gear → Pause syncing. Wait 10 seconds, then Resume.
- Quit and relaunch. Use the gear → Quit. Reopen the app. This flushes a stuck worker without changing data.
- Reboot your device. A fresh network stack and file handles often clear the logjam.
- Check Google’s status page. If Drive has a service issue, local tweaks won’t help. See the Workspace status dashboard for real-time notices.
Fast Diagnostic Map
Use this table to match the symptom you see with the likeliest cause and a quick action. It’s a broad view so you can jump to the right fix fast.
| Symptom | Probable Cause | Fast Fix |
|---|---|---|
| “Syncing…” never finishes | Hung process or cache issue | Pause/Resume → Quit/Reopen → Reboot |
| Uploads fail at 100% | Out of cloud storage | Delete large items or buy storage; empty Trash |
| Some folders won’t update | Folder not selected for syncing | Drive menu → Preferences → check folder scope |
| Works on Wi-Fi A, fails on Wi-Fi B | Firewall/proxy rules | Allowlisted domains/ports per admin guidelines |
| Only certain files fail | Names, path length, or file locks | Shorten paths, remove banned characters, close apps |
| Mac laptop syncs; desktop doesn’t | Account mismatch | Sign out/in; verify the same Google account |
| Frequent “conflict copy” items | Edits on multiple devices at once | Set a single source of truth; merge then re-sync |
| Sync halts during large moves | Cache pressure or bandwidth cap | Let the batch finish; avoid sleep; lift caps if set |
Fix Storage Roadblocks First
Drive, Gmail, and Photos share one pool. When the pool is full, uploads stop. Head to Google One to see what’s eating space, remove bulk items, and empty Trash. Details on pooled space and clean-up tools are documented here: Manage your storage in Drive, Gmail & Photos.
- Open Storage manager. Sort by size and remove obvious giants first.
- Empty Trash in Drive and Photos. Items sit in Trash until purged; they still count toward your cap.
- Large email attachments. In Gmail, search
has:attachment larger:10m, delete, then empty Trash.
Restart, Update, And Reset The App
When storage isn’t the issue, the desktop client may need a refresh.
Soft Reset Steps
- Quit the client from the menu, reopen it, then wait for re-scan.
- Sign out/in. From the gear → Preferences → Accounts → Disconnect, then sign back in. This repairs token issues without removing files online.
- Update the app. The client self-updates, but a stale build can linger after long sleeps. Download the latest installer from Google and run it over the top.
Refresh The Content Cache
The client maintains a local content cache for streaming and quick access. On Windows and older macOS versions, cache behavior and location can be tuned; newer macOS versions manage the cache at the system level. See Google’s “Advanced Drive for desktop configuration” for cache location, bandwidth, and proxy flags, which admins can set via plist/registry keys. These options are described in Google’s admin article on advanced configuration.
Check Folder Scope And Sync Settings
The desktop app can stream everything from the cloud or mirror selected folders. If a folder isn’t in scope, it won’t update.
- Drive menu → Preferences.
- On My Drive, confirm the folders you need are selected.
- On Computers, confirm the local folders you back up are present and not paused.
- If you recently renamed a top-level folder, re-select it so the app tracks the new path.
Network Rules That Block Sync
Corporate or school networks may route traffic through proxies or filter outbound hosts. Drive for desktop encrypts traffic and validates host certificates, so a decrypting proxy must present a trusted cert file. Admin guidance lists the discovery methods and settings for proxies and firewall rules.
What To Do
- Test on a mobile hotspot. If sync works there, the issue sits with the network.
- Ask your admin to allowlist Drive endpoints and ports per Google’s firewall/proxy documentation.
- Using a decrypting proxy? Configure the trusted root certificate for the Drive client so TLS checks pass.
File Names, Path Lengths, And Locks
Long or unusual paths can stop a single file and leave the rest waiting. Windows still has legacy path length behaviors in some tools, and certain characters don’t sync cleanly across platforms.
Shorten Long Paths On Windows
Modern Windows versions can lift the old 260-character ceiling for many apps, but the feature must be enabled, and some software still expects the shorter limit. Microsoft documents the long-path behavior and the “Enable Win32 long paths” policy on its site. If you handle deep folder trees, shorten names or flatten structure to stay clear of limits.
Remove Problem Characters
Avoid reserved names and special characters that differ between Windows and macOS. Keep names simple: letters, numbers, spaces, dashes, and underscores. If a file refuses to upload, rename it locally, then retry.
Close Apps That Hold Locks
Editors can keep a file handle open, which prevents upload. Quit the editor, wait a few seconds, then watch the queue move.
Deep Troubleshooting Steps
If you’ve made it here, the basics weren’t enough. Work through these in order.
1) Verify Service Health
Check the Workspace status dashboard again. If Drive shows a disruption or outage, let it clear first.
2) Rebuild Local Index
- Quit the client.
- Restart the computer to release file handles.
- Launch the client and give it time to rescan. Large libraries can take a while to hash.
3) Repair Account Link
- Open the Drive menu → gear → Preferences.
- Select your account → Disconnect.
- Sign back in, pick Stream files (safer for disk space), and re-select folders if needed.
4) Tweak Bandwidth Caps
If someone set upload/download limits, large jobs will crawl. Lift caps temporarily while you catch up, then reapply gentle limits if you share a tight link.
5) Review Firewall/Proxy Rules
Ask your admin to compare current rules with Google’s guidance for Drive and Docs endpoints and ports. Mis-scoped TLS inspection also blocks sync. A quick A/B test on a hotspot can prove the point in seconds.
6) Re-install The Client
Download the latest installer and run it. This repairs corrupted binaries and re-registers services without touching cloud data.
Limits That Commonly Block Sync
These caps and behaviors trip users every day. If a file sticks, check against this list.
| Limit Or Rule | Typical Value/Behavior | Fix Or Workaround |
|---|---|---|
| Storage pool full | Shared across Drive, Gmail, Photos | Clean up via Google One; empty Trash |
| Windows path length | Legacy 260-char paths in some tools | Shorten paths or enable long-path policy |
| File open locks | Editors or preview apps hold handles | Close the app; wait; retry |
| Unsupported characters | Reserved names and symbols vary by OS | Rename with simple ASCII set |
| Firewall/proxy filter | TLS inspection blocks Drive traffic | Allowlist Drive endpoints; set trusted cert |
| Bandwidth cap | Upload/download limited by user/admin | Lift caps during bulk jobs |
| Paused backup set | Local “Computers” folders paused | Resume per-folder backup |
Windows And Mac Playbooks
Windows
- Enable long paths (when needed). On Pro/Enterprise editions you can enable the “Enable Win32 long paths” policy. Some tools still expect short paths, so trimming folder depth is the safest move for shared projects.
- Check antivirus exclusions. Real-time scanners can hold files open. Temporarily disable scanning for your streaming mount to test, then add a safe exclusion if needed.
- Time and date. Wrong system time breaks secure handshakes. Sync the clock with an internet time source.
macOS
- Grant Full Disk Access. System Settings → Privacy & Security → Full Disk Access → add Google Drive. This helps with Desktop/Documents access and locked items.
- Spotlight reindex. If search results don’t match cloud content, rebuild Spotlight for the mounted drive.
- File provider extension. Keep macOS updated; Drive relies on Apple’s File Provider for streaming mounts.
Clean Naming And Folder Design
A few simple habits save hours later:
- Keep names short. Use human-readable slugs like
Q4-report-2025.xlsx. - Avoid reserved items. Skip
CON,PRN, and similar names on Windows. - Flatten deep trees. Replace nested
Team/Client/Project/Phase/Assets/Final/Versions/2025/Readywith a shallow design and tags inside filenames. - Stable top-level folders. Renaming a root while syncing causes re-scan storms. Rename during a quiet window.
Account And Permission Snags
Some items won’t sync because your account can’t see or edit them.
- Shared drives vs. My Drive. Confirm the item lives where your account has access.
- “View only” shares. You can stream but not upload edits. Request edit access or make a copy to your own space.
- Ownership changes. If a file moved to a shared drive, the owner becomes the drive; your local mirror may need a refresh after the move.
When You Need Admin-Level Tweaks
Large teams often run into caps set for bandwidth or cache. Admins can change cache location, mount points, and proxy behavior with plist/registry configuration. That includes setting a trusted root certificate when a decrypting proxy inspects TLS, and defining bandwidth ceilings for busy links. These controls keep sync stable during heavy use.
Final Checklist Before You Escalate
- Storage pool has headroom; Trash emptied.
- Service health is green on the Workspace dashboard.
- Drive client relaunched; sign out/in completed.
- Folder scope reviewed; paused sets resumed.
- Path lengths trimmed; names cleaned.
- Firewall/proxy tested by hotspot; rules updated if needed.
- Bandwidth caps lifted until the queue clears.
Why These Steps Work
The desktop client streams and caches content, checks file hashes, and negotiates secure sessions. Storage limits stop uploads outright. Bad paths and locks halt single items but jam the queue behind them. Proxies that rewrite TLS block sessions completely. The steps above remove each choke point in a logical order: simple resets, capacity, scope, naming, then network rules. That order saves time and avoids risky moves.
Helpful References
- Google’s pooled storage rules and clean-up tools: Manage your storage in Drive, Gmail & Photos.
- Live service health: Workspace status dashboard.