Can I Delete Xcode Caches?

Usually yes for regenerable build caches, but not every large Xcode folder is the same. Separate safe cache from simulators, archives, and device support before deleting.

Free browser cleanup

Find the biggest storage culprit first.

Run the Chrome or Edge web scan, delete one approved low-risk item free, then use the $29 Deep Cleanup only if meaningful space remains.

Start free cleanup $29 Deep Cleanup

Short answer

You can usually delete Xcode build cache and DerivedData after closing Xcode. The next build may be slower, but Xcode can recreate those files. Be more careful with archives, simulator data, and device support folders because they may affect testing, debugging, or old app releases.

Usually safe after closing Xcode

~/Library/Developer/Xcode/DerivedData
old build products
regenerable indexing and preview cache

Review before deleting

~/Library/Developer/CoreSimulator if you still test old iOS versions
Xcode Archives if you may need symbolication or old release builds
DeviceSupport folders for devices and OS versions you still connect

Read-only checks

du -sh ~/Library/Developer/Xcode/*
du -sh ~/Library/Developer/CoreSimulator/*
du -sh ~/Library/Developer/Xcode/Archives/*

Safer cleanup order

Close Xcode and simulators.
Check folder sizes first.
Delete DerivedData/build cache first.
Move review-first folders to Trash instead of permanent deletion.
Open active projects and simulator targets before emptying Trash.

Want a risk-ranked Xcode cleanup report?

Run the Chrome/Edge web scan and preview what is safe, review-first, or worth keeping before touching Xcode storage.

No terminal command is required. Open the browser scan from the homepage: start scan.

Preview your scan

Deep Cleanup

Still full after the free cleanup?

Send your email once. We reply with the $29 payment link, one clarification, or a no-pay answer if the free cleanup is enough.