How to Clear Google Drive Local Cached Files Safely

Google Drive for Desktop stores temporary local file copies and offline metadata on your computer’s local drive to allow fast streaming and offline access. Over time, this cache folder can bloat to dozens of gigabytes, fill up your primary storage drive, or cause persistent sync errors. Deleting these files improperly while Drive is actively running can corrupt your local database or permanently delete unsynced modifications.

Fast Fix

Verify that all files are fully synced by checking the Google Drive tray icon. Then, completely quit Google Drive (Settings gear > Quit). Press Win + R, enter %LOCALAPPDATA%\Google\, and rename the DriveFS folder to DriveFS_Backup. Restart Google Drive. The app automatically creates a fresh cache directory and re-indexes your cloud files without data loss.

Diagnostic Snapshot

Parameter	Specification
Target Application	Google Drive for Desktop (Windows & macOS)
Default Cache Path (Windows)	%LOCALAPPDATA%\Google\DriveFS
Default Cache Path (macOS)	~/Library/Application Support/Google/DriveFS
Risk Factor	Deleting the cache while local edits remain unsynced will cause permanent loss of those offline edits.
Admin Access Required	No (User profile level)

Forensic Decision Path

Follow this flow before touching the cache directory:

[Local Drive Space Is Full / Cache Issues]
  │
  ├─► Are there unsynced files or pending upload errors in the Drive desktop menu?
  │     ├─► Yes ──► DO NOT delete the cache. Resolve sync queue or manually back up modified files first.
  │     └─► No  ──► Proceed to safe cache eviction or cache rebuild.
  │
  ├─► Is your goal simply to free up hard drive space?
  │     ├─► Yes ──► Change file status from "Available offline" to "Online only", or set cache size limits in Registry.
  │     └─► No (troubleshooting corrupted sync) ──► Perform a full `DriveFS` folder rebuild.
  │
  └─► Did deleting cloud files fail to free local disk space?
        └─► See [Why deleting files in Drive for Desktop doesn't free local space](<http://www.workspaceforensics.com/google-drive-manual/google-drive-storage-reporting/drive-desktop-deletion-not-freeing-space>).

What This Means: System Mechanics

Google Drive for Desktop uses a streaming architecture. When you open a cloud file, it downloads chunks of that file to a local staging database inside a folder named DriveFS.

Inside DriveFS, Google maintains:

1. Content Cache (/content_cache): Binary chunks of files you recently opened, previewed, or marked for offline use.
2. Metadata Engine (SQLite Databases): Local indices linking cloud file IDs to virtual paths in Windows File Explorer or macOS Finder.
3. Upload Outbox: Offline file edits waiting for a stable internet connection to upload to Google Workspace.

If you delete files directly from content_cache while GoogleDriveFS.exe is running, the underlying SQLite database loses track of file chunks. This triggers virtual drive unmounting, client crashes, or generic sync errors. For application crash diagnostics, see “Google Drive for Desktop encountered an error and has stopped”.

Common Reasons to Clear the Cache

• Drive Storage Exhaustion: The local C: drive is running out of space because Drive for Desktop cached large video, design, or archive files. If you receive persistent low disk space alerts, see How to Resolve “Disk Full” Errors with Plenty of Space.
• Stuck Sync Cycles: The sync engine remains stuck on “Checking for updates” or hangs indefinitely on a corrupt local file chunk. Refer to Fix: Google Drive for Desktop Stuck on “Checking for updates”.
• Ghost Mount / File Explorer Disappearance: The local database is corrupted, preventing the virtual drive from mounting into File Explorer. See Fix: Google Drive Not Showing Up in Windows File Explorer.
• Leftover Temporary Files: Sync bloat from temporary editing lock files (.tmp). See Troubleshooting .tmp File Sync Bloat in Google Drive.

Common Misdiagnoses

• Misdiagnosis: “Deleting files from the G: virtual drive frees up local drive space immediately.”
  • Distinction: Deleting a file from the virtual drive deletes it from Google Drive (cloud and trash). It does not necessarily clear the cached disk blocks allocated in %LOCALAPPDATA% until the application runs its scheduled garbage collection cycle.
• Misdiagnosis: “Clearing the cache deletes files in the cloud.”
  • Distinction: As long as files are fully synced to Google Drive servers, deleting or rebuilding the local DriveFS folder only removes local mirror copies. Your cloud files remain intact.

Safe Resolution Steps

Step 1: Verify Sync Status and Back Up Pending Work

Before making any changes, confirm no unsynced changes exist:

1. Click the Google Drive icon in the taskbar or menu bar.
2. Ensure the status reads Everything is up to date.
3. If there are sync errors or pending uploads, manually copy those specific files out of your virtual drive to a safe local folder (like your Desktop).

Step 2: Gracefully Terminate Google Drive

1. In the Google Drive desktop menu, click the Settings gear icon.
2. Click Quit.
3. Ensure background processes have closed (check Task Manager for GoogleDriveFS.exe on Windows or Activity Monitor on macOS).

Step 3: Rebuild the Cache Folder

On Windows:

1. Press Win + R, paste the following path, and press Enter:Plaintext %LOCALAPPDATA%\Google
2. Locate the folder named DriveFS.
3. Rename this folder to DriveFS_Old. (Renaming rather than deleting creates an immediate fallback if you discover missing offline edits).
4. Launch Google Drive from the Start Menu.
5. Sign in if prompted. Google Drive will create a clean DriveFS directory and stream metadata afresh.
6. Once you confirm all files are accessible, delete the DriveFS_Old folder to reclaim your hard drive space.

On macOS:

1. Open Finder, press Cmd + Shift + G, paste:Plaintext ~/Library/Application Support/Google
2. Locate DriveFS and rename it to DriveFS_Old.
3. Relaunch Google Drive from Applications.
4. Verify your files load in Finder, then move DriveFS_Old to the Trash and empty it.

Alternative: Free Space Without Resetting the Database

If your cache is working fine and you only want to free up local disk space without re-syncing:

• Clear Offline Availability: Open your Google Drive virtual folder in File Explorer or Finder. Right-click folders containing large files, select Offline access, and choose Online only. This removes local cached content while preserving your folder structure.
• Change Cache Location to Another Drive: If your secondary drive has more space:
  1. Open Google Drive Preferences > Settings gear.
  2. Under Local cached files directory, click Browse and point the path to a folder on your secondary partition (e.g., D:\GoogleDriveCache).
  3. Click Save and restart the app.

Admin & Advanced Checks: Enforcing Cache Limits

Enterprise administrators can enforce hard cache size ceilings across Windows endpoints via the Registry or Group Policy:

• Registry Location: HKEY_LOCAL_MACHINE\Software\Google\DriveFS
• Value Name: ContentCacheMaxKbytes
• Type: DWORD (32-bit)
• Setting: Enter the maximum cache size in kilobytes (for example, 10485760 sets a 10 GB limit).

In Virtual Desktop or non-persistent environments, redirecting the cache requires specific profile considerations. See Drive for Desktop vs. Virtual Desktop Infrastructure (VDI).

Hard Stops

Stop troubleshooting and back up your data before altering cache files if:

• Drive is Stuck in a Disconnect Loop with Unsynced Changes: If the account is repeatedly disconnecting and you have local changes that never reached the cloud, do not delete the cache folder. Renaming or deleting it will erase those unsaved edits. Follow Resolving “Account disconnected: Please sign in again” Loops to safely preserve your local files