How to Clear Upload Queue and Cache in Google Drive for Desktop

Google Drive for Desktop is a powerful sync client — but like any background app, it accumulates temporary data, stalls on uploads, and occasionally gets stuck in ways that aren't obvious to fix. Whether you're dealing with a frozen upload queue, leftover cached files, or a sync that simply won't budge, understanding what's actually happening under the hood helps you clear the right thing the right way.

What "Clearing an Upload" Actually Means

When people search for how to clear uploads in Google Drive for Desktop, they're usually dealing with one of three distinct problems:

  • A stuck or pending upload that won't complete or won't cancel
  • Cached local data that the app stores temporarily during sync
  • Residual sync activity left behind after files were moved, deleted, or renamed

These aren't the same issue, and the fix for each is different. Lumping them together is why many users try the wrong step first.

How Google Drive for Desktop Handles Uploads

Google Drive for Desktop (the current app replacing the older Backup and Sync and Drive File Stream tools) works by maintaining a local sync engine that monitors specified folders and mirrors changes to the cloud. When you add, edit, or delete a file, the app queues that change and processes it in the background.

The upload queue lives in memory while the app is running. There's no visible queue manager in the same way a download manager might show progress bars for each file — instead, you see aggregate status in the system tray or menu bar icon. This limited visibility is exactly why clearing a stuck upload isn't always intuitive.

Temporary cache files are stored locally to speed up access to recently viewed Drive content. These aren't the same as your synced files — they're working copies the app uses to reduce repeated downloads.

How to Clear a Stuck Upload in Google Drive for Desktop 🔄

Step 1: Pause and Resume Sync

The simplest first move is to pause syncing entirely and then resume it. Click the Google Drive icon in your system tray (Windows) or menu bar (macOS), open the settings gear, and select Pause syncing. Wait 30 seconds, then select Resume syncing. This forces the sync engine to re-evaluate the queue and often clears minor stalls.

Step 2: Restart the Google Drive Desktop App

If pausing doesn't resolve it, a full restart of the application usually will. From the same system tray or menu bar icon, choose Quit Google Drive. On Windows, confirm it's fully closed via Task Manager if needed. Relaunch the app from your applications list. This clears the in-memory queue and rebuilds it from the current state of your sync folders.

Step 3: Identify the Problematic File

Persistent stuck uploads are almost always tied to a specific file, not the queue as a whole. Common culprits include:

  • Files currently open in another application (Word documents, spreadsheets, etc.)
  • Files with special characters in the filename that Drive can't process
  • Files that exceed Google Drive's individual file size limits
  • Files inside a folder that's been moved mid-sync

Check the Drive desktop app's status panel for any error indicators next to specific files. Resolving the file-level issue — closing the app using it, renaming the file, or moving it — typically unblocks the entire queue.

How to Clear the Google Drive Desktop Cache

The cache for Google Drive for Desktop is stored in a specific local directory and can be cleared manually when the app is closed.

Operating SystemCache Location
Windows%LOCALAPPDATA%GoogleDriveFS
macOS~/Library/Application Support/Google/DriveFS

Before clearing the cache:

  1. Quit Google Drive for Desktop completely
  2. Navigate to the folder path above
  3. Look for folders named with long alphanumeric strings — these are per-account cache directories
  4. Inside, the content_cache subfolder holds temporary file data and is safe to delete
  5. Do not delete the root DriveFS folder itself, as this can cause the app to lose its configuration

After clearing the cache and restarting the app, Drive for Desktop will rebuild its local cache as you access files. You may notice slightly slower initial file access while it repopulates.

Variables That Affect How This Works for You 🖥️

Not every user experiences upload clearing the same way, because several factors change what's actually going on:

  • Account type: Google Workspace (business) accounts have different sync behavior and storage quotas than personal Google accounts
  • Sync mode: "Stream files" mode and "Mirror files" mode store and cache data differently — stream mode relies more heavily on the cache you're clearing
  • File volume: Clearing a cache or restarting sync on a Drive with thousands of files takes meaningfully longer than on a small personal Drive
  • OS version: macOS and Windows handle process termination and file locking differently, which affects whether a simple restart resolves the issue or requires additional steps
  • Network conditions: A slow or unstable connection can mimic a stuck upload when the file is actually still transferring

When a Restart Isn't Enough

If uploads remain stuck after restarting the app and clearing the cache, the issue may lie at a different layer: corrupted local database files, account authentication problems, or a conflict between the sync client and your operating system's file permissions. In these cases, signing out of the Google Drive desktop app and signing back in effectively resets the sync state without removing your cloud files. This is more disruptive than a cache clear but more thorough.

A full uninstall and reinstall is the deepest reset available and resolves issues tied to corrupted app data — though it requires re-establishing your sync folder preferences afterward.


How much of this applies to your situation depends on which specific upload behavior you're seeing, which sync mode your Drive is set to, and how your local folder structure is organized. Those details change which of these steps will actually matter for your setup. ⚙️