Mac Full Before a Demo? A Founder’s 20-Minute Disk Space Triage

It’s 8:50 a.m. Your investor demo starts at 9:00. Xcode refuses to build, Docker won’t start, and macOS keeps telling you the disk is almost full. You don’t have time to learn what “System Data” means. You need 40 GB back, now, without deleting anything you’ll regret.

Quick answer To free up disk space on a Mac, start with the biggest, safest targets. Open System Settings → General → Storage, then clear rebuildable data: developer caches (Xcode, Docker, Homebrew, npm), AI models you no longer use, and old Time Machine local snapshots. Rebuildable data is safe to remove. Your documents and project source never need to be touched.

This guide is the runbook I’d hand a founder: ordered by how much space you recover per minute, with the exact commands and the risks of each.

Why founder Macs fill up differently

A typical user’s disk fills with photos and downloads. A founder’s disk fills with regenerable machinery: build artifacts, container images, package caches, simulator runtimes, and increasingly, local AI models measured in gigabytes each.

That’s good news. Regenerable data can be deleted and rebuilt, and you only pay for it with a slower next build or a re-download. The bad news is that most of it hides in places Finder doesn’t show, and the built-in Storage panel lumps much of it into “System Data” or “Developer.”

Minute 0–2: Get a map before you delete anything

Open System Settings → General → Storage and wait for the bars to finish calculating. Note the size of Developer, System Data, and anything labeled for apps like Docker or Xcode.

Then ask the terminal where your home folder’s weight is:

 bash du -sh ~/* ~/.[!.]* 2>/dev/null | sort -h | tail -15

This lists the 15 heaviest items in your home directory, including hidden folders like .ollama, .npm, and .cache. For a visual view, free or paid disk visualizers such as GrandPerspective, OmniDiskSweeper, and DaisyDisk all do this well. The built-in tools show you the number, and a visualizer shows you the shape.

Where the space usually hides Where Typical culprit Safe to remove? How ~/Library/Developer/Xcode/DerivedData Old build output Yes, rebuilt on next build Delete the folder contents Docker Desktop’s disk image Unused images, stopped containers, build cache Yes, if you don’t need them docker system df, then docker system prune ~/.ollama/models Downloaded LLMs Yes, re-downloadable ollama list, then ollama rm ~/.cache/huggingface/hub Model weights from Python/ML work Yes, re-downloadable huggingface-cli scan-cache / delete-cache Homebrew Old formula versions, downloads Yes brew cleanup -s and brew autoremove npm / pnpm / yarn caches Package tarballs Yes npm cache clean –force, pnpm store prune, yarn cache clean node_modules in dead projects Dependencies of abandoned side projects Yes, reinstall later See below Time Machine local snapshots Local snapshots on the internal drive Mostly, macOS thins them itself tmutil listlocalsnapshots / ~/Library/Application Support/MobileSync/Backup Old iPhone/iPad backups Only if you have another backup Delete via Finder’s device management Minute 2–8: The AI model sweep (usually the biggest win in 2026)

If your team experiments with local models, this is likely your largest single reclaimable chunk. A handful of quantized models can quietly occupy tens of gigabytes, and most are ones you tried once.

Ollama:

 bash ollama list # shows each model and its size ollama rm # removes one

Hugging Face cache: run huggingface-cli scan-cache to see every cached repo with its size, then huggingface-cli delete-cache for an interactive picker. Newer versions of the library also ship an hf command with similar subcommands .

LM Studio and similar apps keep their own model folders. Check each app’s settings for the model directory path, since it has moved between versions.

Be honest with yourself here: keep the one or two models you actually use daily, delete the rest. Re-downloading is a bandwidth cost, not a data loss.

Minute 8–14: Developer caches

Work through these in order of how much they usually hold.

Docker. Run docker system df first. It shows how much is reclaimable by category. Then:

 bash docker system prune # stopped containers, dangling images, unused networks, dangling build cache docker builder prune # build cache docker image prune -a # ALL images not used by a container; broader, check first

One catch: Docker Desktop stores everything in a single virtual disk file, and that file doesn’t always shrink immediately after pruning. If free space doesn’t move, check Docker Desktop’s settings for disk image options, or restart Docker, before assuming the prune failed.

Xcode. DerivedData is the easy win:

 bash rm -rf ~/Library/Developer/Xcode/DerivedData

Also look at ~/Library/Developer/Xcode/iOS DeviceSupport (symbols for old devices and OS versions), Archives, and simulators. xcrun simctl delete unavailable removes simulators whose runtimes are gone.

Homebrew, npm, pnpm, yarn. Run the commands from the table. Each is quick, and the combined savings are usually a few gigabytes.

Dead node_modules. This one pays off for founders with a graveyard of prototypes:

 bash find ~/code -name node_modules -type d -prune -print0 | xargs -0 du -sh 2>/dev/null | sort -h | tail -15

Change ~/code to wherever your projects live. Delete the ones attached to projects you haven’t touched in months. npm install brings them back.

Minute 14–18: Snapshots and the “purgeable” trap

macOS counts some space as purgeable: local Time Machine snapshots, cached iCloud content, and similar items it will clear automatically when something needs room. Two practical consequences:

The free-space number in Finder may look larger than what a tool like df reports, because Finder includes purgeable space. Large installers or builds can still fail even when Finder says you have space, if the system hasn’t purged yet.

To see local snapshots:

 bash tmutil listlocalsnapshots /

You can delete one with tmutil deletelocalsnapshots

MacSnip MacSnip app macsnip.app.