Cleaning Up Xcode To Free Up Disk Space

Xcode cleanup is safest when you separate rebuildable cache from archives, simulator runtimes, DeviceSupport, and important project state.

SafeDisk Lite local scan

Download the Mac app and scan in this same page.

The website alone cannot read Mac folders. SafeDisk Lite adds the local permission bridge, then this web UI shows the largest visible buckets and one optional cleanup candidate.

Download Mac beta See sample result

Usually Safe After Closing Xcode

~/Library/Developer/Xcode/DerivedData build products and indexes.
Unavailable simulator devices from old runtimes.
SwiftPM and package-manager caches through their own cleanup commands.

Review First

~/Library/Developer/Xcode/Archives, especially shipped apps and symbolication archives.
~/Library/Developer/CoreSimulator if active projects need specific iOS runtimes.
DeviceSupport folders if you still test on older physical devices.

Read-Only Xcode Checks

du -sh "$HOME/Library/Developer/Xcode/DerivedData" 2>/dev/null
du -sh "$HOME/Library/Developer/Xcode/Archives" 2>/dev/null
du -sh "$HOME/Library/Developer/CoreSimulator" 2>/dev/null
du -sh "$HOME/Library/Developer/Xcode/iOS DeviceSupport" 2>/dev/null
xcrun simctl list runtimes 2>/dev/null
xcrun simctl list devices unavailable 2>/dev/null

Safer Cleanup Order

Close Xcode and stop running simulators.
Measure DerivedData, Archives, CoreSimulator, and DeviceSupport separately.
Clean DerivedData first if it is the largest rebuildable bucket.
Delete unavailable simulator devices before removing runtimes.
Review archives with the app/release owner before removing them.

Deep Cleanup

Still full after the SafeDisk Lite scan?

Start with the SafeDisk Lite scan. If the scan shows review-first storage that still needs judgment, send one request for the $29 Deep Cleanup next step.