How to Clean Xcode DerivedData, Caches & Simulators Safely

What Is Xcode DerivedData and Why Does It Grow?

Xcode stores build-time information in a central directory located at ~/Library/Developer/Xcode/DerivedData. Inside this directory, Xcode creates a dedicated subfolder for each project and workspace you open.

DerivedData contains: 1. Indexing Data: Syntax maps, symbol graphs, and cross-references used for code completion and Quick Help. 2. Build Products: Intermediate object files (.o), pre-compiled frameworks, and dSYMs. 3. Module Caches: Pre-compiled Swift and Clang modules. Because artifacts from older builds, renamed targets, or archived branches can accumulate, DerivedData tends to expand until it is cleared.

Is It Safe to Delete DerivedData?

DerivedData contains generated build and indexing data that Xcode can usually recreate. Removing it may trigger a full rebuild and reindex, so confirm you are deleting DerivedData rather than project or archive data.

Clearing DerivedData is a standard troubleshooting step in the Apple developer community when Xcode behaves erratically, displays persistent build errors, or fails to resolve Swift Package Manager dependencies. Keep in mind that the subsequent build will take longer because Xcode must re-index your codebase and recompile dependencies.

Manual Methods to Clean DerivedData

You can clean DerivedData manually using Xcode settings or Finder, or via Terminal:

• Via Xcode Settings & Finder (Recommended): Open Xcode → Settings (Command + ,) → Locations. Under 'Derived Data', click the small arrow icon next to the path to open the folder in Finder. Confirm you are inside DerivedData, quit Xcode, then select and move project subfolders to Trash. This allows you to inspect what is being removed and recover files from Trash if needed.

• Via Terminal (Advanced): If you prefer command-line workflows, quit Xcode first and run: rm -rf ~/Library/Developer/Xcode/DerivedData/* . Note that rm -rf permanently deletes files immediately without moving them to Trash, so verify the path carefully before running it.

Cleaning Unused iOS, watchOS & tvOS Simulators

Each simulator runtime downloaded through Xcode consumes several gigabytes of storage. Over time, as new OS updates are installed, older simulator versions remain on your drive.

To inspect installed simulators, run xcrun simctl list in Terminal. To remove unavailable or orphaned simulator devices and clear their caches, run xcrun simctl delete unavailable. You can also navigate to Xcode Settings → Components to view, manage, and remove downloaded platform simulator runtimes you no longer test against.

Using Smart Cleaner AI Alongside Xcode Storage Maintenance

When managing developer storage, visual inspection helps identify where drive capacity is concentrated.

Smart Cleaner AI's Disk Analyzer can help you inspect storage-heavy folders and files that are visible to the scanner across your system. Xcode-specific cleanup—such as managing DerivedData, build products, and simulators—should still be reviewed and performed using Xcode settings, Finder, and developer command-line tools so that project configurations remain intact.