Mac Storage Full After Deleting Files? 9 Reasons Why

You delete a folder of old videos, empty a downloads pile, and open About This Mac — only to find the bar barely moved. Mac storage full after deleting files is one of the most frustrating experiences on macOS, and it almost always has a specific, fixable cause. This guide walks through nine reasons your space hasn't been freed, and exactly what to do about each one.

1. The Trash Hasn't Been Emptied

Deleting a file moves it to the Trash; the space is not reclaimed until you empty it. This is the most common culprit and the easiest to dismiss once you've been using a Mac for a while — but it's also easy to forget when you're in the flow of a cleanup.

1. Right-click the Trash icon in the Dock and choose Empty Trash.
2. If files are locked and refuse to delete, hold Option while clicking Empty Trash to force-remove them.
3. Check whether any external drive has its own Trash: open the drive in Finder, then press Shift-Command-. (period) to reveal hidden items. Look for a .Trashes folder.

2. APFS Snapshots Are Holding Your Space Hostage

This is the reason most people never find on their own. macOS (since High Sierra) uses APFS, which creates local snapshots for Time Machine backups. When you delete a file, APFS marks the space as free in the filesystem — but the snapshot still references the old data, so the space cannot physically be reused until the snapshot ages out or is pruned.

To see what snapshots exist on your startup volume:

tmutil listlocalsnapshots /

You'll get a list like com.apple.TimeMachine.2026-05-31-143022. To delete a specific snapshot:

tmutil deletelocalsnapshots 2026-05-31-143022

To delete all local snapshots at once:

tmutil deletelocalsnapshots / --all

After running this, open About This Mac and give Finder a moment to recalculate. You may see several gigabytes reappear immediately.

Is this safe? Yes. Local snapshots are only for convenience — they back Time Machine up while waiting to sync to your backup drive. Deleting them does not affect your files. Your actual Time Machine backups on external media are unaffected.

3. Purgeable Space Is Not the Same as Free Space

macOS reports disk usage in two categories: available and purgeable. Purgeable space is held by items macOS believes it can delete safely on demand — iCloud-optimized documents, cached app content, and so on. The OS will release this space automatically when an app needs it, but it still shows up as "used" in most views, which makes your drive look fuller than it functionally is.

To see the breakdown, hold Option while clicking the Apple menu and choose System Information, then go to Storage. You can also check in Terminal:

df -h /

The Available column reflects only non-purgeable free space. If you need that purgeable space freed immediately (for example, before installing Xcode), the fastest way is to trigger a large write operation — but that is awkward. A tool like Crumb surfaces purgeable volume explicitly and can trigger a flush so you see accurate numbers right away.

4. Optimized Storage and iCloud Downloads

If you use iCloud Drive with "Optimize Mac Storage" enabled, macOS keeps low-resolution placeholders locally and stores the full files in iCloud. But if you've downloaded files for offline use, those full copies are sitting on disk. Similarly, Photos with "Optimize Mac Storage" on can have full originals downloaded without you realizing it.

1. Open System Settings → Apple Account → iCloud → iCloud Drive and confirm Optimize Mac Storage is on.
2. In the Finder sidebar, look for items with a cloud-download icon — these are already local. Items with a cloud icon only are placeholders.
3. In Photos, go to Photos → Settings → iCloud and switch from "Download Originals" to "Optimize Mac Storage" if it was changed.

5. System Data / "Other" Storage Is the Real Culprit

In macOS 13 and later, the storage breakdown in System Settings shows a System Data category that can balloon to tens of gigabytes. It contains caches, log files, temporary files, and developer data. This is legitimately reclaimed space — it's just not obvious which items inside are safe to touch.

Common locations to check manually:

• ~/Library/Caches — per-app caches; generally safe to delete app-specific subfolders
• /Library/Caches — system-wide caches; delete subfolder contents, not the folders themselves
• ~/Library/Logs and /Library/Logs — log files; safe to delete
• /private/var/folders — temporary session files; macOS manages these, but they can grow large
• ~/Library/Developer/Xcode/DerivedData — if you use Xcode, this folder can reach 20+ GB

What NOT to delete: Do not delete ~/Library/Application Support folders for apps you actively use — this can destroy app preferences and saved data. Do not delete anything inside /System or /usr.

6. App Leftovers From Dragged-to-Trash Uninstalls

When you drag an app to the Trash instead of using its uninstaller, the app binary is removed — but support files, caches, and preference files spread across ~/Library/Application Support, ~/Library/Preferences, and ~/Library/Containers remain. Over time these orphaned files accumulate silently.

To find them manually, search each of those directories for folder names matching the app or its developer. For a more systematic pass, download Crumb — its Uninstall tab detects installed apps and shows you the associated leftover files before you commit to removing them.

7. Large Hidden Files

Some processes create large files in locations Finder never shows by default. A few common offenders:

• iOS device backups: ~/Library/Application Support/MobileSync/Backup — iTunes/Finder backups for iPhones and iPads can each be several gigabytes.
• Virtual machine disk images: .vmdk, .sparseimage, or .vhd files wherever Parallels, VMware, or UTM stores them.
• Homebrew downloads cache: $(brew --cache) — usually ~/Library/Caches/Homebrew. Run brew cleanup to clear old versions.
• Docker images and volumes: ~/Library/Containers/com.docker.docker can grow very large.

To find the largest files from Terminal:

sudo du -sh ~/* | sort -rh | head -20

Or navigate your full disk visually with a treemap tool to spot outliers quickly.

8. Sleepimage and Swap Files

macOS writes a sleepimage file to disk to support hibernation. On a Mac with 16 GB RAM, this file is 16 GB. It lives at /private/var/vm/sleepimage. On Apple Silicon Macs running macOS 12+, the sleepimage behavior changed significantly and the file may not be present or may be managed differently.

You can check whether it exists:

ls -lh /private/var/vm/

Deleting the sleepimage manually is not recommended — it will be recreated, and on some configurations it can interfere with wake-from-sleep. If you want to disable hibernation on an Intel Mac to prevent the file from being written:

sudo pmset -a hibernatemode 0

Use this only if you understand the trade-off: your Mac will lose unsaved work if the battery dies completely while sleeping.

9. The Disk Usage Display Hasn't Refreshed

This sounds trivial but matters: the storage bar in System Settings and the Finder sidebar can lag by several minutes after large deletions. APFS recalculates space asynchronously. Before concluding that space wasn't freed, wait 60 seconds and check again — or run:

df -h /

in Terminal, which queries the filesystem directly and reflects actual state immediately.

Comparing the Causes at a Glance

Putting It All Together

When your Mac storage is full after deleting files, the fix is almost always one of these nine things. Work through the list top to bottom — empty the Trash first, then check APFS snapshots (the most commonly missed cause), then look at purgeable space and System Data. Most people recover 10–30 GB just by clearing snapshots and caches they didn't know existed.

If you want to skip the Terminal commands and get a clear picture of what's actually taking up space, Crumb combines a disk treemap, one-click cache clearing, and an Uninstall tab that surfaces leftover files — all without requiring an account or sending your file names anywhere. The free tier covers one full cleanup to confirm it works for you before you commit.