CleanBit: The Mac Cleaner That Explains Every Byte Before It Deletes
Use Mac people, most have experienced the same moment:
A popup "Disk space almost full" appears in the bottom right, click "About This Mac → Storage", look at the gray "System Data" which is tens or even hundreds of GB, and you have no idea - what exactly is filling up the hard drive?
What makes people more hesitant is the interaction of many cleaning tools on the market:
After scanning, they tell you "Found 58 GB of junk", and below there is only a huge "One-click clean". As for whether there is a dependency from an old project, a just-downloaded installer, or a cache of some tool, and whether the environment will break after deletion, often you can only guess.
Another concern: to clean tens of GB of cache, you have to grant full disk high-risk permissions, and even endure a family bucket of background residency and complex settings.
So we made CleanBit.
It is a disk cleanup assistant based on SwiftUI native development, running in the macOS 15+ system sandbox. Its core principle is only one sentence:
Every item is clearly explained: what it is and what impact deletion has; nothing is deleted before you confirm.
01 Smart Scan: Distinguish "Recommended to clean", "Careful", and "Don't touch" at a glance
When you open CleanBit's Smart Scan, you don't see a vague "total junk" number, but a list with its own instructions.
[Image]
Scanning covers four high-frequency scenarios:
- Daily system and browser caches: app caches, app logs older than 7 days, Quick Look thumbnails, window states older than 30 days, incomplete downloads, and browser caches for Safari, Chrome, Edge, Brave, Arc, Vivaldi, Firefox. Cookies, browsing history, and passwords are never touched.
- Download directory and uninstall residuals: Old installers like
.dmg,.pkg,.iso,.xip, and data left by deleted apps in directories likeApplication Support,Containers,Preferences. - Developer tool caches: Xcode DerivedData, old DeviceSupport for various platforms (automatically keeps the latest 2 versions), SwiftUI preview data, simulator caches for shut down simulators, and caches for npm, Yarn, pnpm, Bun, pip, uv, SwiftPM, CocoaPods, Homebrew, Go, Cargo, Gradle.
- AI tool caches and local model recognition: Automatically identifies old versions of Claude Code (keeps the currently used version and the latest version) and Claude desktop cache; while local large models from Hugging Face, Ollama, LM Studio, PyTorch, as well as Docker virtual machine images and pnpm store, are clearly marked with their sizes in the scan.
More importantly, scan results are classified into three risk categories, never conflated:
- Recommended to clean (green, default checked): Pure caches that are automatically rebuilt after deletion; after cleaning, space is freed immediately (if you prefer to stage first, you can change to move to Trash in settings).
- Needs confirmation (yellow, default unchecked): Items that might still be useful, such as Xcode Archives, old installers, app residuals. Even if checked, they are always moved to the Trash, and you can "Put Back" at any time.
- Display only (gray, cannot check): Important assets like local large models, Docker images, pnpm store. They only help you see where the space went, and you won't accidentally delete them.
For rules or directories you don't want to see again, just click "Never clean this category" or hover over an item and set it to "Never clean"; if you only want to quickly deal with a group, you can also click the clean icon on the right of the group to handle it alone.
02 Putting "Restraint" in Code: 6 Layers of Review Before Deletion
Many cleaning tool accidents happen during the few minutes between "scan finished, you go get a glass of water, come back and click confirm", or by accidentally touching cloud sync directories.
CleanBit converges all cleaning actions to a single safe exit, and checks thoroughly before actual deletion:
[Image]
- Path and symlink boundary check: After resolving the real path, it confirms again that it is still within the root directory of the target rule, and never affects anything outside your personal folder or system directories.
- File identity (inode) confirmation: Checks device number and inode to ensure that the target file has not been replaced by another process while waiting for your confirmation.
- iCloud Drive and library package protection: If a sandboxed app directly deletes files in iCloud sync directories, it can cause multi-device sync loss. CleanBit automatically blocks items in cloud drives and lets you handle them in Finder; it also prohibits deleting the internal structure of libraries like
.photoslibrary,.musiclibrary,.fcpbundle. - Running apps and simulator lock: If an app is currently running (like Slack or Xcode), a simulator hasn't been shut down, or an
_npxcommand is executing, related caches are grayed out and disabled in the list, and will be re-checked before deletion. - Git tracking and recent write guard: Rules in development directories automatically skip content tracked by Git, and items with recent writes are locked by default.
- Built-in "Dry Run": If you are naturally cautious with new tools, you can enable Dry Run in settings. It will fully go through scanning, confirmation, and generating a cleaning report, but won't actually delete a single file, suitable for getting to know the tool on first use.
The confirmation box that pops up when clicking "Clean" also calculates the account clearly: how many move to Trash (recoverable), how many are deleted directly (automatically rebuilt), listed separately, at a glance.
[Image]
03 Two "Workbenches" Tailored for Developers and Heavy AI Users
Beyond ordinary caches, what really eats tens of GB for developers and AI practitioners are often build artifacts scattered in various project directories, and accumulated local AI conversation records.
CleanBit splits these two types of scans into separate pages, not forcing them into Smart Scan:
Project Artifacts
Automatically scans the big chunks in development directories that "can be reinstalled or recompiled at any time": node_modules, target, .build, .venv, Pods, .next, etc., and clearly marks each project's last modified time.
[Image]
A landing page untouched for two years has 1.1 GB node_modules, a Rust project from a few months ago has 3.2 GB target - you can see at a glance which to clean. Content tracked by Git is always skipped, and projects "recently written, possibly in use" are automatically unchecked to prevent deleting an environment you're actively developing in.
AI Sessions
If you heavily use Claude Code or Codex, your local directory often accumulates hundreds or thousands of .jsonl history conversation files, which can add up to several GB over time.
[Image]
On the AI Sessions page, you can set your own time range (e.g., only old sessions from 90 days ago), scan only history conversation files (not touching memory directories like memory), and all cleaning moves them to Trash, so you can still retrieve them when needed.
04 See Where Space Goes: Space Analysis, Large Files, Duplicate Files
Besides cleaning known rules, often we just want to know: "Who is occupying my hard drive?"
CleanBit provides three handy tools under the sidebar "Space" group:
Space Analysis: A Tree Map, Drilling Down Layer by Layer
Uses a rectangle tree map (Treemap) with a directory list on the right, supports clicking any folder to drill down layer by layer, covering your personal folder or any directory you authorize.
[Image]
The underlying statistics support hard link deduplication, so the same hard link is not counted twice, making total usage closer to real disk consumption.
Large Files: List Files That Are "Big and Long Unused"
Combining with macOS Spotlight index, filter by file size threshold and last opened time (unlimited / 3 months / half a year / 1 year). A .xip that was unzipped half a year ago and forgotten, an old system image, or temporary 4K footage exported, you can quickly spot and move to Trash.
[Image]
Duplicate Files: Compare Only by Content Hash, Keep at Least One of Each Group
Don't guess duplicates by filename. First filter by size, then compute checksums, only list files that are byte-for-byte identical. You can choose "Keep earliest" or "Keep latest" with one click, and the system forces each group keeps at least one, so you'll never delete all copies including the only original.
[Image]
05 Uninstall Apps: Clean Residuals Too, but Don't Touch Your Personal Data by Default
Dragging a .app to Trash is often just the beginning of uninstalling - caches, logs, update packages, HTTP storage, WebKit data remain in corners.
On CleanBit's Uninstall Apps page, after selecting an app, it not only lists the app itself, but also finds associated caches, logs, preferences, window states, containers, and update residuals.
[Image]
But here's a detail we insist on: by default, only the app itself, caches, and logs are checked.
Preferences, window states, cookies, app data - these "may contain personal data" items are all unchecked by default, and you must actively decide whether to take them along; all uninstalled items are moved to Trash, not erased directly.
Even deeper is shared data protection: if you have multiple copies of the same app, versions with the same name, or associated sub-products on your computer, CleanBit recognizes this shared relationship in the list and pre-deletion review, automatically keeps shared data, only handles the main app, avoiding deleting the production config when you uninstall a test version.
06 Native Sandbox, Privacy Bottom Line, and a Bit of Design Obsession
The reason for running entirely in the macOS system sandbox is that we want boundaries to be clear:
- Three levels of minimal permissions: You only need to authorize your personal folder in the system file panel to use most cleaning functions; full disk access is optional (only recommended when cleaning Trash, Safari and other app container caches); the "Applications" folder is only requested when uninstalling apps.
- Sandbox permission diagnostics: In "Settings → Diagnostics", you can click any time to run a test of the current sandbox access boundaries, everything is transparent.
- Data stays local: Your filenames, folder paths, file contents, installed app list never leave your Mac. CleanBit has no account system, and doesn't use your personal files for push or ads.
In terms of interaction and visual design, CleanBit doesn't use the mediocre default system list, but builds a custom interface around the "bit" motif:
A disk is made up of bits; cleaning is zeroing out unnecessary bits - dot matrix backgrounds, 0/1 square checkboxes, a tick ring representing disk usage, and theme colors that flow with functional modules.
[Image]
You can choose the quiet Midnight, the bright and transparent Daylight, the color-changing Aurora, or let it follow the system to switch automatically between day and night. If you want to keep an eye on disk space at any time, you can enable the menu bar view and low space alerts on demand (stops when you quit the app, no background residency burden).
07 Finally: Making Cleaning a Transparent Thing
The original intention of making CleanBit is simple: cleaning your disk should not be a blind box lottery.
Compared to the thrill of "one-click delete all", we care more about whether you truly see what each item is, whether deleting it will affect your current projects, and whether the deleted things can still be recovered.
If your Mac's hard drive is running low again, whether you want to understand the ins and outs of that tens of GB of "System Data", or want a cleaning assistant that doesn't interrupt your workflow and is tailored for macOS 15+ and modern development/AI tool environments, CleanBit's "Dry Run" and "Space Analysis" are suitable for first getting to know what you have.
After all, seeing where space goes is itself a reassuring thing.
Top 2 from juejin.cn, machine-translated. The original thread is authoritative.
Reader perk: claim a free lifetime membership redeem code on the App Store: https://apps.apple.com/redeem/?ctx=offercodes&id=6829159531&code=CLEANBIT
Like