A file manager that reaches cloud storage too

A Mac with a sync client installed ends up with two file systems that look like one. Finder shows Google Drive in the sidebar, the folders open, the documents are there, and nothing seems unusual until a second file manager is pointed at the same location. Then the sidebar entry is missing, or a folder scan takes several minutes, or the reported folder size is a fraction of what it should be, or the app fills the disk by pulling down twenty gigabytes nobody asked for.

None of that means the file manager is broken. Cloud storage on macOS stopped behaving like a plain folder several releases ago, and a large share of the tools people reach for still assume the old arrangement. Once the current arrangement is clear, choosing a file manager that handles Google Drive properly becomes a short list of yes or no questions rather than a matter of taste.

Where Google Drive actually lives on a current Mac

Since macOS 12.3, Apple has required cloud storage providers to plug into the system through a File Provider extension instead of mounting a volume or planting a folder in the home directory. Google Drive, Dropbox, OneDrive, and Box all went through that migration. Apple describes the mechanism plainly in the framework documentation.

An extension other apps use to access files and folders managed by your app and synced with a remote storage. Source: developer.apple.com

The practical result is a path change. Content now appears under ~/Library/CloudStorage/, with one directory per connected account, named in the form [email protected]. The older arrangements, a ~/Google Drive folder from Backup and Sync and a mounted volume at /Volumes/GoogleDrive from Drive File Stream, are gone. iCloud Drive is a separate case and still sits at ~/Library/Mobile Documents/com~apple~CloudDocs.

Two things follow from that path. First, ~/Library is hidden in Finder by default, which is why the folder can feel unreachable even though it is an ordinary path in a shell. Second, any file manager, script, backup rule, or launch agent that still points at ~/Google Drive is pointing at nothing. A surprising number of stale automation problems on Macs trace back to exactly that, and the fix is a path update rather than a new tool.

Anything that can open a directory can open this one. The distinction that matters is not whether a file manager can see the folder. It is what the file manager does with items inside it that have not been downloaded.

Streaming and mirroring create different problems

Google Drive for desktop offers two modes for the same account, and they behave nothing alike from a file manager's point of view.

Streaming a file uses almost no computer space, but mirroring downloads a full copy directly to your computer. Source: support.google.com

In streaming mode, most items on disk are placeholders. The name, the size, and the modification date are real. The contents are not present until something reads the file, at which point the system fetches it. Apple calls these dataless files. In mirroring mode, every selected file is a full local copy, disk usage matches the cloud, and a file manager sees an ordinary directory tree.

Streaming is the default for a reason: a Google account includes 15 GB of storage shared across Drive, Gmail, and Photos, and paid plans go far beyond what most laptops can hold. Mirroring an entire shared drive is often physically impossible. That is why the placeholder model exists, and why it is worth understanding before blaming a file manager for odd behaviour.

The single most useful setting is per folder rather than per account. Drive for desktop can mirror specific folders while streaming the rest. Mirroring the two or three directories used every day, and leaving the archive streamed, removes almost every symptom described below without giving up the space savings.

Why a folder scan stalls on cloud storage

A placeholder becomes a real file the moment something reads its contents. That is fine when a person double clicks a document. It is expensive when a tool walks the tree.

Several ordinary operations read every file they touch:

• Calculating folder sizes, which many file managers do automatically in a details view
• Generating thumbnails or previews for a folder full of images and video
• A recursive text search that opens files rather than asking Spotlight
• Checksum based backup and sync tools comparing content instead of metadata
• Command line habits like du -sh, grep -r, and find . -exec pointed at a streamed directory

Any of those can turn a browse into a bulk download that saturates the connection and fills the disk. The behaviour is identical whether the tool is a graphical file manager or a shell one liner, because both are simply reading files.

The defences are unglamorous and effective. Turn off automatic folder size calculation for cloud paths. Prefer mdfind, which queries the Spotlight index, over grep -r when searching a streamed tree. Exclude ~/Library/CloudStorage from any backup tool that reads file contents. Mirror the working folders and stream the archive. And when a file manager offers a setting for handling files that are not downloaded, find it before the first large scan rather than after.

Four routes into Google Drive, and what each one costs

There is more than one way for a file manager to reach the same account, and the differences are structural rather than cosmetic.

Route	Where it appears	Local copy	Reachable from a shell	Behaviour with streamed files
Sync client plus Finder	~/Library/CloudStorage/	Only if mirrored	Yes	Native placeholder support
Another file manager over the same path	~/Library/CloudStorage/	Only if mirrored	Yes	Depends on the app
A file manager with a built-in Drive connection	Remote pane or mounted volume	Downloaded on demand	Only while mounted	Not applicable, nothing is stored locally
A command line mount such as rclone	A chosen mount point	Cached only	Yes	Not applicable

The second row is where most disappointment happens. A file manager that treats a dataless file as an ordinary file will happily materialize a folder of raw video to draw a preview grid. Tools built after the File Provider transition tend to leave placeholders alone. Tools designed for the older mounted volume model tend not to.

The third row covers apps that speak to Drive directly rather than through the sync client: Cyberduck, Mountain Duck, ForkLift, Commander One, and CloudMounter all offer a Google Drive connection of some form. That route sidesteps placeholder handling entirely, because nothing is stored locally in the first place. The trade is that files exist only inside that app's session, so a shell, a text editor, or a build script cannot reach them unless the app mounts a volume as well.

One detail catches people out on every route. Google Drive permits two files with the same name in the same folder, and a Google Docs item is not a document at all but a small link file with a .gdoc, .gsheet, or .gslides extension. Any file manager showing a Drive tree is showing an approximation of something that was never a POSIX file system.

Shared drives are not the same object as My Drive

An account often holds two very different things that look identical in a file listing. My Drive belongs to the person. A shared drive belongs to the organization, and each one appears as its own top level directory inside the account folder rather than nested inside My Drive.

The distinction shows up in three places that matter to a file manager.

Storage accounting is the first. Files in a shared drive never count against the personal Google storage quota, even though syncing them consumes real space on the laptop. A tool reporting how much of the quota a folder uses is answering a different question from a tool reporting disk usage, and on a shared drive the two numbers have no relationship at all.

Permissions are the second. Access is granted server side at the drive or folder level, so the POSIX mode bits visible in a file manager are a local fiction. Running chmod inside a shared drive changes nothing about who can open the file, and a file manager that offers a permissions dialog for cloud paths is offering a control that does not reach the thing it appears to control.

The third is Shared with me. Those items are not present on disk at all unless they have been explicitly added to a drive or given a shortcut. A recursive copy of the account folder will silently skip everything that only appears under Shared with me, which is a common and unpleasant discovery during a migration or an audit.

Four questions worth asking before switching tools

Feature lists rarely answer these. A ten minute test on a real folder does.

Does it leave undownloaded files alone

Point the candidate at a streamed folder holding large media, switch to a view that shows previews, and watch the network. If throughput jumps, the app is materializing placeholders. Sometimes that is desirable. It should be a choice rather than a surprise.

Does search use the system index

Spotlight indexes metadata for streamed items without downloading them, so a search by name or type stays cheap. An app doing its own recursive walk over file contents does not have that property. For a large Drive, this one difference decides whether search takes seconds or an afternoon.

Does the terminal follow the current folder

Cloud paths are long, contain an account address, and often contain spaces. Typing them is unpleasant and error prone. A file manager whose shell inherits the visible directory removes the problem completely. A file manager without one turns every operation into a copy and paste of a path fragment.

What is backing this up

Time Machine excludes ~/Library/CloudStorage, and cloud sync is not a backup: a deletion propagates. Any file that exists only in a streamed folder needs a separate answer, whether that is a mirrored copy, a versioned archive, or an export on a schedule.

The requirement hiding behind the search

Searches for a Mac file manager that handles Google Drive usually come from a specific daily shape: files in a cloud folder, a shell open in another window running against those same files, and increasingly an assistant in a third window that has been told about neither. The cost is not any single step. It is the constant re-establishing of context, three times over, for the same directory.

Seen that way, the feature to filter on is not the Drive connection. Google Drive already appears as a normal path in every application on the Mac. The feature to filter on is whether the folder view, the shell, and the assistant share a working directory, so that a path selected in one is already current in the others. The set of tools that do this is much smaller than the set that lists cloud support, and the difference in a working day is larger. The specific behaviours involved are described under what it does, how the same session continues away from the desk is covered under continuing from iPhone and iPad, and a side by side view of the alternatives sits on the comparison page.

What to change first

Before installing anything, open Drive for desktop settings and mirror the two or three folders used daily while leaving the rest streamed. That single change removes most of the stalling, the wrong folder sizes, and the surprise downloads, and it costs nothing. If the remaining friction is switching between a folder, a shell, and an assistant on the same directory, the tool to look at next is Atriens, which keeps those three in one window.