Where Did All My Storage Go on Mac? A 2026 Detective's Checklist

You had 80 GB free last month. Now macOS is warning you about low storage and you have no idea where it went. If you're asking "where did my storage go on Mac," you're not alone — this is one of the most common and most frustrating experiences on macOS, because the operating system quietly consumes space across a dozen different locations, many of them invisible in the Finder. This guide walks through every likely culprit, in roughly the order of how often they're the actual cause.

Step 1: Get the Real Picture First

Before you delete anything, understand what you're actually dealing with. macOS has two places to check.

About This Mac → Storage

1. Click the Apple menu → System Settings (macOS 13+) or System Preferences (macOS 12).
2. Select General → Storage.
3. Wait for the bar to fully load — it can take 30–60 seconds to calculate accurately.

The colored bar gives you a broad category breakdown (Applications, Documents, System Data, etc.), but the categories are coarse and "System Data" in particular is a catch-all that often hides the real culprits.

Terminal: the honest byte count

For a no-nonsense count of what is actually consuming space on your startup disk, open Terminal and run:

sudo du -sh /* 2>/dev/null | sort -rh | head -20

This lists the top 20 directories at the root level by size. You'll need your admin password. Repeat inside suspicious directories (e.g., sudo du -sh ~/Library/* 2>/dev/null | sort -rh | head -20) to drill down.

Step 2: The Six Most Common Culprits

1. System Data / "Other" (the biggest mystery)

"System Data" in macOS storage reporting is a bucket that includes caches, logs, temporary files, Time Machine local snapshots, and anything else macOS cannot cleanly categorize. It can legitimately reach 30–60 GB on a well-used Mac without anything being wrong — but it can also balloon silently.

• User caches: ~/Library/Caches — safe to clear most of; apps rebuild what they need.
• System caches: /Library/Caches — generally safe, but requires admin access.
• Log files: ~/Library/Logs and /var/log — safe to delete old logs.
• Temporary files: /private/var/folders — macOS manages these; do not delete manually.

Be careful: cleaning is permanent. If you're unsure what a specific folder does, do not delete it. Crumb's "Is this safe to delete?" AI can explain any folder and its removal risk before you touch it.

2. Time Machine Local Snapshots

When Time Machine cannot reach your backup drive, macOS stores local snapshots on your internal disk — these can quietly consume tens of gigabytes. Check them with:

tmutil listlocalsnapshots /

To delete all local snapshots (safe if you have an up-to-date external backup):

tmutil deletelocalsnapshots /

Or delete a specific date: tmutil deletelocalsnapshots 2026-05-15-010203

3. iOS and iPhone Mirroring Backups

iTunes-era backups still live at ~/Library/Application Support/MobileSync/Backup/ on Macs running older setups, or can be managed in Finder → your iPhone → Manage Backups. A single full iPhone backup is typically 5–20 GB. If you use iCloud Backup for your devices, local backups are redundant.

4. Large App Support Folders and Caches

Applications routinely stash data far outside their .app bundle. Some common offenders:

You can clean Homebrew's download cache safely with brew cleanup. Xcode DerivedData is safe to delete — Xcode recreates it on next build. Simulator runtimes you no longer use can be removed via Xcode → Settings → Platforms.

5. Deleted App Leftovers

Dragging an app to the Trash removes the .app bundle but leaves behind preference files, caches, and support data scattered across ~/Library. Over years this debris can add up to several gigabytes. Finding all of it manually is tedious — this is exactly where download Crumb and use its Uninstall tab, which locates and lists every leftover associated with a given app so you can review and remove them together.

6. iCloud "Optimized Storage" Edge Cases

If you use iCloud Drive with "Optimize Mac Storage" enabled, files are evicted to the cloud when space is low — but iCloud metadata and partial downloads can still consume space. Check your iCloud status in System Settings → Apple ID → iCloud. Large items stuck in a "downloading" state can hold space unexpectedly. Signing out of and back into iCloud (last resort) sometimes clears these stale states.

Step 3: Find Missing Storage Mac — the Whole-Disk Audit

After checking the common culprits, you may still have unaccounted gigabytes. The Terminal du command works but requires comfort with the command line and careful navigation. Crumb's Visualize tab performs a whole-Mac audit — scanning every directory including system locations — and surfaces the largest items ranked by size, so you can see exactly which folders are consuming space without typing a single command. It works across your user folder and system volumes in one pass.

Whichever method you use, work through these folders systematically:

1. ~/Downloads — old installers and archives accumulate here silently.
2. ~/Desktop — large files on the Desktop sync to iCloud and still consume local space.
3. ~/Movies and ~/Library/Application Support/Final Cut Pro — video projects are enormous.
4. ~/.npm, ~/.gradle, ~/.m2, ~/.cargo — developer tool caches; safe to partially or fully clear.
5. /Library/Application Support — system-level app data; be more cautious here.

Step 4: What Is and Is Not Safe to Delete

This distinction matters because cleaning is permanent. A rough rule of thumb:

• Generally safe: Caches (~/Library/Caches), logs (~/Library/Logs), old Time Machine snapshots, Homebrew cache, Xcode DerivedData, app leftovers from apps you've already removed.
• Risky without research: Anything in /System, /usr, or /private; application support folders for apps you still use; anything you cannot identify.
• Do not touch: /System/Library, /usr/lib, SIP-protected paths, or any folder whose purpose is unclear to you.

When in doubt, use the "Is this safe to delete?" feature in Crumb, or search the exact folder name before removing it. A few extra minutes of research is worth it — there is no undo for permanently deleted files outside the Trash.

Keeping Storage Under Control Long-Term

• Empty the Trash regularly — files in the Trash still consume space.
• Run brew cleanup periodically if you use Homebrew.
• After finishing a development project, archive or delete node_modules, DerivedData, and build artifacts — these are the fastest-growing directories on a developer Mac.
• Review iCloud storage in System Settings → Apple ID → iCloud → Manage to see what is actually stored, not just synced.
• After any major macOS upgrade, check for leftover iOS firmware files in ~/Library/iTunes (older Macs) and /Library/Updates.

Mac storage disappears through dozens of small accumulations, not usually one big event. Work through the checklist above in order, check the actual byte counts rather than relying on the macOS storage bar alone, and be conservative about what you delete until you understand what it is. Most missing gigabytes turn out to be caches, snapshots, and developer artifacts — all recoverable space that apps will cheerfully rebuild if needed.