Mac Storage Full but Nothing to Delete? Find the Hidden Files

You open Finder, look around, and nothing seems out of place — yet macOS is telling you the disk is nearly full. The maddening part is that mac storage full but nothing to delete is one of the most common complaints from Mac users, and it almost always has the same cause: the space is there, but it is hidden behind paths Finder never shows you. This guide walks through exactly where to look and how to reclaim that space safely.

Why Finder Hides the Files Eating Your Disk

Finder deliberately hides several categories of files to protect users from accidentally deleting things macOS needs. The problem is that some of those protected directories balloon over time and never clean themselves up. The three main culprits are:

• System Data / Other Storage — the catch-all bucket in About This Mac → Storage that includes caches, logs, temporary files, and purgeable content.
• App containers and support files — stored in ~/Library/, which is hidden from Finder by default.
• iOS device backups and Xcode caches — can silently consume tens of gigabytes.

Because Finder's default view starts at your home folder and hides ~/Library/, you can have 40 GB of cache files you have never seen.

How to Reveal Your Hidden Library Folder

Before you can clean anything, you need to see it. There are two quick ways to open the hidden Library folder:

1. In Finder, open the Go menu and hold Option. A Library item appears in the list. Click it.
2. Use Go → Go to Folder… (⌘ Shift G) and type ~/Library, then press Return.

Once you are inside ~/Library, you will find directories like Caches, Application Support, Containers, and Logs. These are the main places to investigate.

The Most Common Hidden Space Hogs on macOS

1. User and System Caches

Apps write cache data to speed up their next launch. Over months or years this accumulates without any automatic pruning. The paths to check:

• ~/Library/Caches/ — per-user app caches (generally safe to delete; apps rebuild them)
• /Library/Caches/ — system-wide caches (safe for most entries; avoid deleting entries you do not recognise)

To see which subdirectory is largest, open Terminal and run:

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

This lists the 20 largest cache folders, sorted by size. A single app like Xcode, Slack, or a browser can account for several gigabytes on its own.

2. iOS and iPhone Backups

Every time you backed up an iPhone or iPad to your Mac (via Finder or the old iTunes), a full device backup was written to:

~/Library/Application Support/MobileSync/Backup/

These backups are compressed but still large — a 256 GB device backup is typically 20–80 GB. You can manage them in Finder → your device → Manage Backups, or delete the folders directly after confirming you no longer need them. Deleting a backup is permanent and not recoverable, so make sure you have a current iCloud backup before removing anything.

3. Xcode Derived Data and Archives

If you have ever installed Xcode, its build artefacts accumulate rapidly:

• ~/Library/Developer/Xcode/DerivedData/ — intermediate build files; safe to delete, Xcode rebuilds them
• ~/Library/Developer/Xcode/Archives/ — app archives for distribution; only delete if you no longer need to re-sign or submit those builds
• ~/Library/Caches/com.apple.dt.Xcode/ — Xcode's own cache

DerivedData alone can exceed 30 GB on an active development machine.

4. App Containers and Orphaned Support Files

Sandboxed apps write data to ~/Library/Containers/. When you drag an app to the Trash, this container is usually left behind — orphaned, consuming space, and invisible in Finder. The same applies to ~/Library/Application Support/ entries from long-deleted apps.

To find large containers quickly:

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

5. Mail Downloads and Attachments

Apple Mail stores every attachment you have ever opened in:

~/Library/Mail/

This folder can grow to several gigabytes without ever appearing in a Finder search. You can remove old attachments inside Mail by selecting messages and choosing Message → Remove Attachments, or delete the Attachments subfolder directly — though the latter will remove offline copies permanently.

6. Log Files

macOS and third-party apps write diagnostic logs continuously. They live at:

• ~/Library/Logs/
• /Library/Logs/
• /var/log/

Logs are safe to delete in most cases. If you are troubleshooting an app crash, save the relevant log first, then clear the rest.

Using a Disk Map to Find What You Cannot Name

Terminal commands help once you know which folder to query, but if you have no idea where the space went, a visual treemap is far more effective. A treemap renders every file as a rectangle proportional to its size, letting you spot a 15 GB folder at a glance without knowing its name in advance.

Crumb's Visualize view does exactly this: it maps your entire drive, including hidden Library paths and system volumes, and lets you click into any block to identify it. Its whole-Mac audit also surfaces the largest items across all user accounts — useful on shared Macs where another account's data is invisible in your own Finder. If you are unsure whether something is safe to remove, the built-in "Is this safe to delete?" feature explains what any folder does before you act.

For readers who prefer a pure command-line approach, ncdu (installable via Homebrew) gives an interactive terminal treemap:

brew install ncdu
ncdu /

Navigate with arrow keys, press d to delete. Be careful at the root level — deleting system paths can make macOS unbootable.

The "System Data" Category Explained

In Apple Menu → System Settings → General → Storage, you will often see a large System Data or Other bar. This is not a single folder you can open. It is macOS's aggregate of:

• Purgeable content (APFS space reclaimed by the OS under pressure)
• Time Machine local snapshots
• Virtual machine disk images
• Files in hidden system volumes

Local Time Machine snapshots are managed automatically — macOS purges them when space is needed — but if you want to remove them immediately:

tmutil listlocalsnapshots /
tmutil deletelocalsnapshots [snapshot-date]

Replace [snapshot-date] with the date string shown by listlocalsnapshots, e.g. 2025-11-14-083012.

A Quick Reference: Safe vs. Careful

Putting It Together: A Step-by-Step Search

1. Open System Settings → General → Storage and note which category is largest.
2. Run du -sh ~/Library/Caches/* | sort -rh | head -20 in Terminal to find top cache consumers.
3. Check ~/Library/Application Support/MobileSync/Backup/ for old device backups.
4. If you use Xcode, inspect ~/Library/Developer/Xcode/DerivedData/.
5. Use a treemap tool — either ncdu / in Terminal or download Crumb for a visual, clickable map that covers hidden paths automatically — to find anything the above steps missed.
6. Before deleting anything unfamiliar, search its name online or use an "explain this folder" tool to confirm it is safe.

Conclusion

When your Mac storage is full but nothing seems to be there, the files are almost always hiding in ~/Library/ — caches, backups, Xcode artefacts, and orphaned app containers that Finder never surfaces. A combination of targeted Terminal commands and a disk treemap will locate the culprits in minutes. Delete what is clearly safe, be cautious with anything you do not recognise, and your disk will have breathing room again without touching anything you actually care about.