Chippytea

Free up space on your Mac.

chippytea is an ultra-performant, native macOS app that clears space on your Mac. Built with SwiftUI and Rust, it helps you find app caches, developer tools, old build folders and downloads you may no longer need. Review their estimated sizes, see what removing them means, and choose what to keep or remove. SwiftUI + Rust · macOS 14+ · Free and open source

Build it · How it works · Contribute · Security

An illustrated cleanup, not a live scan. Animation respects reduced motion.

chippytea runs locally from your menu bar. No account, no telemetry, no automatic deletion.

How it works

• Find cleanup opportunities. Scan folders you choose, or use Scan my Mac for app and developer caches, logs, Xcode data, Python bytecode, build folders, downloads and large personal files. It also checks known system and tool-managed storage locations automatically.
• Check before you clean. Review the files, estimated size, and consequences. Git and activity checks vary by category; personal files and caches without an identified owning app still need your judgment.
• Choose what to remove. Move files to Trash, or permanently remove eligible developer caches, build files and dependencies. Review the outcome and any credited space in the cleanup history.

Check duplicate files compares already-indexed old/large personal-file suggestions when you ask. It verifies contents, lets you choose one copy to keep and one to review, and rechecks both before moving the selected copy to Trash. This is a bounded check, not a whole-Mac duplicate search; ordinary scans never hash personal-file contents.

Moving files to Trash does not free storage. App caches, logs, Python bytecode, Xcode DerivedData, downloads and personal files are review/Trash-only; they never earn chips. Verified developer caches, build files and dependencies can be deleted permanently after their ownership, activity and contents are rechecked.

Known npm, npx, Corepack, Bun, pip, uv, mise, Cargo, SwiftPM, Zig, Expo, Homebrew download and AWS CLI caches appear in the same cleanup list, with the same checkboxes and review action. Only recognized cache directories are eligible; active tools, shared files and unrelated configuration stay protected. Blocked caches stay in the list with their reason and cleanup disabled. Installed toolchains, container data and system locations appear alongside cleanup findings with their relevant review steps. Their measured size does not establish how much is removable; some system locations need administrator access.