![Google Drive Not Syncing? 12 Ways to Fix Stuck Files [2026]](/images/blog/google-drive-not-syncing-fix-hero.webp)
You dragged a file into Google Drive an hour ago, the little spinning cloud icon is still going, and your colleague on the other laptop still can't see it. Google Drive not syncing is one of the most common cloud-support tickets we get at IT Cares — and after digging through hundreds of these cases, one thing stands out: it's almost never a Google outage. Looking back over our own support tickets tagged "Google Drive not syncing" in the past year, well over half traced back to two very boring, very fixable causes — a Google Account storage quota that quietly filled up (usually from Gmail attachments or Google Photos, not the files you were trying to sync) and a file or folder name containing a character Drive silently refuses to sync. The rest were split between oversized files, antivirus software interfering with the sync process, and a local sync cache that had simply gotten confused.
This guide covers all 12 fixes, ranked from fastest to most involved: the ones you can try in under a minute (pause/resume, checking your storage quota) before the ones that require more patience (switching sync modes, reconnecting your account, or forcing a full local resync). It applies to Google Drive for desktop — the official sync client that replaced the old "Backup and Sync" app — on both macOS and Windows. If you manage Drive for a small team or business, the filename and permission fixes in particular are worth bookmarking, since they're the ones that come back again and again.
What makes Google Drive sync problems particularly frustrating is how quietly they fail. Unlike a crashed application or a blue screen, a stuck sync rarely throws up a loud, obvious error message. Instead you get a small, easy-to-miss badge on a file icon, or a spinning cloud that simply never resolves into a checkmark. Multiply that across a shared team folder with dozens of contributors, and you get the classic support call: "half my files are here, half aren't, and nobody knows why." The good news is that Drive for desktop keeps enough local diagnostic information — sync status per file, account storage data, and connection logs — that almost every case can be traced to one of the twelve causes below without needing to contact Google support directly.
Where to find Google Drive for desktop's settings
Every fix in this guide starts from the same place: click the Google Drive icon in your Mac menu bar (top right) or Windows system tray (bottom right, you may need to click the small up-arrow "^" to reveal hidden icons). In the popup that appears, click the small gear/Settings icon in the top right corner. From there you can pause syncing, open Preferences, disconnect your account, or quit the app entirely — every fix below refers back to this menu.
What the Drive Icons Actually Mean
Before troubleshooting, it helps to know exactly what you're looking at. Google Drive for desktop shows a small badge on every synced file's icon in Finder or File Explorer, and a different icon in the menu bar/tray itself:
| Icon / Status | What It Means | Action Needed |
|---|---|---|
| Green checkmark | File is fully synced and up to date | None — this is normal |
| Spinning gray/blue arrows ("sync pending") | Actively uploading or downloading, or genuinely stuck | Wait 5-10 minutes for large files; if unchanged, start with Fix 1 |
| Red exclamation mark | A sync error on that specific file | Usually a filename, size, or permission problem — see Fixes 4, 5, or 10 |
| Grey cloud with a slash through it | File exists locally but hasn't been uploaded to Drive yet | Check your internet connection and pause/resume sync |
A spinning "sync pending" icon isn't automatically a problem — Google Drive genuinely does take time to sync large files or folders with thousands of small files. The rest of this guide is about telling that apart from a sync that's actually stuck.
It's also worth knowing where these badges show up. On macOS, they appear as small overlay icons in the bottom-right corner of each file's thumbnail in Finder, inside your Google Drive folder (found under Locations in the Finder sidebar, or wherever you've mounted it). On Windows, the same overlay badges appear in File Explorer under the "Google Drive" entry in the left-hand navigation pane. If you don't see any badge at all on a file — not even a checkmark — that usually means the file hasn't been picked up by Drive's watcher yet, which points back to Fix 1 or Fix 7 below.
Can't fix it yourself? Skip the trial-and-error.
Our certified bilingual tech remotes in, reads your system logs, and resolves it on the spot — same day, from $119.99. No fix, no fee.
12 Fixes for Google Drive Not Syncing
Pause and Resume Syncing (Soft Reset)
Click the Google Drive icon in your menu bar (Mac) or system tray (Windows), click the gear/Settings icon in the top right of the popup, and choose Pause syncing. Wait about 30 seconds, then open the same menu and choose Resume syncing. This forces Drive for desktop to re-scan every watched folder from scratch and re-queue anything it had silently given up on — it's the equivalent of a soft reset and, in our support tickets, resolves roughly a third of "stuck sync" complaints on its own, in under a minute, with no data loss. Nothing about this step touches your actual files, whether they're stored locally or in the cloud — it only resets the background process that watches for changes, so there's no risk in trying it first, every time, before anything else on this list.
Check Your Google Account Storage Quota
Open one.google.com/storage (or drive.google.com and click the storage meter in the bottom-left corner) in a browser. Google's free tier gives you 15GB shared across Gmail, Google Photos, and Drive — and it's very common for Gmail attachments or backed-up photos to quietly eat most of that quota without you noticing. When your account storage is completely full, Drive for desktop does not always show a clear "storage full" error; it often just shows files stuck on sync pending indefinitely. If you're over quota, delete large Gmail attachments, empty your Gmail Trash and Spam folders, or upgrade to a Google One plan. Google One plans start at 100GB and scale up to multiple terabytes, and for a household or small office juggling photos, email, and shared documents, moving up even one tier is often cheaper than the time lost troubleshooting a "phantom" sync failure that was really just a full account.
Confirm Your Internet Connection Is Actually Stable
Open a new browser tab and load drive.google.com directly. If it loads slowly or times out, the problem is your connection, not Drive for desktop. On unstable Wi-Fi, large uploads can silently drop partway through and re-queue themselves, which looks identical to a "stuck" sync. If you're on a VPN or corporate network, try temporarily disconnecting it — some VPN configurations block or heavily throttle Google's sync endpoints. If you have a phone nearby, switching it to mobile data and loading drive.google.com there is a quick way to confirm whether the problem is with Google's service in general (rare) or specific to the network your computer is on (much more common) — a five-second test that saves a lot of guesswork.
Rename Files With Unsupported Characters
Google Drive for desktop cannot sync filenames or folder names that contain any of the following characters: / \ < > : " | ? *. Files copied from older Windows shares or macOS systems sometimes carry these characters (a colon in a timestamp, a question mark in a scanned document title) without anyone noticing until sync silently fails on that one file. Look for files showing the red exclamation-mark badge, right-click, rename, and remove any of the characters above — the file will typically start syncing again within seconds. Businesses that regularly exchange files with Windows servers or older document-management systems are especially prone to this, since those systems are often more permissive about which characters they allow in a filename than Google Drive is — worth setting a simple naming convention team-wide to avoid repeat cases.
Check for Oversized Files
Google Drive supports individual files up to 5TB for most file types via desktop sync, but that limit is smaller for some Google Workspace file types, and any file that hits the ceiling will show the error "This item is too large to sync." This is rare for everyday documents but common for exported video files, large database dumps, or disk-image backups accidentally saved into a synced folder. Move oversized files out of your Drive folder (onto external storage or a dedicated backup solution) and Drive will stop retrying them. If you genuinely need to share a very large file, splitting it into smaller archive parts, or uploading it directly through the Drive web interface (which handles some large-file scenarios differently than the desktop sync client), can work around the limit without needing a separate backup tool.
Switch Sync Mode: Stream Files vs. Mirror Files
Open the Drive icon > gear icon > Preferences, then go to the Settings tab. Google Drive for desktop offers two modes: Stream files downloads a file to your computer only when you open it, saving local disk space, while Mirror files keeps a complete, always-available local copy that stays in sync in both directions. If your sync is stuck in Stream mode, switching to Mirror files (or vice versa) forces the app to fully re-evaluate every single file against the cloud copy, which frequently clears sync jobs that were quietly stalled. Note that Mirror files needs enough free local disk space to hold a full copy of everything in your Drive — check your available storage first if your Drive account holds hundreds of gigabytes and your laptop has a smaller SSD, since Stream files is usually the better long-term choice on space-constrained machines, with Mirror files reserved as a one-time troubleshooting toggle rather than a permanent setting.
Fully Quit and Relaunch Google Drive for Desktop
On Mac: click the Drive icon > gear icon > Quit Google Drive, then relaunch it from Applications or Spotlight (Cmd+Space, type "Google Drive"). On Windows: right-click the tray icon and choose Quit, then relaunch it from the Start menu. This goes further than pause/resume — it fully closes the background sync process and re-establishes the connection to Google's servers from a clean state, which resolves cases where the app itself has become unresponsive rather than just a specific file being stuck. If you check Activity Monitor (Mac) or Task Manager (Windows) after quitting and still see a Google Drive-related process running, end it manually before relaunching — occasionally the background sync helper process lingers a few seconds after the menu-bar icon disappears.
Check Whether Antivirus or Firewall Software Is Blocking Sync
The actual sync process on Windows runs as GoogleDriveFS.exe, and some antivirus or endpoint-security software — particularly business-grade EDR tools — flags or throttles this process because it constantly reads and writes large numbers of files, which superficially resembles ransomware behavior. Check your antivirus's activity log or blocked-items list for GoogleDriveFS.exe, and add an exclusion for it and for the Google Drive installation folder if you find it there. On managed business networks, this is also worth checking with your IT administrator, since a firewall rule at the network level can silently throttle sync traffic for every user. As a diagnostic step, temporarily disabling third-party antivirus (built-in Windows Defender can usually stay on) for a few minutes and watching whether sync activity resumes is a quick, low-risk way to confirm whether security software is the culprit before you go looking for the right exclusion setting.
Fix Windows "File Name Too Long" / Path-Length Errors
Windows has historically limited full file paths to 260 characters (some organizations enable extended/long-path support, raising the effective limit to around 400 characters, but it isn't on by default everywhere). Deeply nested folder structures — especially ones copied from SharePoint or a mapped network drive — can easily exceed this, causing Drive to fail silently on those specific files with a "file name too long" style error. Shorten folder names, flatten deeply nested subfolders, or move the affected files closer to the root of your synced folder to get them under the limit. On Windows 10 and 11, IT administrators can also enable long-path support system-wide through Group Policy or a registry change, which raises the ceiling well beyond 260 characters — a more permanent fix for organizations that regularly work with deeply nested project folders.
Resolve "Sync Issue – Insufficient Permission" Errors
This specific error means Drive can see that a shared file or folder exists but is blocked from syncing your changes to it — usually because it was shared with you as view-only when you tried to edit it, or because the owner has since revoked or downgraded your access. Open the file directly at drive.google.com in a browser; if you no longer have access, you'll see a "Request access" prompt. Send that request to the folder owner and ask them to restore the permission level you need. Once access is corrected, the sync error clears automatically without needing to touch the desktop app. This is especially common with Shared drives in a Google Workspace business account, where individual folder-level permissions can differ from the overall Shared drive membership — double-check both levels if a single subfolder is the only thing failing to sync while everything around it works fine.
Disconnect and Reconnect Your Google Account
Open Drive icon > gear icon > Preferences > Settings tab (or click your account icon/avatar), then choose Disconnect account. Relaunch Google Drive for desktop and sign back in with your Google credentials. This forces a full re-authentication and clears out expired or corrupted authentication tokens — a common cause of syncs that fail silently in the background without any visible error message, particularly after a Google password change or a security-related sign-out on other devices. Authentication tokens can also expire after long periods of inactivity, or if your organization's Google Workspace administrator has changed session-length or two-factor authentication policies — a reconnect resolves all of these scenarios the same way.
Delete the Local DriveFS Folder to Force a Full Resync (Last Resort)
Quit Google Drive completely first (Fix 7). Then delete the local sync cache folder: on macOS it's at ~/Library/Application Support/Google/DriveFS, and on Windows it's at %USERPROFILE%\AppData\Local\Google\DriveFS. This folder holds only local sync metadata and cached copies — none of your actual files, which remain safely stored on Google's servers. Relaunch Drive for desktop afterward and it will rebuild its entire local index from scratch, re-downloading or re-verifying every file against the cloud. This is the most effective fix for a corrupted local sync database, but it can take a long time to complete on a large Drive, so reserve it for when Fixes 1-11 haven't worked. Before you start, confirm you have enough free local disk space to accommodate the resync, especially if you're using Mirror files mode — running out of space mid-rebuild will simply leave you with a second stuck sync on top of the first.
Before you delete the DriveFS folder
Deleting the DriveFS folder is safe for your cloud data — your files live on Google's servers, not in that cache — but if you're on Mirror files mode with a large amount of content, the full re-download can take hours and use significant bandwidth. Do this on a stable, unmetered connection, and expect the Drive icon to show heavy sync activity for a while afterward. Do not interrupt the process or delete the newly recreated DriveFS folder again mid-resync.
Why "Sync Pending" Doesn't Always Mean Something Is Broken
A lot of the panic around Google Drive not syncing comes from misreading a slow-but-working sync as a stuck one. If you've just moved a folder with several thousand small files, or a handful of large video exports, into your Drive folder, the spinning "sync pending" icon can legitimately stay visible for a long time — Drive processes files individually, and each one needs to be hashed, uploaded, and confirmed against Google's servers before the icon updates. On a typical home internet connection, uploading 50GB of mixed files can realistically take several hours.
The genuine warning signs of a truly stuck sync are: the spinning icon hasn't moved past the same handful of files after 30+ minutes on a decent connection, the upload/download speed shown in the Drive activity panel has dropped to zero and stayed there, or specific files are showing the red exclamation-mark error badge rather than the neutral spinning-arrows icon. If you're seeing genuine no-progress rather than just slow progress, that's when it's time to work through the fixes above — starting with pause/resume, since it costs nothing to try and clears a meaningful share of cases on its own.
You can check upload and download progress directly: click the Drive icon in the menu bar or tray, and the popup window shows a live activity feed of exactly which files are currently transferring and at what stage. If that feed shows steady movement — even slow movement — through a long list of files, the sync is working, just taking its time. If the same one or two files sit at the top of that list without changing for a long stretch, that's your signal those specific files are the ones with a problem, which usually points to Fix 4 (unsupported characters) or Fix 5 (oversized file) rather than anything account-wide.
How to Prevent Google Drive Sync Problems Going Forward
Once you've cleared a stuck sync, a handful of habits keep it from happening again — especially useful advice to share across a household or small team that shares a Drive account or a set of Shared drives:
- Check your storage quota monthly. Set a calendar reminder to glance at one.google.com/storage, particularly if your account also handles Gmail and Google Photos. Catching a near-full quota before it hits 100% avoids a mystery sync failure later.
- Agree on a filename convention. Avoid colons, slashes, question marks, and asterisks in shared folder and file names — most of these show up from copy-pasting timestamps or titles from other software that's more permissive than Drive.
- Keep Google Drive for desktop updated. The app updates itself automatically in most cases, but if you've disabled automatic updates, check periodically — Google regularly ships fixes for exactly the kind of silent sync failures covered in this guide.
- Review sharing permissions when someone leaves a project. "Insufficient permission" errors spike whenever access is revoked from someone who still has files actively syncing — coordinate permission changes with anyone who might be mid-sync.
- Pick Stream or Mirror files deliberately, not by default. On a laptop with limited storage, Stream files avoids ever running low on disk space because of Drive content; on a desktop with plenty of storage and unreliable Wi-Fi, Mirror files means your files are available even when the connection drops.
Google Drive Still Won't Sync?
IT Cares offers remote cloud-sync troubleshooting for Google Drive, OneDrive, and Dropbox — for individuals and small businesses alike. Most sessions resolved same-day.
Frequently Asked Questions
Why is Google Drive stuck on "sync pending" and never finishing?
A spinning sync-pending icon that never resolves usually has one of five causes: your Google Account storage is full (check one.google.com/storage), a file or folder name contains a character Drive can't sync (/ \ < > : " | ? *), a single file exceeds Google's size limits for desktop sync, your antivirus or firewall is blocking the GoogleDriveFS.exe process, or the local sync database has become corrupted and needs to be rebuilt. Start with pause/resume, then work down the ranked list in this guide — most cases resolve in the first three fixes. If you manage sync for a shared team folder, also check whether the stuck files are concentrated around one specific contributor's uploads, since that's often a sign the problem is with that person's account (storage quota, permissions, or filename habits) rather than with Drive itself.
How do I force Google Drive to sync immediately?
There is no dedicated "sync now" button in Google Drive for desktop. The closest equivalent is: click the Drive icon, click the gear/Settings icon, choose "Pause syncing", wait about 30 seconds, then choose "Resume syncing". This forces the app to re-scan every watched folder and re-queue any files it had silently given up on. If that doesn't help, a full quit and relaunch of the app goes one step further and re-establishes the connection to Google's servers from scratch.
What's the difference between Stream files and Mirror files in Google Drive for desktop?
Stream files keeps most content in the cloud and only downloads a file to your computer the moment you open it, which saves local disk space but means you need an internet connection to access files you haven't opened recently. Mirror files keeps a complete, always-available local copy of your entire Drive that's kept in sync in both directions. You choose the mode in Preferences > Settings. Switching from one mode to the other forces Drive to fully re-evaluate every file, which frequently unsticks sync jobs that were stuck in Stream mode. Neither mode is objectively "better" — the right choice depends on your available local storage and how often you need offline access to files you haven't opened in a while.
Why does Google Drive show a "sync issue - insufficient permission" error?
This error means the file or folder was shared with you under restricted permissions (view-only when you tried to edit, for example) or the person who shared it has since revoked or changed your access. Google Drive for desktop can see that the item exists but is blocked from syncing changes to it. The fix is to open the file in a browser at drive.google.com, use the "Request access" prompt if you no longer have permission, and ask the folder owner to restore or grant the access level you need.
Will deleting the DriveFS folder delete my files from Google Drive?
No. The DriveFS folder (macOS: ~/Library/Application Support/Google/DriveFS, Windows: %USERPROFILE%\AppData\Local\Google\DriveFS) only contains local sync cache, database, and metadata — not your actual files, which live safely on Google's servers. Quitting Google Drive first and deleting this folder simply forces the app to rebuild its local index from scratch the next time it launches, re-downloading or re-verifying everything against the cloud copy. It can take a while to resync a large Drive, but no cloud-stored data is lost. If you're nervous about deleting the wrong folder, double-check the exact path first — renaming the folder instead of deleting it (adding "-old" to the end, for example) achieves the same reset while giving you a fallback copy until you've confirmed the rebuilt sync is working correctly.
Comments (3)
Had two client folders stuck on "sync pending" for over a day. I was ready to reinstall the whole app. Pause, wait 30 seconds, resume — both folders started moving again within a minute. Wish I'd tried that first instead of googling for an hour.
Never occurred to me that my Gmail was the reason Drive stopped syncing. Turns out years of email attachments had quietly filled my 15GB. Cleared out old attachments and everything I'd been trying to upload for a week finally went through. This should honestly be step 1 on every guide.
Our small office had a shared drive folder that just refused to sync properly on one machine, no matter what we tried. Deleted the DriveFS folder like this guide said and let it rebuild overnight — took about 3 hours for 40GB but came back completely clean. IT Cares walked me through it over the phone when I got nervous about deleting the wrong thing.
Leave a Comment