DerivedData is generally rebuildable
DerivedData lives under ~/Library/Developer/Xcode/DerivedData and contains build output, indexes, and preview-related caches. After closing Xcode, removing an old project's directory is generally safe. The cost is a slower first open and rebuild.
For one misbehaving project, try Clean Build Folder or remove only that project's DerivedData. There is no need to erase every development cache for a local issue.
Treat Archives as release assets
Archives contain archived builds, dSYMs, and distribution information. You may need the matching dSYM to symbolicate a crash from a version already in production, so Archives are not ordinary cache.
Review dates, versions, and upload state in Xcode Organizer. Keep supported production versions, and delete old archives only after confirming that CI or another backup preserves the symbols you need.
Manage simulators and DeviceSupport
Remove unused Simulator runtimes from Xcode's platform settings. A runtime can be large, and the official interface keeps component state consistent. Reset individual simulator devices from Devices and Simulators when their app data is the problem.
DeviceSupport helps Xcode debug physical devices. It may be prepared again when you connect a matching OS version, but keep versions you still test regularly.
Add cleanup to project closeout
After delivering a project, remove rebuildable DerivedData, obsolete simulator contents, and redundant local dependencies. Back up Archives and dSYMs separately. Diskly can rank these scattered locations by usage before you decide what to touch.
If your team uses CI, document retention for artifacts, symbols, and cache independently. Local cleanup should not accidentally become the only release-asset policy.
Understand first, clean second
Diskly scans locally on your Mac, maps real usage in a treemap, and keeps every cleanup suggestion reviewable.
Download free trial