Mac Storage Full? Why It Happens and 9 Fixes That Work

If your Mac says storage is full but you can't figure out where the space went, you're not imagining it. macOS hides a surprising amount of disk usage in places that don't show up in the Finder — and the usual advice ("empty the Trash, delete old downloads") barely scratches the surface. This guide diagnoses the real culprits behind a full Mac disk and walks through nine fixes that actually move the needle, in order from safest to most powerful.

Why Is My Mac Storage Full? The Real Causes

Before you start deleting things, it helps to understand what's actually eating your disk. macOS groups storage into categories you can see in System Settings → General → Storage, but several of the biggest offenders are poorly labeled or invisible.

System Data Bloat

The "System Data" category in Storage settings is a catch-all for caches, logs, temporary files, and anything macOS can't cleanly categorize. On a machine that's been running for a year or two, this bucket routinely swells to 30–80 GB. It includes:

• Application caches in ~/Library/Caches/ and /Library/Caches/
• System logs in /var/log/ and ~/Library/Logs/
• Temporary files in /private/tmp/ and /private/var/folders/
• Mail attachments and message caches in ~/Library/Mail/
• Xcode derived data and simulators (often 20–60 GB on developer machines) in ~/Library/Developer/

Purgeable Space: The "Mac Says Storage Full But It's Not" Problem

macOS marks some disk space as purgeable — files the system has promised to delete if it needs room, like locally-stored iCloud documents or cached Apple TV downloads. The catch: macOS sometimes won't purge this space until it absolutely has to. So Finder might show 5 GB free, your app might get a "disk full" error, yet System Information shows 20 GB "purgeable." This is one of the most common reasons people say "I deleted everything and my Mac is still full."

App Leftovers After Uninstalling

Dragging an app to the Trash removes its .app bundle, but almost every app scatters support files across your system. These leftovers survive the uninstall:

• ~/Library/Application Support/AppName/
• ~/Library/Preferences/com.developer.AppName.plist
• ~/Library/Containers/com.developer.AppName/
• ~/Library/Group Containers/
• Launch agents in ~/Library/LaunchAgents/

A handful of uninstalled apps can leave behind 5–15 GB of orphaned files. These never appear in Storage settings because macOS doesn't know which app they belong to anymore.

Duplicate Files

Downloads folders, photo libraries, and project directories accumulate duplicates over time — the same PDF downloaded twice, photos synced from multiple devices, backup copies you forgot about. These are byte-for-byte identical files that contribute real disk usage and are entirely safe to remove once identified.

Time Machine Local Snapshots

If you use Time Machine, macOS stores local snapshots on your internal drive to serve as a safety net between backups. These count toward used space but are also purgeable — the system should reclaim them automatically under pressure, but sometimes they linger.

9 Fixes for a Full Mac Disk

Fix 1: Check What's Actually Using Space

Before deleting anything, get a clear picture. Open System Settings → General → Storage and wait for it to analyze. For more detail, use the built-in Storage Recommendations panel, or open Disk Utility. For a proper visual breakdown — including which specific folders and files are the biggest — a treemap tool gives you the full picture at a glance. Crumb's Visualize tab does this natively, showing a whole-Mac treemap down to individual files so you can spot the real culprits immediately.

Fix 2: Clear Application Caches

Application caches are temporary files apps create to load faster. They rebuild automatically, so deleting them is safe.

1. Open Finder, press Cmd+Shift+G, and go to ~/Library/Caches
2. Sort by size and look for large folders from apps you use (browsers, Spotify, Slack, etc.)
3. Delete the contents of folders, not the folders themselves
4. Repeat for /Library/Caches (requires your admin password)

Alternatively, you can do this from Terminal:

rm -rf ~/Library/Caches/*

Safe to delete: contents of Caches folders. Not safe: the folders themselves, or anything in ~/Library/Application Support/ without knowing what it is.

Fix 3: Delete Log Files

Logs are text records of what apps and the system have done. They can grow large, especially crash logs and diagnostic reports.

rm -rf ~/Library/Logs/*
sudo rm -rf /var/log/*.log /var/log/asl/

These are safe to delete. macOS and apps will create fresh logs going forward.

Fix 4: Clear Temporary Files

macOS cleans /private/tmp/ on reboot, but /private/var/folders/ (the per-user temp cache) is less reliably cleaned. A full restart clears /tmp. For the deeper temp locations:

getconf DARWIN_USER_CACHE_DIR

That command prints your specific temp cache path. Inspect the contents before deleting — it should contain only generated, non-critical files.

Fix 5: Remove Xcode Derived Data and Simulators (Developers)

If you have Xcode installed, its derived data and simulator runtimes are often the single largest disk hog on a developer Mac — frequently 20–60 GB.

# Remove derived data (safe — rebuilds on next build)
rm -rf ~/Library/Developer/Xcode/DerivedData/*

# List installed simulators
xcrun simctl list devices

# Delete unavailable simulators
xcrun simctl delete unavailable

To remove full simulator runtimes (each is 5–15 GB): open Xcode → Settings → Platforms, and delete any runtime you no longer need.

Fix 6: Clean Up After Uninstalled Apps

For apps you've already deleted, hunt down orphaned support files:

ls ~/Library/Application\ Support/
ls ~/Library/Containers/
ls ~/Library/Group\ Containers/

Look for folder names matching apps you no longer have. Cross-reference with what's installed in /Applications/ before deleting. This is tedious to do manually. Crumb's Uninstall tab automates it: select an app, and it finds every leftover file — support data, preferences, containers, launch agents — and shows you exactly what it will remove before touching anything.

Fix 7: Find and Remove Duplicate Files

Focus your duplicate hunt on the folders most likely to accumulate them:

• ~/Downloads/
• ~/Desktop/
• Your Photos library (check for repeated imports from phones or cameras)
• Project and archive folders

The Terminal command fdupes (installable via Homebrew: brew install fdupes) can scan a directory for exact duplicates:

fdupes -r ~/Downloads/

Review the output carefully before deleting — fdupes -rd will delete duplicates interactively.

Fix 8: Force macOS to Reclaim Purgeable Space

If your Mac says storage is full but the space is marked purgeable, you can nudge macOS to reclaim it. The cleanest method is to trigger iCloud optimization:

1. Go to System Settings → Apple ID → iCloud → iCloud Drive
2. If "Optimize Mac Storage" is on, macOS will offload older files to iCloud to free local space
3. Alternatively, Time Machine snapshots can be listed and deleted manually:

# List local Time Machine snapshots
tmutil listlocalsnapshots /

# Delete a specific snapshot (replace date string)
tmutil deletelocalsnapshots 2025-11-15-120032

Note: deleting local snapshots removes a recovery option until your next backup to an external drive. Only do this if your external Time Machine backup is current.

Fix 9: Use a One-Click Cleaner to Catch What You Missed

The manual steps above cover the most common culprits, but macOS generates more cleanup targets than any checklist can enumerate — browser caches, app-specific temp files, stale font caches, and more. If you've done all of the above and your Mac storage is still stubbornly full, a dedicated cleaner that knows where macOS hides things is the most practical next step.

Download Crumb for a one-click Clean that targets system caches, user caches, logs, temp files, and System Data/purgeable space in one pass — the categories most responsible for silent disk bloat. Its "Is this safe to delete?" feature, powered by on-device heuristics and optional AI, lets you ask about any unfamiliar folder before removing it, which is useful when you're not sure whether something belongs to a live app or a long-deleted one.

What You Should NOT Delete

Some folders look large and tempting but should never be touched:

As a general rule: if you don't know what a folder is, don't delete it. Use macOS's built-in Quick Look (spacebar in Finder) or a tool with a "safe to delete" explanation before removing anything unfamiliar. Cleanup is permanent unless you've moved files to a quarantine folder first.

A Word on "Mac Says Storage Full But It's Not"

If an app crashes with a disk-full error but Finder shows available space, you're almost certainly hitting a purgeable-space timing issue. macOS reports free space to apps differently than Finder does, and purgeable blocks aren't counted as available until the system actually writes them out. The fix: trigger a large file write (even a test file via dd) to force macOS to purge, or use the Time Machine snapshot deletion commands in Fix 8 above. If the problem persists, check whether APFS is reporting space correctly:

diskutil apfs list

Look for the "Purgeable" figure under your APFS volume. That's the space macOS can reclaim but hasn't yet.

Conclusion

A full Mac disk is almost never just a matter of having too many files in obvious places. System Data bloat, purgeable space that macOS won't release, orphaned app leftovers, and accumulated caches account for the majority of mysteriously full storage on machines that feel like they shouldn't be full. Work through the fixes in order — starting with caches and logs, then app leftovers and duplicates, then forcing purgeable space to clear — and you'll typically recover tens of gigabytes without deleting anything you care about. When in doubt about any file or folder, check before you delete: permanent is permanent.