
Purge finds the junk and clears it.
Everything lands in the trash first.
brew install jithin-sabu/tap/purgeLogs, crash reports, old installers, font caches, and every per-app folder in ~/Library/Caches. macOS and your apps rebuild this stuff and almost never clean it up.
Every line is public. Read it, fork it, or ignore us and audit it yourself. See the repo.
For caches and junk, Purge only clears paths on its allowlist. Anything it doesn't recognize never shows up. Large Files is separate: you pick what goes.
Even the junk it clears goes to the trash, never wiped on the spot. Changed your mind? It's still sitting right there.
Purge can only reach paths on a fixed allowlist baked into the app. Everything else is off-limits. Whatever it removes goes to the trash, so you can put it back.
App and developer caches, leftovers from apps you remove, and large files or duplicates you pick yourself. Each item is marked Safe to clean or Check first. Clean only runs on the Safe ones.
No. Purge moves files to the trash. Emptying the trash is a separate action you take yourself.
Moving files to the trash doesn't free disk blocks. The space comes back when you empty the trash. Purge shows what's sitting in the trash so the number isn't a surprise.
Yes. No license, no trial, no paid tier, nothing bundled in. The full source is on GitHub if you want to read it.
No analytics, no telemetry, no crash reporting. The only network request it makes is checking for updates.
Purge is free, open source, and limited to a published allowlist you can read before you run it. It does one job. It doesn't upsell you when you're done.
Yes. macOS needs that permission before Purge can scan cache folders. You grant it in System Settings during onboarding, or later under Privacy & Security.
Drag Purge to the trash. If you turned on the optional login item for the menu bar companion, switch it off in System Settings under Login Items.