What is purgeable space on Mac?
Purgeable space on Mac is storage macOS frees up automatically when it needs room: caches, Spotlight indexes, and local snapshots you can't delete yourself.

Purgeable space on Mac is storage macOS keeps in reserve, space it will free up automatically the moment it needs the room. You can't delete it yourself, and you're not supposed to. It's not junk you forgot to clean. It's macOS holding onto data it thinks is still useful, ready to drop the second the disk gets tight.
What purgeable space on Mac actually means
Apple's definition is narrow: purgeable is "space that macOS can free up when needed by removing files from your computer." The key word is macOS; you can't manually delete purgeable files. Only the system can.
What lives in it, according to how macOS actually manages storage:
- OS-controlled caches: data macOS keeps around while there's room to spare, and discards when there isn't.
- Spotlight indexes: the search database, rebuildable on demand.
- Version databases: the local history apps keep for macOS document versioning.
- APFS local snapshots: in common usage, though this one is disputed (more below).
The common thread: everything in the purgeable bucket is reconstructable or disposable. macOS keeps it as a convenience and treats it as expendable. That's why it can promise to give the space back without asking you first.
APFS local snapshots: the part most people mean
When people say "purgeable space," they usually picture snapshots, so it's worth understanding them on their own.
When Time Machine (or a macOS updater) takes a local snapshot, APFS doesn't copy your files. It freezes the current state of the filesystem by copying only metadata, so it's fast and nothing is duplicated at that moment. The cost comes later: as you change files afterward, their original blocks have to be kept as long as the snapshot references them. That quiet retention is what consumes space.
Because snapshots share blocks, a group of them is smaller than the sum of each measured alone, and a snapshot of a disk that hasn't changed costs almost nothing. But over days of edits, they add up.
macOS is meant to manage them for you: snapshots older than 24 hours are automatically deleted, snapshots are only kept on disks with plenty of free space, and when space runs low, more get deleted starting with the oldest. You can list the ones currently on your boot volume:
tmutil listlocalsnapshots /
That command shows you what exists. It does not, on its own, tell you how much space they're actually costing, which brings us to the messy part.
Is purgeable space the same as snapshots?
Short answer: not exactly, and the experts disagree.
Cleaner-app documentation tends to say purgeable space "mostly consists of local snapshots." But the most rigorous independent analysis, Howard Oakley at The Eclectic Light Company, argues the opposite. He documents a Mac carrying 9 GB of snapshots while reporting 0 GB purgeable, because Apple appears to count snapshots as used space, not purgeable. In his reading, genuine purgeable space is the OS-controlled caches, Spotlight indexes, and version databases, not the snapshots at all.
So don't trust a tidy "purgeable = snapshots" equation. When the people who reverse-engineer this for a living can't reconcile the number, the honest takeaway is that the figure is murky by nature. Finder makes it worse: it has been caught reporting 83.71 GB purgeable on a volume where the real purgeable amount was 0 GB. For the full breakdown of why the numbers lie, see why your Mac lies about free space.
How do I remove purgeable space on Mac?
You don't, at least not directly. That's the whole design. Purgeable space is, by definition, controlled by macOS. There's no "delete purgeable" button, and manually hunting down snapshots is a good way to break Time Machine's local restore points.
What actually works is the indirect route:
- Free up real space. Empty the Trash, delete large files you don't need, and clear the caches you do control (the per-user ones in
~/Library/Caches). - Let macOS reclaim the rest. When the disk gets tight, the system deletes old snapshots and caches to make room, automatically, and usually within minutes of you needing the space.
If your disk is actually full and macOS isn't freeing space, the problem is almost never the purgeable figure itself. It's real files sitting in System Data or elsewhere. The full diagnosis of a jammed disk is in why your storage is full.
See your real free space instead of guessing
Rather than staring at a purgeable number nobody can define, measure what's actually free.
In the GUI: open Disk Utility (Applications → Utilities) and select the APFS container in the sidebar, the top-level item, not the volume beneath it. The container view shows true free space. If you select the volume instead, you get free space with the purgeable amount in brackets, described by Apple as "the maximum space that could be freed if all purgeable contents were to be deleted," an upper bound, not a promise.
In the Terminal, if you prefer:
df -h /
df reports what the filesystem itself says is used and available at the container level, which is the most trustworthy quick answer. Finder's figures, by contrast, are frequently just wrong; they don't count snapshots the way the filesystem does, so treat anything Finder tells you about free space with suspicion.
The honest bottom line
Purgeable space is macOS keeping a reserve it will spend on your behalf. You can watch it (tmutil listlocalsnapshots /), you can measure around it (df -h / or Disk Utility's container view), but you can't reach in and delete it, and the exact size is disputed even among the people who study it. The right move is almost always to free up real space and let the system do the reclaiming it already promises to do.
Sorting "reclaimable by you" from "reserved by macOS" by hand means cross-checking Disk Utility against df against Finder and hoping you read the right one. Plumby does that reconciliation for you. It shows what's actually yours to clear versus what macOS controls and will free on its own, names the exact paths, and never guesses at a number it can't measure. It won't pretend it can delete purgeable space; nothing can. It just shows you where the space that is yours to reclaim actually sits.


