You deleted a folder, maybe even several. You emptied the Trash. You dragged apps to the bin. And yet your Mac storage bar is still screaming red. If you're staring at the "why is my mac storage full when i deleted everything" problem, you are not going crazy — macOS hides gigabytes of reclaimable space in at least eight places your Finder window never shows you. This article names each one, shows you exactly where to look, and explains the safest way to actually get that space back.
1. The Trash Is Not Actually Empty
This sounds obvious, but Finder has more than one Trash. If you use an external drive or a network location, macOS creates a hidden .Trashes folder at the root of each volume. Files you delete from those volumes land there, not in your main Trash. The main Trash icon can show empty while gigabytes linger elsewhere.
- Open Finder, choose Finder → Empty Trash (not just close the Trash window).
- For external drives, right-click the Trash icon and choose Empty Trash — this sweeps all volumes.
- To inspect hidden trash folders on an external disk, press Cmd+Shift+. in Finder to show hidden files, then look for
.Trashesat the root of the volume.
Safe to delete: Yes. Trash exists purely for recovery before permanent removal.
2. Purgeable Space Is Counted as "Used"
APFS (the file system on every modern Mac) reports a category called purgeable space. This includes iCloud-optimized local copies, cached files macOS thinks it can evict, and other items the OS has flagged as removable — but has not removed yet. The macOS storage bar shows this as used, even though macOS will clear it when you genuinely run out of room.
The frustrating part: you cannot manually reclaim purgeable space the way you delete a file. macOS releases it on its own schedule. You can nudge it by running the following Terminal command, which asks the OS to purge its disk cache immediately:
sudo purgeYou will be asked for your password. After it completes, check Apple menu → About This Mac → Storage again — the available number often jumps by several gigabytes.
Safe to run: Yes. purge only evicts cached data; it does not touch your files.
3. Time Machine Local Snapshots Are Invisible GB
When Time Machine cannot reach your backup destination (the drive is unplugged, the NAS is offline), macOS silently stores local snapshots right on your SSD. These can grow to tens of gigabytes and are completely invisible in Finder. They appear inside the "System Data" category in the storage overview, so you see a huge number there with no obvious way to shrink it.
To list all local snapshots:
tmutil listlocalsnapshots /To delete a specific snapshot (replace the date string with one from the list above):
tmutil deletelocalsnapshots 2026-05-28-032145To delete all local snapshots at once (macOS will rebuild them as needed):
tmutil deletelocalsnapshots / --allSafe to delete: Generally yes, if your external Time Machine drive is healthy and up to date. If your drive has not backed up recently, deleting local snapshots removes your only recent recovery point.
4. iCloud Optimized Files Still Occupy Local Space
If you use iCloud Drive with Optimize Mac Storage enabled (System Settings → Apple ID → iCloud → iCloud Drive), macOS is supposed to evict old files to the cloud and keep only recent ones locally. In practice, the eviction is lazy — files you accessed months ago may still have full local copies sitting in ~/Library/Mobile Documents/.
You cannot force-evict individual files via Terminal reliably. The practical options are:
- Right-click a folder in Finder and choose Remove Download to evict it to iCloud-only.
- Toggle iCloud Drive off and back on in System Settings, which forces a fresh sync assessment.
- Accept that macOS will eventually evict them — it just may not do so until storage pressure is real.
Safe to evict: Yes, as long as your iCloud account is active and you have reliable internet access to re-download them.
5. App Caches Have Grown Unchecked
Every app on your Mac writes cache data to ~/Library/Caches/. Browsers are the worst offenders — Chrome, Firefox, and Safari can each hold multiple gigabytes of cached web data. Video editors (Final Cut, DaVinci Resolve), Xcode, Docker, and Spotify are also notorious.
To see what is largest in your user cache folder:
du -sh ~/Library/Caches/* | sort -rh | head -20Individual subfolders (for example ~/Library/Caches/com.apple.Safari or ~/Library/Caches/Google/Chrome/Default/Cache) are generally safe to delete while the app is closed — the app will rebuild the cache on next launch, which will be slower than usual for a session. The system-level cache at /Library/Caches/ (no tilde) requires more caution; files there are owned by macOS or daemons and may not be straightforward to delete individually.
Safe to delete: User caches — yes, with app closed. System caches — selectively and with care.
6. Log Files Are Silently Accumulating
macOS and every third-party app write diagnostic logs to ~/Library/Logs/ and /var/log/. Crash reports pile up in ~/Library/Logs/DiagnosticReports/. These are rarely enormous individually, but they add up over months of use.
To check the size of your user logs:
du -sh ~/Library/Logs/To delete all crash reports (safe):
rm -rf ~/Library/Logs/DiagnosticReports/*The system log directory at /var/log/ is managed by macOS's newsyslog daemon and rotates automatically — leave those alone unless you have a specific reason to inspect them.
Safe to delete: User-level logs and crash reports — yes. System logs — leave them to macOS.
7. Deleted Apps Left Leftover Data Behind
When you drag an app to the Trash, macOS removes the app bundle but leaves support files scattered across your Library folder. A typical app can leave behind files in five or more locations:
| Location | What Lives There |
|---|---|
~/Library/Application Support/ |
User data, project files, settings |
~/Library/Preferences/ |
.plist settings files (usually small) |
~/Library/Containers/ |
Sandboxed app data (can be very large) |
~/Library/Group Containers/ |
Shared app-group data |
/Library/Application Support/ |
System-wide app data (requires admin to remove) |
Finding these manually requires knowing the app's bundle identifier and searching each path. An easier approach: Crumb's Uninstall tab detects installed and recently removed apps, surfaces their leftover files with sizes, and lets you remove them in one step — the same workflow that would otherwise take ten minutes of Terminal spelunking per app.
Safe to delete: Leftovers from apps you have already uninstalled and do not plan to reinstall — yes. Be cautious with Application Support folders for apps you still use; they may contain documents or project files, not just cache.
8. The Storage Bar Has Not Refreshed Yet
This is the most infuriating culprit and the one people overlook: macOS's storage graph in System Settings is notoriously slow to update. It can lag by several minutes, and on large drives the calculation can take much longer. The number you are reading may simply not reflect what you did five minutes ago.
How to force a refresh:
- Close System Settings entirely.
- Wait 2–3 minutes, then reopen it and navigate back to Storage.
- If the number still looks wrong, run
df -h /in Terminal — this queries the live filesystem directly and does not have the same lag as the GUI.
df -h /The "Avail" column in that output is what your disk actually has free right now.
A Faster Way to Find and Clear All of It at Once
Manually hunting through eight categories across a dozen Library paths is genuinely tedious. If you want to see everything at once — caches, logs, purgeable space, Time Machine leftovers, app remains — download Crumb and run its whole-Mac audit. The Visualize tab shows a treemap of what is actually occupying space, and the one-click Clean pass clears system caches, user caches, logs, and temp files in one operation. Crumb's "Is this safe to delete?" AI can also explain any unfamiliar folder before you remove it, which removes the guesswork from the categories above that sit between "probably fine" and "do not touch."
The free tier covers one cleanup, which is enough to benchmark how much space you can realistically recover.
What You Should Never Delete
While clearing space, avoid these locations regardless of their size:
/System/and/usr/— core macOS system files; deleting these can prevent your Mac from booting.~/Library/Keychains/— passwords and certificates; losing these locks you out of services.~/Library/Mail/— your local Mail database; deleting it removes offline copies of all your email.- Active Time Machine snapshots if you have no other backup.
- Any folder you cannot immediately identify; use Crumb's AI explainer or a quick web search before deleting.
Summary: Where the Space Is Hiding
- Trash not emptied — check all volumes, not just the main Trash.
- Purgeable space — run
sudo purgeto nudge macOS into releasing it. - Time Machine local snapshots — list with
tmutil listlocalsnapshots /, delete carefully. - iCloud local copies — right-click folders and choose Remove Download.
- App caches — check
~/Library/Caches/, clear by app while the app is closed. - Log files — safe to clear
~/Library/Logs/DiagnosticReports/. - App leftovers — hunt
~/Library/Application Support/and Containers for removed apps. - Stale storage graph — wait and use
df -h /for a live reading.
Work through this list in order and you will almost certainly recover meaningful space. The invisible culprits — purgeable space and local Time Machine snapshots — are where most people find the biggest surprises.