Google Drive Streaming Still Using Disk Space? What the Cache Actually Stores

Short answer: Google Drive's Stream files mode is designed to minimize local storage, not eliminate it. Google documents that streamed file data is stored in a local content cache, and local disk is also used when you open files, mark them available offline, or work on recently and frequently used content. Unsynced changes can also live in that cache until they reach the cloud. If your SSD is filling up, the first job is therefore not “delete the cache.” It is to identify which local state is consuming space and whether any unsynced work still depends on it.

That distinction matters because the safest fix for a folder made available offline is not the same as the safest fix for a cache holding unsynced edits. Clearing or disconnecting the wrong layer can turn a storage problem into a data-loss problem.

Streaming does not mean zero local storage

Google's current Drive for desktop documentation makes the distinction explicit:

Streaming stores files primarily in the cloud.
Local storage is still used when you work on files on the computer.
Recently and frequently used files may occupy local space.
Files marked Available offline use local disk space.
Streamed file data is stored in a local content cache.
Unsynced changes can remain in that cache until they upload.

By contrast, Mirroring keeps a full local copy of My Drive content in addition to the cloud copy.

That means a user can be in Stream files mode and still see gigabytes of Google Drive-related local usage without anything being “broken.” The technical question is whether that usage is expected for your recent workload or whether the wrong files have become persistent local content.

A similar misconception exists with other virtual-drive products. If you use pCloud as well, How pCloud Drive Cache Actually Works explains the same general lesson through a different client architecture: a cloud-first view still needs some local state to operate.

First confirm that you are actually in Stream files mode

Before troubleshooting cache size, verify the sync mode itself.

Open Google Drive for desktop → Settings → Preferences → Folders from Drive / Google Drive, then check whether My Drive syncing options is set to Stream files or Mirror files.

If it says Mirror files, the local disk usage may simply be the expected full local copy.

Mode	Primary file location	Normal local disk behavior
Stream files	Cloud-first	Cache, opened files, recent/frequent files, offline-marked files, unsynced changes
Mirror files	Cloud + local disk	Full local copy of mirrored My Drive content

Shared drives are a separate detail: Google states that Shared Drives are streamed rather than mirrored. Local folders you choose under Folders from your computer are handled as mirrored content.

Do not diagnose a mirrored library as a “runaway stream cache.” They are different storage models.

The four local states that can make Stream files use much more disk than expected

A useful way to troubleshoot this is to separate local usage into four buckets.

1. Files you opened recently

When you open a streamed file, Drive needs local file data so the application can read it. Google states that streaming uses local storage when you work on files and for recently or frequently used files.

This is expected behavior.

The size impact depends on your workload. Opening a few documents may be trivial. Opening multi-gigabyte video files, disk images, RAW photo libraries or project archives can create a much larger local footprint.

2. Files or folders marked Available offline

This is the most common “I thought I was streaming” surprise.

Google states that marking a streamed file Available offline makes it consume local hard-drive space. Marking a folder available offline does the same for all files inside it, and new items added to that folder are automatically available offline too.

That means one offline folder can quietly grow over time even if the rest of My Drive remains cloud-first.

Open the Drive for desktop menu and inspect Offline files. This is more useful than guessing from folder icons alone because it gives you a direct inventory of content intentionally retained locally.

3. Content cache for streamed files

Google documents a local content cache for streamed data. This cache exists because streamed files still need local data while being opened, edited, or used offline.

On Windows and older macOS implementations, Drive for desktop manages this cache automatically. For work or school accounts, an administrator may be able to configure a cache limit.

On newer versions of macOS using Apple's File Provider architecture, Google says macOS manages the content cache and the user cannot set the same cache-space limit through Drive for desktop.

This platform difference matters. A “change the cache limit” fix that may exist in one environment is not a universal macOS solution.

4. Unsynced changes

This is the state you must protect before doing aggressive cleanup.

Google's advanced documentation states that, in streaming mode, unsynced changes are stored in a local cache and can be lost if that cache is cleared or corrupted.

That turns the cache from “temporary junk” into a possible holder of the only current copy of recent work.

Before clearing application data, disconnecting the account, moving cache-related directories, or reinstalling the client, confirm that important recent edits have already reached Drive online.

If the problem involves files Drive could not upload and moved aside, use Google Drive Lost & Found: Recover Unsynced Files Before You Disconnect before changing account state.

Decision tree separating normal Google Drive cache use from offline files, mirrored files and unsynced changes

Check this before deleting anything

Use this order.

Step 1: Compare the file with drive.google.com

For any important file edited recently, confirm the latest version exists online.

If the current version exists only locally, do not clear cache or disconnect the account yet.

Step 2: Inspect Offline files

Open the Drive for desktop menu and review the Offline files section. Look for unexpectedly large folders or folders you forgot were pinned offline.

If the local usage is mostly intentional offline content, the problem is not cache corruption. It is a storage-policy choice.

Step 3: Check Stream versus Mirror

If My Drive is mirrored, the full local footprint is expected.

If you switched from Mirror to Stream recently, continue to the next section because the old mirror folder can remain on disk until you remove it safely.

Step 4: Check whether the SSD is nearly full

A nearly full cache partition can itself become a Drive problem. Google states that you cannot upload a folder larger than the available storage on the partition where the cache folder is located.

This is a subtle but important interaction: a cloud upload can fail because the local staging/cache environment lacks enough free space, even when the cloud account itself has plenty of quota.

Step 5: Identify whether a large application workload is forcing local reads

Video editors, photo tools and applications that repeatedly scan or rewrite large files may interact poorly with streaming. Google specifically notes that applications requiring extensive writing, video editing or high-resolution photo editing are often faster with mirroring.

If your workflow constantly touches the full content, the problem may be architectural: streaming is minimizing idle storage, but the application is repeatedly demanding the data anyway.

If Offline files are the cause, remove offline persistence—not the cloud file

If you intentionally or accidentally made a large file or folder available offline, the safest fix is to change that availability state rather than deleting the file.

What to do:

Confirm the file exists correctly in Drive online.
Remove the Available offline setting for the content you no longer need locally.
Allow Drive and the operating system time to release local file data according to the current client/platform behavior.
Recheck free disk space.

Why this works:

You are changing the local persistence requirement, not deleting the cloud object.

Risk:

Low if the cloud copy is already confirmed and there are no unsynced edits.

How to verify:

the file remains visible in Drive;
the online copy is intact;
the file is no longer listed as offline-pinned;
local free space improves after the system releases local data.

Do not use Delete as a substitute for “make this cloud-only.” Deletion changes the synchronized file state, not merely its local availability.

If you recently switched from Mirror to Stream, the old mirrored folder may still be taking space

This is one of the easiest storage problems to misdiagnose.

Google's switch procedure says that when you move from Mirror files to Stream files, the old mirrored My Drive folder stops syncing. Google instructs users to:

ensure local files have finished syncing to the cloud;
switch to Stream files;
close Drive for desktop;
then delete the old mirrored folder.

Google also explicitly warns that you should confirm sync completion before deleting or moving folders to avoid data loss.

So if you switched modes and expected hundreds of gigabytes to disappear automatically, check whether the previous mirror folder is still sitting on disk as an ordinary local folder.

Do not delete it just because the new virtual Drive is working. First confirm that every file you care about exists in the cloud and that there are no local-only changes inside the old folder.

If the cache itself is large, do not treat “clear cache” as the first move

A cache can contain expendable file data, but Google also documents that unsynced changes in streaming mode can live there.

That means the correct sequence is:

Verify remote state → protect unsynced local work → identify offline-pinned content → only then consider cache-level remediation.

Blindly deleting cache directories is not a professional first-line fix because the meaning of that data depends on current sync state, OS implementation and client version.

On newer macOS systems, the situation is even more platform-dependent because macOS manages the File Provider content cache. A Windows-specific cache path or manual deletion recipe should not be copied to modern macOS.

CloudScope therefore does not recommend a generic “delete this folder” command here.

Why a huge upload can fail even though you use streaming

Google's content-cache documentation contains an easy-to-miss limitation: Drive for desktop cannot upload a folder larger than the available free space on the partition where the cache is located.

This can produce a confusing incident:

cloud quota is sufficient;
the source folder is visible;
Drive is configured to stream;
the local SSD has limited free space;
a very large folder upload stalls or fails.

The mistake is assuming streaming removes every local-space requirement from the upload path.

It does not.

If your failure begins during very large transfers, also separate this from Google's server-side transfer rules. Google Drive Upload Stopped After 750 GB? covers the separate per-user 24-hour upload/copy ceiling used in Workspace environments.

macOS File Provider changes what you can control

Modern macOS versions can stream Google Drive through Apple's File Provider framework. Google documents several practical consequences, including that macOS manages the content cache and that the Drive application may not expose the same cache-size controls available in other environments.

This means two users can both say “Google Drive Stream files is using disk space” and still have different remediation options depending on operating system and Drive architecture.

Do not follow a Windows cache tutorial on a current Mac simply because the symptom looks the same.

The safe invariant is platform-independent:

Protect unsynced work first, identify intentional offline content second, and only then reduce disposable local state using controls supported by that platform.

What not to do

Do not disconnect the account just to reclaim space

Google states that offline streamed files are removed when a streaming account is disconnected. More importantly, disconnecting while unsynced work or recovery data exists can complicate recovery. Diagnose first.

Do not delete the old mirrored folder before verifying cloud sync

A mode switch does not prove every local file reached the cloud. Confirm the online copy first.

Do not assume every gigabyte belongs to cache

Mirrored folders, offline-pinned content, opened media and other application temp files can all contribute to disk pressure.

Do not assume streamed means “zero bytes local”

Google explicitly documents local cache and offline use. Treat zero-local-storage expectations as the wrong mental model.

Do not clear state while Drive reports unsynced changes

If the only current copy lives in the local streaming cache, clearing it can destroy the very data you are trying to protect.

Safe sequence for reducing Google Drive local disk usage without losing unsynced changes

A practical 2 a.m. diagnostic sequence

If your SSD is suddenly full and Google Drive is one of the suspected consumers, use this order:

Confirm whether My Drive is set to Stream files or Mirror files.
Open Drive online and verify the newest version of important recent files.
Open Drive for desktop's Offline files view.
Identify large offline-pinned folders and files.
If you recently switched from Mirror to Stream, locate the old mirror folder.
Check local free space on the cache partition.
Consider whether recent work opened or edited very large files repeatedly.
Only after remote state is verified should you reduce offline persistence or remove an old mirrored copy.
Avoid generic cache deletion if any unsynced work remains.
Verify success by checking both local free space and current file state online.

Success is not simply “the disk number went down.” Success means:

the intended cloud copies are intact;
recent edits are present online;
no important local-only file disappeared;
offline-pinned content matches your actual needs;
the SSD has enough working headroom for Drive and other applications.

The deeper rule: cloud-first is not local-free

The mistake behind this problem is usually conceptual rather than a broken setting.

A streamed cloud drive still needs local mechanisms for file access, caching, offline work and unsynced edits. The real optimization is not to eliminate all local usage. It is to make sure only the data that needs to be local is persistent.

If your archive is so large that even normal cache and active-project working sets regularly exhaust the SSD, the next question may not be “How do I clear more cache?” It may be whether the workflow should use a larger local working disk, mirrored active projects, or a different storage architecture. Cloud Storage vs External Hard Drive is the better next decision if local working capacity has become the bottleneck.

And if the files are supposed to protect you from loss rather than simply stay accessible, review Cloud Backup vs Cloud Storage. Reducing a cache is not the same thing as improving recovery.

Sources and verification

CloudScope checked these primary sources on 21 August 2026:

Google Drive Help — Stream & mirror files with Drive for desktop: https://support.google.com/drive/answer/13401938
Google Drive Help — Use Google Drive files offline: https://support.google.com/drive/answer/2375012
Google Drive Help — Customize Drive for desktop settings / content cache: https://support.google.com/drive/answer/13470231
Google Drive Help — Manage Google Drive for desktop: Advanced guide: https://support.google.com/drive/answer/16631477
Google Drive Help — Understand your computer and Google storage when using Drive for Desktop: https://support.google.com/drive/answer/17196458

Product behavior, UI labels and macOS File Provider behavior can change. Re-check the current client documentation before publishing this draft.

Internal Link Map

pCloud Drive cache explanation → /articles/pcloud-drive-cache-explained/ → mechanism comparison → Horizontal
Google Drive Lost & Found → /articles/google-drive-lost-and-found/ → protect unsynced files → Horizontal
Google Drive Upload Stopped After 750 GB? → /articles/google-drive-750gb-upload-limit/ → separate daily transfer limit → Horizontal
Google Drive Storage Full → /articles/google-drive-storage-full/ → distinguish cloud quota from local disk → Horizontal
Cloud Storage vs External Hard Drive → /articles/cloud-storage-vs-external-hard-drive/ → local working-capacity decision → Down
Cloud Backup vs Cloud Storage → /articles/backup-vs-cloud-storage/ → recovery architecture → Down
/category/cloud-storage/ → topic hub → Up

Reverse Internal Link Suggestions

google-drive-storage-full → add contextual link distinguishing cloud quota from local SSD/cache pressure.
google-drive-lost-and-found → link here where streaming cache and unsynced local state are discussed.
pcloud-drive-cache-explained → link here as Google Drive comparison for virtual-drive local cache behavior.
cloud-storage-vs-external-hard-drive → link here from local SSD pressure / cloud-streaming discussion.

Image Metadata

Purpose: Show the four different local-storage states behind Drive streaming.

Filename: google-drive-streaming-local-storage-hero.svg Alt: Google Drive streaming local storage diagram showing cloud files, local cache, offline files and mirrored files Placement: After introduction Source: Original technical diagram based on Google Drive documentation Format: SVG Dimensions: 1200×630

Purpose: Diagnose which layer is consuming local disk.

Filename: google-drive-streaming-disk-space-cause-tree.svg Alt: Decision tree separating normal Google Drive cache use from offline files, mirrored files and unsynced changes Placement: After four-state explanation Source: Original technical diagram based on Google Drive documentation Format: SVG Dimensions: 1200×760

Purpose: Show safe cleanup order that protects unsynced work.

Filename: google-drive-streaming-safe-cleanup.svg Alt: Safe sequence for reducing Google Drive local disk usage without losing unsynced changes Placement: Before 2 a.m. diagnostic sequence Source: Original technical diagram based on Google Drive documentation Format: SVG Dimensions: 1200×760

CTA

Commercial CTA: None. This is a low-commercial troubleshooting article. Internal next-step CTAs only.

Structured Data

Article
BreadcrumbList

OG

OG Title: Google Drive Streaming Still Using Disk Space? OG Description: Streaming minimizes local storage; it does not eliminate cache, offline files or unsynced local state. Diagnose the exact layer before deleting anything. OG Image: /assets/google-drive-streaming-local-storage-hero.svg

Google Drive Streaming Still Using Disk Space? Here's What Is Actually Local