Why deleting files in Drive for Desktop doesn’t free local space

Deleting files or folders inside your local Google Drive for Desktop directory often does not increase your computer’s free hard drive space. This happens because Drive for Desktop operates as a cached virtual mount. Depending on your sync mode, the files you deleted may have been cloud placeholders that never occupied local disk space to begin with, or the deleted data has simply moved to local and cloud trash bins without being purged from disk.

Quick Answer

If your sync setting is set to Stream, deleted files were cloud placeholders taking up 0 bytes of physical disk space. If the files were Mirrored or cached locally, deleting them sends them to your operating system’s Recycle Bin/Trash and Google Drive’s cloud Trash. You must empty both trash locations and clear the local virtual file cache to recover space.

---

Cause 1: You Deleted “Streamed” Files (Virtual Placeholders)

Google Drive for Desktop offers two sync modes: Stream files and Mirror files.

When configured to Stream files (the default setting):

• Drive mounts a virtual drive letter (such as G:\ on Windows) or a virtual volume under macOS (/Volumes/GoogleDrive or within ~/Library/CloudStorage).
• The files visible in File Explorer or Finder do not actually live on your physical hard drive. They are sparse, virtual metadata pointers that display the file name, modified date, and size without storing the underlying file content locally.
• The Result: If you delete a 40 GB folder of video files that was purely streamed, your physical local disk space will not increase by a single megabyte because those 40 GB were stored entirely on Google’s cloud servers, not on your SSD.

---

Cause 2: The Two-Stage Trash System

When you delete a file that was stored locally (such as an offline cached file or a mirrored file), the operating system and Google Drive protect against accidental deletion by moving the data through two separate staging areas:

1. Your OS Recycle Bin / Trash: When you press Delete in File Explorer or move an item to the Trash in macOS Finder, the file is moved to your local OS trash folder. Until that bin is manually emptied, the physical bytes remain allocated on your drive.
2. Google Drive Cloud Trash: Simultaneously, Drive for Desktop marks the file for deletion in the cloud, placing it into the cloud Trash bin where it continues to exist for 30 days.

To release the space:

• Windows: Right-click the Recycle Bin on your desktop and select Empty Recycle Bin.
• macOS: Right-click the Trash icon in your Dock and select Empty Trash.

---

Cause 3: The Hidden Local Content Cache Remains Full

Drive for Desktop maintains a hidden local directory where it stores temporary working copies of files you have opened, edited, or uploaded. Even after you delete a file through File Explorer or Finder, Drive for Desktop’s local cache engine may keep the underlying data blocks cached until the cache cleanup cycle triggers or local disk limits are enforced.

The local cache lives in these default paths:

• Windows: %LocalAppData%\Google\DriveFS
• macOS: ~/Library/Application Support/Google/DriveFS

Within this directory, a subfolder named with a long string of numbers (your account ID) contains the cached file blocks. Deleting files through your regular desktop file manager does not instantly truncate this cache directory.

---

How to Safely Reclaim Local Disk Space

If you confirmed that files were stored locally and emptying your operating system’s trash did not reclaim your hard drive space, follow this sequence:

Step 1: Adjust Your Local Cache Size Limit

You can force Google Drive for Desktop to restrict how much local disk space it reserves for temporary cache storage:

1. Click the Google Drive icon in the Windows system tray (bottom-right) or macOS menu bar (top-right).
2. Click the Settings gear icon and choose Preferences.
3. Click the secondary Settings gear in the top-right corner of the Preferences window.
4. Scroll down to Local cached files directory.
5. Check the option for Disk space usage limit (if available on your version) or switch the synchronization method.
6. If you have folders set to “Available offline,” right-click those folders in File Explorer/Finder, select Offline access, and choose Online only. This strips the local physical bytes while keeping the files accessible via the cloud.

Step 2: Clear the Local DriveFS Cache Safely

Do not manually delete random files inside the DriveFS directory while the application is active; doing so can corrupt your sync database and cause sync loops. Instead:

1. Fully quit Google Drive for Desktop (Click Settings gear > Quit).
2. For detailed, step-by-step instructions on purging these cached blocks without breaking your profile, follow How to Clear Google Drive Local Cached Files Safely.
3. Restart Google Drive for Desktop. The application will rebuild a clean, compact database containing only the metadata for your active files.

---

Cause 4: APFS Local Snapshots (macOS Specific)

On macOS, users often delete tens of gigabytes from Google Drive only to see “Available Space” remain completely unchanged in Disk Utility.

This is frequently caused by Apple File System (APFS) local snapshots created automatically by Time Machine. When you delete files, APFS retains the physical storage blocks in a hidden snapshot until the snapshot is pruned or transferred to an external backup drive.

To check for and clear local snapshots:

1. Open Terminal.
2. Run the following command to list active snapshots: tmutil listlocalsnapshots /
3. If snapshots are listed, you can thin them by running: tmutil thinlocalsnapshots / 10000000000 4

This instructs macOS to clear local snapshot caches, immediately releasing the freed blocks to the file system.

If your local drive remains full despite these steps, review How to Resolve “Disk Full” Errors with Plenty of Space.