Key takeaways:

Before you start

Back up first. If you’re not running Time Machine or a cloud backup already, do that before touching system files. None of the steps below require sudo or disabling System Integrity Protection, and none delete anything outside your user Library or app support folders, but disk cleanup is still not the moment to skip a backup.

Step 1: See what’s actually using your space

Open the Apple menu, click About This Mac, go to Storage, then click Manage. This gives you a real breakdown instead of a guess: Applications, Documents, System Data, Photos, and so on. On macOS Tahoe this pane is under Storage Settings directly; on Sonoma and earlier it opens a separate management window. Either way, note your System Data figure specifically, since that’s the category almost all cleanup targets below.

A healthy System Data figure on a current macOS version generally sits between 12 and 25 GB. If yours is well above 30 GB, everything below applies to you directly.

Step 2: Clear purgeable space and thin local snapshots

“Purgeable” space is macOS’s own reserve — old iCloud-synced files it can re-download, cached data it can rebuild, and local Time Machine snapshots. macOS is supposed to clear this automatically under storage pressure, but it doesn’t always trigger reliably, especially with an external Time Machine drive that’s rarely connected.

Check how many local snapshots exist and how much space they hold:

tmutil listlocalsnapshots /
tmutil listlocalsnapshotdates /

To manually thin snapshots older than a specific date (replace the date with one from the output above):

sudo tmutil deletelocalsnapshots 2026-05-01-120000
Warning: This command requires sudo. Only delete snapshots you can confirm are old via listlocalsnapshotdates, and keep your actual Time Machine backup drive connected and current before removing any local snapshot.

Step 3: Empty user and app caches safely

Caches are the single largest recurring category most people never touch. They live in three places, and only one of them is yours to manage:

Location What it is Safe to clear?
~/Library/Caches Per-app user caches: browser cache, app thumbnails, download temp files Yes, generally safe
/Library/Caches System-wide caches shared across users, install/update leftovers Usually safe, review before deleting
/System/Library/Caches OS-level caches protected by SIP Don’t touch — you can’t anyway

To see what’s taking the most room before deleting anything:

du -sh ~/Library/Caches/* | sort -rh | head -20

You’ll typically see Safari, Chrome, and any Electron-based apps (Slack, Discord, VS Code) near the top, often 1–5 GB each. Delete the contents of individual subfolders rather than the whole Caches directory at once, so you can confirm nothing breaks before moving to the next one. If you’d rather skip the folder-by-folder hunt, CleanMyMac app maps every cache in a single scan and lets you review before removing anything.

Step 4: Remove old iOS backups and fully uninstall unused apps

Two categories consistently produce the biggest single recoveries, and neither shows up clearly in Finder.

Old iOS device backups, if you ever backed up an iPhone or iPad through Finder, live at ~/Library/Application Support/MobileSync/Backup/. Each one can run 5 to 50 GB, and it’s common to find backups of a device you no longer own. Check them via Finder > your device > Manage Backups, rather than deleting the folder directly.

App leftovers are the bigger trap. Dragging an app to Trash removes the .app bundle but rarely touches its support files, caches, and preferences, which persist at:

~/Library/Application Support/[AppName]
~/Library/Caches/[AppBundleID]
~/Library/Preferences/[AppBundleID].plist
~/Library/Logs/[AppName]

Adobe Creative Cloud, Xcode, and Microsoft Office are the most commonly cited offenders here, sometimes leaving several gigabytes behind per app, long after the main application is gone. This is the one category where a dedicated Mac junk removal tool genuinely saves time over hunting four separate folders manually per app — MacPaw’s CleanMyMac for Mac (version 5.5.6, rated 4.9/5 from 539 reviews) includes a full App Uninstaller module that catches all leftover files in one pass. It’s worth naming as the exception rather than the rule.

Step 5: Clear developer and creative-app-specific caches

If you do any development or creative work, this step alone can outweigh everything above it.

du -sh ~/Library/Developer/Xcode/DerivedData
du -sh ~/Library/Caches/Homebrew
docker system df

Xcode’s DerivedData folder regenerates on next build and is safe to clear entirely:

rm -rf ~/Library/Developer/Xcode/DerivedData/*

Homebrew’s download cache is safe to clear the same way:

brew cleanup --prune=all

Docker Desktop is its own separate problem — its virtual disk image doesn’t shrink automatically even after you delete images and containers inside it. Run docker system prune -a to reclaim space inside Docker, and check Docker Desktop’s own resource settings if the VM disk itself still shows as large afterward. For a visual overview of what’s eating space across all these categories, the best Mac disk cleanup utility options (including CleanMyMac, available from MacPaw at $3.33/month on an annual plan, or $119.95 as a one-time purchase) can map your entire disk at a glance.

Step 6: Verify what you actually reclaimed

Go back to About This Mac > Storage and check System Data again. Don’t be alarmed if the number hasn’t dropped immediately — the Storage pane recalculates on a delay and Spotlight often needs to reindex changed folders first. Give it 15 to 60 minutes before assuming a step didn’t work.

What this won’t fix

This process clears caches, backups, snapshots, and leftovers — it does not reduce the actual size of your Photos library, your Documents, or apps you’re still using. If System Data itself stays unusually high after all six steps, that points toward something more specific: a corrupted Spotlight index (rare, but has been reported reaching hundreds of gigabytes before a rebuild), a runaway log file, or an APFS snapshot issue that needs its own diagnosis. It also won’t fix a genuinely full disk that just has too much data on it for its size — at that point the fix is an external drive or iCloud offloading, not cleanup.

Frequently asked questions

Why does my Mac say disk almost full when Finder shows free space?

This usually means the space is tied up as purgeable storage or local Time Machine snapshots, both counted by macOS as used until the system needs the room. It typically resolves once macOS needs the space or you thin the snapshots manually.

Is it safe to delete everything in ~/Library/Caches?

Generally yes for user-level caches in ~/Library/Caches, since apps rebuild them automatically. Avoid touching /System/Library/Caches, which is protected by System Integrity Protection anyway.

Does clearing cache make a Mac slower afterward?

Briefly. The first launch of an app after clearing its cache takes slightly longer while it rebuilds necessary files, but it’s a one-time cost measured in seconds.

How much space can I realistically free up on a Mac?

On a Mac uncleaned for a year or more, 10 to 30 GB of safe-to-delete data is common, with old iOS backups and abandoned app leftovers usually the largest single chunks.

Why did my storage not change right after deleting files?

The Storage pane doesn’t refresh instantly. It recalculates on a delay and after Spotlight reindexes changed folders, so give it 15 to 60 minutes before assuming a deletion didn’t work.