Xcode DerivedData Cleaner for Mac
Last updated: 2026-06-05
Quick answer
You can delete Xcode DerivedData on Mac from ~/Library/Developer/Xcode/DerivedData. It is regenerated by Xcode, but the next build may be slower. CodeCleaner can scan this folder, show per-project sizes, and let you remove selected DerivedData safely.
Native macOS app. No account required. Local scan. You review before cleanup.
Xcode DerivedData stores build products, module caches, and indexing data for every project you open. It lives at ~/Library/Developer/Xcode/DerivedData and is invisible in Finder by default. Many iOS and macOS developers find this folder alone consuming tens of gigabytes.
What is Xcode DerivedData?
DerivedData is where Xcode stores intermediate build products, compiler module caches, SourceKit indexes, and build logs. Each project gets its own subfolder with a unique hash suffix. These files are generated during compilation — they are not source code and can always be regenerated.
Where does DerivedData live on Mac?
The default path is ~/Library/Developer/Xcode/DerivedData. Verify in Xcode under Settings → Locations → Derived Data. Press Cmd+Shift+G in Finder and paste the path, or use Terminal to inspect sizes.
How to check DerivedData size
Run du -sh on the DerivedData folder to see total size. For per-project breakdown, list subdirectories with du -sh ~/Library/Developer/Xcode/DerivedData/* — older projects you no longer open are often the largest offenders.
How CodeCleaner helps with DerivedData
CodeCleaner scans DerivedData in parallel, shows per-project sizes, and lets you select which folders to remove. Scan first, review before deleting — only items you approve are removed. Source code in your repositories is never targeted.
Manual steps (Terminal)
Run these commands in Terminal first. Scan first, review before deleting — or use CodeCleaner for a visual interface with per-item size breakdowns.
Check DerivedData size
du -sh ~/Library/Developer/Xcode/DerivedDataDelete all DerivedData
rm -rf ~/Library/Developer/Xcode/DerivedDataSafety warnings
- Quit Xcode before deleting large DerivedData trees to avoid transient indexing errors.
- The first rebuild after deletion may take longer — Xcode regenerates indexes and intermediates.
Or use CodeCleaner
CodeCleaner automates this with a native macOS app. Scan first, review before deleting. Free scan, no account required.
Native macOS app. No account required. Local scan. You review before cleanup.
Frequently asked questions
- Is it safe to delete Xcode DerivedData?
- Yes. DerivedData holds generated build products and indexes, not your source files. Xcode recreates it on the next build.
- Will deleting DerivedData delete my source code?
- No. Your Swift, Objective-C, and project files in your Git repositories are untouched.
- Why does DerivedData get so large?
- Every project you open accumulates indexes, module caches, and build artifacts. Switching branches and Xcode versions adds more without removing old data automatically.
- How often should I clean DerivedData?
- When disk space is tight or after major Xcode upgrades. Many developers clean every few months or when DerivedData exceeds 20 GB.
- Why use CodeCleaner instead of rm -rf?
- CodeCleaner shows per-project sizes so you can remove stale projects only, scan first, and review before deleting — without navigating hidden Library folders manually.
Why developers trust CodeCleaner
- Source code is never targeted
- Only known cache and build artifact paths
- Docker cleanup through official Docker CLI
- Local-only processing — no cloud upload
- No account required
- Free scan before paying for cleanup
Native macOS app. No account required. Local scan. You review before cleanup.