Google Drive for desktop on Mac is acting like malware in a suit. It's supposed to quietly sync files in the background, but instead it happily balloons to 20–30GB of RAM and drags the entire system to its knees.

By Joshua at JK Dreaming • March 2026

This isn't a "close a few tabs" issue. This is watching Activity Monitor and realizing a single sync app is eating more memory than your DAW, browser, and editor combined. So if Google's not going to ship sane defaults, the only real move is to smack Drive down until it behaves.

Step 1: Catch Google Drive in the Act

Open Activity Monitor and sort by Memory. Find Google Drive / GoogleDriveFS. If you're seeing RAM numbers in the double digits (in GB), you're not crazy — that's ridiculous for a sync tool.

At this point, treat it like a runaway process, not a trusted utility:

Open Activity Monitor → sort by Memory column
Locate GoogleDriveFS or Google Drive for Desktop
Force-quit if memory usage exceeds a few hundred MB
Reboot fully before reconfiguring

Only after the reboot do you let Drive start again — and this time, on your terms.

Sort by memory — Drive wins, horribly

Step 2: Stop Mirroring Your Entire Life

By default, Drive loves to mirror or keep files "available offline," which is great until you realize it's hammering local resources.

In the menu bar app, open Preferences → Google Drive and switch to Stream files, not Mirror.

Streaming mode means files stay in the cloud by default and are fetched on demand — not treated like a second local disk. If you're building, rendering, or working with big media directories, the last thing you want is Drive eagerly indexing all of it in real time.

Step 3: Put Drive on a Cache Diet

If there's any setting for cache or local storage, crank it down, not up. Look for options like cache size, storage on this computer, or similar.

Set cache limit to a conservative single-digit GB
Clear existing cache once to eliminate corrupt/bloated state
Never mark massive folders as "available offline"
Offline + giant file trees = nonstop scanning and memory churn

Step 4: Tell Drive It Doesn't Run the Show

Don't let Drive sync whenever it feels like it. It runs on your schedule.

When you're focused on work: Pause syncing. When you're done with heavy tasks or away from the machine: Resume and let it catch up.

Exclude any folder that's noisy. Drive is terrible at being a file watcher for hot, constantly-changing dev or media folders:

node_modules/
.next/ .astro/ .nuxt/
dist/ build/ out/
media-cache/ .cache/

Treat it as an archive/transfer tool, not a live mirror of your working directory.

Step 5: Keep It Updated, But Don't Blindly Trust It

Sometimes the resource usage is tied to a specific version or macOS combo.

Update Drive for desktop to the latest version
If it still behaves like a memory leak with a logo, don't waste time debugging Google's regression for them
Use the web UI when you only need occasional access
If an app consistently eats 20–30 GB of RAM, it has forfeited the right to auto-launch on login

A more lightweight client or one-off mount is always better than giving Drive permission to run wild on your system.

Step 6: Nuclear Reset If It Keeps Misbehaving

If Drive climbs right back up in RAM even after all the above, it's time for a hard reset:

Sign out of Drive in the app
Quit it completely
Nuke its local data folder (~/Library/Application Support/Google/DriveFS)
Sign back in and re-configure with strict streaming and minimal offline folders

Think of it as a hard reset for a sync brain that's gotten corrupt or stuck in a pathological state. Ten minutes re-authing beats living with a helper that randomly steals half your memory.

My Baseline "Don't Wreck My Mac" Setup

Here's my non-negotiable Google Drive configuration:

Stream files only — No mirroring, no local copies unless explicitly needed
Critical folders only — Never build outputs, caches, or dev tooling
Cache capped + cleared — Conservative limit, cleared when things feel weird
Sync paused during deep work — Resume manually when ready to let it catch up

Google built Drive for convenience, but they're not the ones dealing with crashes, beachballs, and brutally slow context switches. If the app won't respect your hardware, you have to enforce boundaries yourself.