Can you delete Xcode Derived Data?

By CleanMacster Team · Published · Updated

Xcode Derived Data contains generated build and indexing output that can generally be recreated from your project. Close active work and identify the correct project-specific location before clearing it. Expect a slower next build or reindex. Keep source code, signing material and release archives; they are different from Derived Data.

Find the actual location

Check Xcode Settings → Locations and any custom project/workspace build settings. The default location is under your user Library, but scripts can override it with -derivedDataPath. Do not assume the default contains all build output.

Find Derived Data in Xcode Settings

Xcode 27.2 Settings Locations heading and the Derived Data row set to Default.
Captured on October 30, 2026 in Xcode 27.2 (27B48), Settings → Locations, on macOS 27.2. This crop shows the Locations heading and Derived Data row; local account paths and the lower rows are excluded. Your project or build script can use a different path. No settings or project files were changed.
  1. Derived Data: read the path below this row in your own Xcode settings before looking for generated output. Check custom project settings or a script’s -derivedDataPath too.
  2. Archives: Xcode lists this separately below Derived Data, outside this crop. It is not the Derived Data folder. Preserve release archives and symbols you may need.
  3. Compilation Cache: this Xcode version lists another cache location below Archives, outside this crop. Its existence is not a reason to remove the entire parent Developer folder.

Inspect first

du -sk "$HOME/Library/Developer/Xcode/DerivedData"

This read-only estimate reports accessible allocated blocks in KiB. It can fail on a missing or inaccessible directory. Check a project’s specific folder rather than deleting all projects’ output as a routine habit.

Clear the narrowest scope

  1. Save work and stop the build or indexing task.
  2. Confirm the project’s Derived Data location.
  3. Review the folder and preserve anything you deliberately placed there.
  4. Remove only the generated output you intend to reset.
  5. Open the project, rebuild and allow indexing to complete.

Do not use a wildcard command if you are uncertain how the path expands. Moving generated output aside may help review, but moving it elsewhere on the same disk does not itself free capacity.

What it costs

Compilation, module caches and indexing may need to run again. Dependency downloads or other caches can be outside Derived Data, so clearing it is not a universal dependency reset. Time depends heavily on project size, hardware and what is already cached.

Keep archives and source

Xcode Archives can include shipped app builds and symbols useful for crash reports. They are not the Derived Data folder. Do not delete them under the assumption that every item under Library/Developer is regenerable.

Our controlled example

Our Xcode storage cleanup experiment documents a disposable sample build with a dedicated DerivedData path, measured output and rebuild times. It is a procedure example, not a benchmark of your project or of CleanMacster’s cleaning speed.

Using CleanMacster

Review the identified developer category and path before selecting it. You can also manage generated output directly in your development workflow without purchasing a utility.

Short visual summary

A silent illustrated procedure, not a screen recording or a product benchmark.
Text transcript
  1. Locate the project’s Derived Data.
  2. Keep source files and archives.
  3. Clearing output means rebuilding.

Sources and verification

Sources checked . CleanMacster publishes this page; see our editorial policy. Instructions can differ by system and app version.

Review your Mac before cleaning

Scanning is free. Cleaning requires a license. For macOS 14 or later.