Emergency Mac Cleanup: Free Up 50GB+ in 10 Minutes

Your Mac's storage warning just appeared at the worst possible moment — a Final Cut render, an Xcode update, or a macOS upgrade sitting at "not enough space." This guide is about how to free up space on Mac fast, ordered from the largest, safest wins to the smaller ones, with realistic estimates so you know where your 10 minutes are best spent. Everything here works on macOS Monterey through macOS 26 Tahoe.

Before You Start: Check What's Actually Taking Space

Open Apple menu → System Settings → General → Storage. Wait 20–30 seconds for the bar to populate. The categories shown — Applications, Documents, System Data, iCloud Drive — tell you where to attack first. "System Data" is usually the biggest surprise and the least understood; it includes caches, Time Machine local snapshots, and purgeable space.

Step 1: Clear Caches, Logs, and Temp Files (5–20 GB typical)

This is the fastest single action and the safest. macOS and apps accumulate gigabytes of cache files that are automatically regenerated on demand — deleting them never causes data loss.

The one-click route

Crumb is a menu-bar utility that clears system caches, user caches, log files, temp files, and reclaims purgeable space in a single click. For a genuinely emergency cleanup this is the fastest option — open it from the menu bar, click Clean, and it's done in under a minute. You can download Crumb and use one cleanup for free, no account needed.

The manual route

If you prefer Terminal, you can clear the user cache yourself. Quit all apps first, then run:

rm -rf ~/Library/Caches/*

For system-level caches (requires admin password):

sudo rm -rf /Library/Caches/*

Clear system logs:

sudo rm -rf /private/var/log/*
sudo rm -rf ~/Library/Logs/*

Risk level: Very low. These files are safe to delete. Apps will recreate whatever they need. The one real caveat: don't delete caches mid-operation (e.g., while Xcode is indexing).

Step 2: Remove Time Machine Local Snapshots (2–30 GB)

Time Machine keeps local snapshots on your internal drive so you can restore files even when your backup disk isn't connected. These are the "purgeable" bytes macOS reports — the system will delete them automatically under storage pressure, but you can reclaim them right now.

List your local snapshots:

tmutil listlocalsnapshots /

Delete all of them at once (you will still have your full off-site backups):

tmutil deletelocalsnapshots /

On Apple Silicon Macs you may need to target the data volume:

tmutil deletelocalsnapshots /System/Volumes/Data

Risk level: Low, provided your Time Machine external backup is current. Verify that first with tmutil latestbackup.

Step 3: Delete Large Files and Downloads (varies widely)

Your Downloads folder is often a graveyard of disk images, ZIP archives, and installer packages you'll never open again.

1. Open Finder, go to ~/Downloads, sort by Size (View → Show View Options → Sort By: Size).
2. Look for .dmg, .zip, .pkg, and .iso files. If you've already installed the app, the disk image is safe to trash.
3. Empty the Trash when done.

To find large files across your entire home folder via Terminal:

find ~ -size +500M -not -path "*/.*" 2>/dev/null | sort

Risk level: Depends. Review before deleting. Never trash a file you don't recognize in a system path.

Step 4: Uninstall Applications You No Longer Use (1–10 GB per app)

Dragging an app to the Trash removes the .app bundle but leaves behind preference files, Application Support data, and caches scattered across ~/Library. A proper uninstaller cleans all of it.

Crumb's Uninstall tab lists every installed app, shows its total disk footprint including leftover files, and lets you remove everything in one shot. For large creative apps (Adobe, DaVinci Resolve, Xcode simulators) this can reclaim tens of gigabytes.

If you want to do it manually for a specific app, its leftovers are typically in:

• ~/Library/Application Support/<AppName>
• ~/Library/Preferences/com.developer.AppName.plist
• ~/Library/Caches/com.developer.AppName
• /Library/Application Support/<AppName> (system-wide)

Step 5: Clear Xcode Derived Data and Simulator Runtimes (5–50 GB for developers)

If you do any iOS or macOS development, Xcode's derived data and cached simulator runtimes are notorious space hogs.

# Derived data — safe to delete, Xcode rebuilds it
rm -rf ~/Library/Developer/Xcode/DerivedData

# Archives you no longer need to distribute
# ~/Library/Developer/Xcode/Archives

# Simulator runtimes (large — only delete versions you're not targeting)
xcrun simctl delete unavailable

To see how much each simulator runtime takes:

du -sh ~/Library/Developer/CoreSimulator/Profiles/Runtimes/*

Risk level: Low for DerivedData (fully regenerated), medium for runtimes (takes time to re-download).

Step 6: Prune Docker Images and Volumes (2–40 GB for Docker users)

Docker desktop stores images, containers, and volumes in a disk image that grows without bound unless you prune it.

# Remove stopped containers, unused images, dangling volumes, and build cache
docker system prune -a --volumes

Risk level: Review first with docker system df. This is destructive — running containers and named volumes are preserved by default, but double-check before running.

Step 7: Optimize iCloud Drive and Photos Library

If you use iCloud, you can offload originals to the cloud and keep optimized local copies:

• Photos: Photos app → Settings → iCloud → "Optimize Mac Storage"
• iCloud Drive: System Settings → Apple ID → iCloud → iCloud Drive → "Optimize Mac Storage"

This won't free space instantly — macOS decides when to evict local copies — but it reclaims space passively over the following hours.

Quick Reference: Expected Space Savings

What Not to Delete

A few folders that look like cache but are not safe to remove:

• ~/Library/Application Support/MobileSync/Backup — your iPhone/iPad backups
• ~/Library/Mail — local mail storage (offline access will break)
• /private/var/db and /System/Library — system internals, never touch manually
• Any folder you don't recognize in /Library without looking it up first

If you're ever unsure whether a folder is safe to delete, Crumb's "Is this safe to delete?" AI explains any path and its removal risk in plain language, using on-device heuristics without sending file contents anywhere.

Conclusion

Working through steps 1–4 alone typically frees 15–60 GB on a developer machine and 5–25 GB on a general-use Mac. Start with caches and Time Machine snapshots for the fastest wins, work your way down to app cleanup and developer artifacts, and you'll almost certainly have the space you need before your install or render begins. Cleaning is permanent, so take 10 seconds to confirm what you're removing — but don't let caution stop you from reclaiming space that was never doing anything useful.