All posts

Why your Mac cleaner found 47 GB (and where it really went)

Open any Mac cleaner and it does the same trick: a spinner, a dramatic number — 47.3 GB of junk! — and a big button. The number is usually real. What’s missing is where it came from and what’s about to happen to it. So here’s the teardown, not as an accusation, just so you can read any of these tools — including sheersweep — with clearer eyes.

The big number

Most of that 47 GB is genuinely safe to remove: caches, logs, temp files your apps rebuild the moment they need them again. That’s the honest core of every cleaner. The number looks huge because it’s counting things that were always meant to be disposable — a browser cache that’s back to 2 GB by tomorrow afternoon.

The number isn’t the lie. The lie, when there is one, is in the two things the spinner glosses over.

The invisible delete

A cache cleaner deletes files. The question is which files, and whether you can see the list before it runs. A black-box cleaner answers “trust us” — the selection logic lives on a server, or behind a subscription, or just out of view. Most of the time it’s fine. The problem is you can’t tell the one time it isn’t, because you were never shown the list.

This is the only thing that actually matters when you evaluate a cleaner: can you see exactly what it will remove, before it removes anything? If the answer is a dry-run you can read, the rest is detail. If the answer is a percentage bar, you’re trusting a stranger with rm.

The thing almost none of them tell you

Here’s the genuinely useful bit, the one worth knowing even if you never touch a cleaner again: on modern Macs, deleting a file doesn’t always give you the space back.

APFS takes local snapshots — little point-in-time backups Time Machine leaves on your own disk. If a snapshot still references the file you just deleted, the space stays pinned until the snapshot expires. So you “clean” 30 GB, the bar says done, and your free space barely moves. People reinstall macOS over this. The fix is one command — tmutil thinning the local snapshots — and it’s the step most cleaners quietly skip, because it doesn’t photograph as well as a big number.

(If you want to see it yourself: tmutil listlocalsnapshots / shows what’s pinning your disk right now.)

So we wrote the boring one

None of this needs a black box. A Mac cleaner is, at heart, a list of cache paths and a find … -delete. So sheersweep is one shell script you can read end to end: it prints what it would free before freeing anything, it only clears things the OS rebuilds, it has a hard-coded list of things it will never touch, and yes — it releases the APFS snapshots and tells you it did.

No spinner, no 47 GB hero shot, no subscription. Just the same job, with the lid off. That’s the whole pitch, and you can verify every word of it by reading the source.

Keep reading

Notes from the workshop — the door is open.