Xcode DerivedData: How to Safely Reclaim 50GB+ on Your Mac
Xcode's DerivedData folder is a notorious drive hog. Learn what it is, why it grows, and how FreeUpMac helps you find and remove it safely.
- Xcode
- DerivedData
- Developer
If you build iOS or macOS apps, ~/Library/Developer/Xcode/DerivedData is probably eating more SSD than your actual projects.
What DerivedData is
Xcode stores build artifacts, indexes, and module caches here so rebuilds are faster. Over months it becomes a graveyard of old app targets you forgot about.
How much space?
It is common to see 20–80 GB on a single machine. Simulator runtimes and DeviceSupport folders add even more under ~/Library/Developer.
Is it safe to delete?
Usually yes — Xcode recreates what it needs on the next build. The tradeoff is longer first compile after cleanup.
Do not delete while Xcode is building. Quit Xcode first, or remove folders from the map after inspecting them.
Find it without Terminal
FreeUpMac labels DerivedData blocks on the treemap as Xcode DerivedData · Review. Scan Home, double-click Developer, and the hog is obvious.
Pro unlock lets you move selected folders to Trash in one confirm step.