You paid for a 2TB cloud storage subscription on iCloud, Google Drive, or OneDrive. You uploaded thousands of high-resolution photos and family videos, feeling victorious because you bought a laptop with a modest 256GB SSD. You tell yourself, "My files live in the cloud now! My laptop's drive is completely empty."

Then, a week later, a giant warning banner pops up across your screen: "Disk Almost Full: 2GB Remaining." You open File Explorer or Finder in total shock. How can a laptop with almost no local files be completely full? You didn't buy offloaded storage; you just set up a bidirectional mirror that is quietly filling your internal drive with hidden caches [1].

The Fallacy of the Virtual Drive

Most consumer cloud services do not operate like a USB thumb drive. When you drag a 10GB video into your cloud folder, the desktop app doesn't simply upload it and delete the local copy. It establishes a Sync Relationship.

By default, cloud utilities maintain a local copy of every single file on your internal drive so you can access them when offline. Even when you enable "Online-Only" or "Optimize Storage" mode, your operating system creates local file system pointer files (placeholders). While the full file raw bytes reside on remote servers, your computer still caches huge amounts of local data:

• High-Resolution Thumbnail Databases: Browsing through 50,000 cloud photos requires your computer to store gigabytes of local preview thumbnails so scrolling through folders remains instant.
• Hidden Hydration Caches: The moment you double-click or preview a cloud file, your OS quietly "hydrates" it—downloading the full raw file to a hidden system cache folder (like ~/Library/Caches or Appdata/Local).
• Stale Temporary Writes: When editing cloud documents, software creates temp files locally that often fail to purge automatically after background syncs complete.

The Background Hydration Trigger

The sneakier culprit is third-party software running in the background. Even if you set your cloud folder to "Online-Only," local indexing software (like Spotlight, Windows Search, backup tools, or antivirus scanners) periodically crawls your directories.

When an antivirus or indexing daemon touches a cloud placeholder file to scan it, the cloud engine assumes you requested the file and automatically triggers background hydration [2]. Within an hour, hundreds of gigabytes of "online-only" files get pulled back down onto your local flash storage without your knowledge.

How to Reclaim True Local Drive Space

Take manual control over your cloud sync client and purge hidden hydration caches using these controls:

• Manually Evict Local File Contents: On macOS, right-click any cloud folder and select "Remove Download." On Windows OneDrive, right-click and select "Free Up Space." This strips the physical bytes off your local SSD while keeping the visual placeholder icon.
• Purge System Cloud Caches: Check your system storage breakdown for "System Data" or "Other." Use utility apps to purge hidden cloud provider cache directories (e.g., clearing Dropbox's hidden .dropbox.cache folder).
• Use Web Interfaces or Mountable Network Drives: If you truly want files completely isolated from your internal hard drive, do not install desktop sync apps. Access your cloud files strictly via web browser or mount them as a remote WebDAV / S3 network drive (like Mountain Duck) that bypasses local folder sync entirely.

The Key Takeaway

Cloud sync desktop applications are mirror utilities, not secondary hard drives. Unless you actively evict downloaded files or access them via a web browser, your cloud drive will continuously hydrate cached files back onto your local storage. Monitor your placeholder settings and purge local downloads regularly.