macOS · Caches & Privacy
You cleared your history.
The cache did not.
Caches exist to make things fast, and they do it by keeping copies. Thumbnails of documents you opened once. Fragments of pages you visited. Query strings, filenames, previews. Clearing a browser’s history is one setting in one app, and it leaves most of this untouched.
Free to try, no account required.
What is actually in there
Browser caches outlive browser history
Clearing history removes the list. The cached page fragments, images and favicons are separate, and several browsers keep their own stores in their own places — Safari, Chrome, Firefox, Edge and Brave each with different retention.
Application caches hold previews of your documents
Quick Look thumbnails, recent-item previews and app-specific caches keep renderings of files. A document can be deleted while a readable thumbnail of its first page remains.
Logs record what ran, and when
User-level logs are a timeline of application activity. Individually dull; together, a fairly complete account of what you did on a machine and when you did it.
Deleting a cache is not erasing it
Moving cache files to the Trash and emptying it removes the names. The contents stay on the disk exactly as any other deleted file does, recoverable with free software — which is the whole reason this page is separate from the storage pages.
Clearing them properly
Every store, found rather than guessed
Browser caches across Safari, Chrome, Firefox, Edge and Brave; application and user caches; user logs and temporary files; and the developer and media caches that quietly accumulate — Xcode, npm, yarn, pip, Cargo, CocoaPods, Homebrew, Spotify, Slack, Discord, Zoom.
Rated by consequence
Each category carries a rating. Safe ones can go without thinking; conditional ones cost you something real — a slower next launch, a re-download — and are reported rather than swept up. Ones that would break something are not offered at all.
Sized before anything is removed
You see what each category holds before agreeing to it, so "clear my caches" is a decision rather than a leap.
Secure deletion, where it matters
For caches that are sensitive rather than merely large, the contents are overwritten and the name destroyed before the entry is unlinked — instead of leaving the data in place and the name in an index.
Free-space overwriting for what is already gone
Caches you cleared months ago are still recoverable from unallocated space. Overwriting free space is what addresses the history rather than today’s files.
Refusals are reported
Anything protected or out of reach is named as refused rather than counted as cleared. A privacy tool that overstates what it removed is worse than none, because you stop checking.
What it does not do yet
- — On APFS, overwriting a file in place cannot guarantee the original blocks were reused — the filesystem may write elsewhere. Where a cache is genuinely sensitive, overwriting free space afterwards does more than pass counts do.
- — Local snapshots may hold their own copies of what you cleared. Thin the snapshots if the history itself is what you need gone.
- — Cloud-synced application data is out of reach. A cache cleared locally may persist in an account you signed into, and no local tool can see that.
- — System-level caches need the privileged helper installed. Without it, everything user-level still works, and that is where the disclosure risk mostly sits anyway.
Questions people ask
Will clearing caches slow my Mac down?
Briefly and specifically. A browser cache means slower first loads of sites you visit often; a developer cache means a slower next build. Both rebuild themselves. That is exactly why categories are rated rather than cleared wholesale.
Is this the same as clearing my browser history?
No, and that is the point. History is a list one app keeps. Caches are copies of content, kept by many apps in many places, and they survive the history being cleared.
Do I need to overwrite cache files, or is deleting enough?
Deleting is enough for space. It is not enough for privacy — the contents stay on the disk until something reuses the blocks. If the reason you are clearing caches is that someone might look, overwrite them.
What about the caches I cleared last year?
Still potentially recoverable from unallocated space. Overwriting free space is the step that addresses everything deleted before you started caring, and it is the one most people skip.
Try it on your own files
One purchase, no subscription. $24.99 once, and every feature is included.