Why Is Xcode Taking Up So Much Space: safe Xcode cleanup path
If you are dealing with Why Is Xcode Taking Up So Much Space, start with a read-only scan and a safe/review/do-not-touch cleanup order before deleting anything.
Start with read-only diagnosis
Xcode storage is a stack of different folders. DerivedData is usually easy to rebuild, while archives, runtimes, and device support deserve review.
du -sh ~/Library/Developer/Xcode/DerivedData
du -sh ~/Library/Developer/Xcode/Archives
du -sh ~/Library/Developer/CoreSimulatorUsually safer cleanup candidates
- DerivedData after Xcode is closed
- Old unavailable simulator devices
- Regenerable package and build caches
Review before deleting
- Archives used for release history or symbolication
- Simulator runtimes needed by current projects
- DeviceSupport folders for devices still in use
What to do next
After you find the largest folders, sort each item into three buckets: safe to remove, review first, and do not touch. That keeps the cleanup focused on recoverable space instead of random Library deletion.
Want this checked against your scan?
Run a local read-only scan, then get a plain-English cleanup report with safe, review, and do-not-touch buckets.