Why is my Mac storage full when I deleted everything?

You cleared out Downloads. You dragged a couple of apps to the Trash. Maybe you deleted a whole folder of old video. Then you opened Storage settings and the bar barely moved, or moved by a fraction of what you deleted. If you're asking why is my Mac storage full when you just deleted everything, the short version is that the space you freed and the space macOS reports are not the same thing. Several culprits keep holding blocks you can't see, and most of them aren't things you can delete by hand.

Here's each one: what it is, where it lives, and where to go to actually fix it.

Why is my Mac storage full right after deleting files?

Because on an APFS disk, deleting a file doesn't always hand the space straight back. Two mechanics get in the way.

• Local snapshots still point at the "deleted" file. When Time Machine (or a macOS update) takes a local snapshot, APFS keeps the original blocks of anything you change or delete afterward, for as long as that snapshot exists. So the file is gone from Finder, but its blocks are retained. macOS is supposed to clean this up on its own (snapshots older than 24 hours auto-delete, and more get removed when the disk runs low), but until then, the space stays occupied.
• Freed space becomes "purgeable," not free. Purgeable is Apple's word for space macOS will release on demand when it needs it; you can't delete it yourself. Exactly what counts as purgeable is murky enough that macOS-internals experts openly disagree about it, which is its own tell. One researcher caught Finder reporting 83.71 GB purgeable when the real amount macOS could free was 0 GB.

That's the whole reason the numbers don't move the way you expect. For the full mechanic (snapshots, purgeable space, and why Finder, df, and du never agree), see purgeable space.

"System Data": the slab you can't delete directly

Open Apple menu → System Settings → General → Storage and you'll see a fat grey block labeled System Data. It isn't a folder. It's a catch-all, "everything macOS couldn't sort" into Apps, Photos, or Documents, described by the people who study it as little more than a rough estimate. It's where the caches, logs, local snapshots, and leftover app data all get swept together.

The frustrating part is that Apple tells you outright you "can't directly manage the contents of this category." It commonly runs anywhere from tens of GB to over 100 GB; people post to Apple's own forums with 218 GB sitting in there. What's actually inside it, and which parts are safe to touch, is its own topic: System Data.

The Trash you didn't actually empty

The simplest culprit, and the easiest to miss. Dragging a file to the Trash doesn't free anything; the space isn't returned until you empty it. Delete 30 GB, forget the Trash, and Storage settings will keep counting all 30 GB as used.

Empty it (Finder → Empty Trash), or turn on Empty Trash automatically in Storage settings to clear anything older than 30 days. Note the snapshot caveat above: even after emptying, blocks referenced by a local snapshot won't come back until macOS thins that snapshot.

Old iPhone and iPad backups

If you've ever backed up a phone to this Mac, those backups live at:

~/Library/Application Support/MobileSync/Backup/

Each one can be tens of GB, they pile up (old devices, old backups), and they land inside System Data where you'd never spot them. This is often the single biggest quick win, but delete the wrong one and you lose a restore point. The safe way to view and remove them (Finder → device → Manage Backups, which labels each by device and date) is covered in how to actually free space.

Your Photos library

For most non-developers, this is where the real gigabytes are, and video is the hog. A Photos library at ~/Pictures/Photos Library.photoslibrary can quietly grow to a large share of the disk, and deleting individual shots barely dents it.

The low-risk fix is to turn on iCloud Photos with Optimise Mac Storage, which keeps full-resolution originals in iCloud and only recent files on the Mac (it needs enough iCloud space to hold the library). Big video projects are usually better moved to an external drive. Both approaches are in the how to actually free space guide.

If you write code: a full disk on another scale

Developer machines hide storage in a category of their own; this is where 20 GB becomes 100.

• node_modules graveyards: hundreds of MB per project, multiplied across every repo you've ever cloned and forgotten.
• Xcode: DerivedData, simulators, and per-version device support commonly total 20–50 GB, and none of it is obvious.
• Docker.raw: Docker's Linux VM is one big file that grows as you add images but doesn't shrink when you delete them. One documented case: 67 GB on disk for 15–20 GB of actual content.

None of this shows up as anything but "System Data." The full inventory, with exact paths and the commands to find each one, is in the full hidden-storage map.

So what actually clears it

Start where Apple points you: System Settings → General → Storage, read the bar and the Recommendations block, and empty the Trash first. Then work down from the safe, high-payoff wins (old iOS backups, offloaded Photos, properly uninstalled apps) rather than fighting the parts macOS owns (snapshots, purgeable space, System Data), which it thins on its own and which you can't safely delete by hand. The ordered, low-risk walkthrough is how to actually free space; the complete map of every hiding place is the full hidden-storage map.

The honest catch is that doing this by hand means cross-checking numbers that don't agree, digging through a hidden folder, and hoping you delete the right backup. That's the job Plumby is built for. It names every piece of your used space with exact paths, reconciles the gap between what Finder, df, and du each claim, and clears only what's safe. Freed space is measured as each item goes, and it never touches your documents, photos, or projects. Your Mac won't tell you where the space went. Something should.