Developer storage guide
How to clean Xcode DerivedData safely
DerivedData contains rebuildable indexes and build products, so stale project folders can usually be removed after Xcode and related tools stop using them. Deleting it forces later indexing and rebuilds; do not confuse DerivedData with source repositories or Xcode Archives.
What macOS can do on its own
Use a project-specific cleanup when one workspace is broken, and a broader cleanup only when you have reviewed ages and sizes.
- Finish current builds, quit Xcode and simulators that depend on the output, and commit or back up source work separately.
- Open the DerivedData location from Xcode settings or Finder and inspect folder names, modification dates, and sizes.
- Move only stale project folders to Trash. Keep Archives and source repositories out of the selection.
- Reopen the active project and expect Xcode to re-index and rebuild before emptying Trash.
When Mint helps
Mint is useful when several Xcode projects have accumulated build output and you want candidates grouped with other developer artifacts.
- Scan supported developer locations and surface DerivedData with path, size, and age context.
- Review candidates before removal rather than deleting the whole parent directory blindly.
- Use the available Xcode DerivedData cleanup rule as a dry run before executing it.
- Move approved artifacts to Trash and record the batch in the local operation journal.
Boundaries and safety checks
DerivedData is reproducible, but removing it can cost time and interrupt active work.
- Do not remove output used by a running build, test, preview, or debugging session.
- Xcode Archives are separate and may contain the only retained build suitable for export or symbolication.
- A successful rebuild is the best confirmation before Trash is emptied; Undo still depends on the trashed item existing.
Frequently asked questions
Is Xcode DerivedData safe to delete?
It is rebuildable, but deletion removes indexes and build products and can slow the next build. Stop active Xcode work and review project-specific folders first.
Does cleaning DerivedData delete my source code?
Not when the selection is truly inside DerivedData. Confirm exact paths and keep source repositories and Archives outside the cleanup list.
Can Mint find other developer artifacts?
Mint can scan supported locations for developer artifacts including DerivedData, simulator data, package-manager caches, and stale node_modules, subject to edition access and your review.
Review stale DerivedData by project
Run a developer-artifact scan, keep current projects selected only when intentional, and test a rebuild before emptying Trash.