Take back your disk from build junk.
Xcode, Node, Gradle and friends quietly fill a Mac with gigabytes of regenerable files. The Developer tab finds them, tells you which are safe to rebuild, and moves them to the Trash — without ever touching your source code.
Download Free for MacWhat it finds
Seven toolchains — every artifact your tools rebuild on their own.
Xcode
DerivedData, Archives, iOS/watchOS DeviceSupport, simulator caches
Rebuilt on the next build or device connection
JavaScript / Node
node_modules, .next build cache, npm, Yarn and pnpm caches
npm install, yarn or pnpm install
Swift
.build folders, Swift Package Manager cache, CocoaPods Pods and cache
swift build, pod install
Rust
Cargo target folders and the registry cache
cargo build
Python
Virtual environments (.venv, venv) and the pip cache
Recreate with python -m venv, reinstall requirements
Java / Gradle / Android
Gradle build output and the Gradle cache
The next Gradle build
Homebrew & Go
Homebrew downloads and the Go build cache
Fetched again on demand
Built so you never lose work
Project-aware, not path-guessing
A node_modules, target or build folder is only listed when its manifest (package.json, Cargo.toml, Podfile, build.gradle…) sits right next to it. Source code and .git folders are never candidates.
"Safe to rebuild" vs "Review first"
Anything from a project you touched in the last two weeks, Xcode archives you may have shipped, and DerivedData while Xcode is open are labelled Review first and left unselected.
Trash first, always
Everything is moved to the Trash rather than erased, so you can put it back. Your tools regenerate the rest automatically.
Fast and local
Scanning runs entirely on your Mac. No file names or paths are uploaded anywhere.
Free to scan, fair to keep
- Scan everything — always free
- Clean up to 2 GB free (lifetime)
- Pro: $12.99 once removes the limit, no subscription
- Universal app: Apple Silicon and Intel
Frequently asked questions
Is it safe to delete node_modules?
Yes. node_modules is fully regenerated by npm, Yarn or pnpm from your lockfile. MacDiskCleaner only lists it when a package.json sits next to it, marks recently used projects as Review first, and moves it to the Trash so it stays recoverable.
Can I delete Xcode DerivedData?
Yes. DerivedData holds build products and indexes that Xcode recreates; the first build afterwards is slower. Quit Xcode first — MacDiskCleaner warns you if it is running.
Should I delete Xcode Archives?
Only ones you no longer need. Archives are what you need to symbolicate crash logs for builds you shipped, so MacDiskCleaner labels them Review first and never pre-selects them.
Does it clean Docker?
It shows how much space Docker images, containers and build cache use (read-only) and the command to reclaim it. It never deletes Docker data itself, because that must go through Docker.
Will it touch my source code or git history?
No. It only targets dependency folders, build output and tool caches, each verified against a sibling manifest file. .git folders and source files are never candidates.
Is the Developer tab free?
Scanning is always free. Like every cleanup, removal counts toward the 2 GB free allowance; Pro ($12.99 one-time) removes the limit.
Ready to clean up your Mac?
Free to download. No account required to start.
Version 1.1.2 · 4.8 MB · macOS 14 or later · Apple Silicon & Intel