xcode cache cleanup / clear DerivedData / remove DeviceSupport
Xcode cache cleanup on macOS
Target DerivedData, Archives, DeviceSupport, and simulator caches to reclaim large development storage safely.
Where storage typically grows
- DerivedData grows with every build and branch switch.
- Old DeviceSupport and simulator runtimes can consume tens of gigabytes.
- Archives may be critical for release rollbacks and should be reviewed carefully.
Paths covered by Free Mac Space
- ~/Library/Developer/Xcode/DerivedData
- ~/Library/Developer/Xcode/Archives
- ~/Library/Developer/Xcode/iOS DeviceSupport
- ~/Library/Developer/CoreSimulator
- ~/Library/Caches/com.apple.dt.Xcode
Recommended workflow
1.
Filter Xcode category items by size and last modified date.
2.
Clean stale DerivedData first for low-risk and fast recovery.
3.
Review archive names before selecting anything in Archives.
4.
Export a report for team visibility if multiple developers share cleanup guidance.
Safety boundary
Archive and simulator decisions should stay intentional. Free Mac Space requires explicit selection and keeps an audit trail.
FAQ
Should I delete all Xcode archives?+
No. Keep archives tied to production releases and remove only stale or redundant sets.
Will cleanup break active projects?+
DerivedData cleanup is generally safe; archived build artifacts need manual review before removal.
Can I prove what changed after cleanup?+
Yes. Export JSON/CSV/HTML/PDF reports and check the local cleanup audit log.