Why a disk cleaner should show you the plan before it deletes anything
· 7 min read
Disk cleaners on the Mac are neither the menace nor the necessity they are usually presented as. What separates a safe one from a risky one is a single property: whether you see an itemized list of what it intends to remove, and approve it, before anything is deleted.
A cleaner that presents a number and a button is asking you to trust its judgment about files it has not explained. A cleaner that presents a list is asking you to make the decision, which is the only arrangement that survives an unusual setup. The interface, the categories and the price matter much less.
What actually goes wrong
The failures are rarely dramatic. Almost nobody’s Mac is destroyed by a cleaner. What happens instead is a slow, hard-to-attribute mess:
Work goes missing that was never a cache. Plenty of apps keep genuine data in folders a naive scanner reads as disposable: local databases, offline copies, drafts, message history, license files. If the tool decides by folder name, some of that goes.
Things get slower, not faster. Caches exist because regenerating them is expensive. Deleting a browser cache, a font cache and an icon cache in one pass means the next few hours are spent rebuilding all three. The disk is emptier and the Mac is worse.
Space comes back within days. Most cache categories refill during ordinary use. If the cleaner does not say which categories regenerate, you cannot tell the durable wins from the temporary ones.
Sign-ins and settings reset. Container and preference folders sit next to cache folders, and clearing too broadly logs you out of things.
None of these announce themselves at the moment of deletion. That is why the review step is not decoration.
Cache, app data and leftovers are three different things
Any tool worth running distinguishes between them, and any article worth reading tells you the difference.
Cache is a local copy of something that can be produced again: thumbnails, compiled shaders, downloaded package archives, rendered previews. Deleting it costs time and nothing else.
Application support data is the app’s actual state. It lives in similar-looking places, ~/Library/Application Support and ~/Library/Containers, and deleting it is deleting your data. A tool that treats these as the same category should be closed.
Leftovers are files belonging to apps that are no longer installed: preferences, support folders, launch agents, logs. These are genuinely free space and the most defensible thing a cleaner removes, because the app that owned them is gone.
Which caches are safe to delete on a Mac goes through the specific folders and which ones bite.
What macOS already does for you
Say it plainly: for a lot of Macs, no cleaner is needed at all.
- Storage recommendations. System Settings, General, Storage offers to empty the Trash after 30 days, store files in iCloud, and review large files.
- Purgeable space. macOS already reclaims caches and snapshots on demand when the disk gets tight, which is why the free space figure is frequently more pessimistic than reality.
- Per-app storage. The same panel breaks usage down by application and by category.
- Snapshot thinning. Time Machine’s local snapshots are managed automatically and deleted under pressure.
Where macOS falls short is visibility. It presents a large opaque category called System Data with almost no help identifying what is in it, and it does not look outside your own account. That gap is the honest reason people install a cleaner, and a reason to want an auditor more than a deleter. What System Data is on a Mac covers doing that part by hand.
A checklist for judging one
Before you run any cleaner, including one you have used for years, check these. They are observable in the first five minutes.
- Does the scan change anything? A first pass should be read-only. If a scan and a cleanup are the same action, there is no review step by definition.
- Does it itemize? Not “4.2 GB of caches” but the actual paths, grouped, with sizes, that you can expand and untick.
- Does it explain what an item is? The useful question about any file is whether it regenerates and what stops working without it. A tool that cannot answer that is asking you to guess.
- Can you undo? Recoverable removals should be reviewable afterwards, and the tool should say plainly which deletions are not.
- Does it run unattended? A background agent deleting on a schedule has removed the review step permanently. Check Login Items in System Settings.
- Is it signed and notarized, and does it say why it wants Full Disk Access? Seeing the whole disk is legitimate for a whole-Mac audit. Asking without a reason is not.
- Does anything leave the Mac? File contents should never be uploaded. Nor should a list of your file paths, which is nearly as revealing.
- Does it use pressure? Warnings about your Mac being at risk, countdowns, or a scan that will not show results without a subscription are all the same signal.
A tool that passes all eight is safe in the only sense that matters: you are the one deciding.
Where a cleaner earns its place
Two situations, in practice.
The first is when the disk is full and you cannot find why. The parts Finder never shows you, local snapshots, other user accounts, container disk images, swap, backups for devices you no longer own, are what an audit is good at surfacing. Finding the answer is most of the work.
The second is the repetitive jobs: pairing an uninstalled app with its leftovers, finding byte-identical copies across a disk, sorting a folder of five thousand downloads by type. Tedious by hand, mechanical for software.
Crumb is built on the property this article is about: the audit is read-only and covers the whole Mac, and nothing is deleted until you approve the plan, with reclaimable removals reviewable afterwards. Be equally clear about the limits: it does not repair disks and does not recover deleted files, so the review step is the safety net rather than a formality. The audit and one full cleanup are free.
What no cleaner can do
Recover a file it removed a week ago. Once a file is gone from the disk and outside any snapshot or backup, no cleaner brings it back. This is the argument for having a backup before a cleanup rather than after.
Make an old Mac fast. Free space helps when the disk is nearly full, because macOS needs room to swap and to write temporary files. Past that, cleaning is not a performance intervention, and a tool that markets it as one is selling something else. A disk with actual errors is a job for First Aid in Disk Utility, which is a different problem entirely.
Decide what your files are worth. A duplicate finder cannot tell which copy of a folder is the one your accountant needs. Finding duplicate files without deleting the wrong copy covers where that goes wrong.
Questions
Is it safe to use a Mac cleaner at all? Yes, if it audits before it deletes and shows you the list. Judge the specific app by the checklist above rather than the category by its reputation.
Do I need one if I am careful? No. Everything a cleaner does can be done with Finder, Terminal and patience. What you are buying is the audit that tells you where to point that patience.
Should I back up before running one? Yes, and it costs nothing if Time Machine is already running. Check the backup is current rather than assuming it.
Is clearing caches worth doing regularly? No. Clearing them on a schedule means paying the rebuild cost repeatedly for space that returns anyway. Clear them when you need space today, not as maintenance.