{
  "id": 21030294,
  "title": "Is Xcode DerivedData Safe to Delete? What Happens and How to Clean It",
  "url": "https://urgent.news/2026/11/21/is-xcode-deriveddata-safe-to-delete-what-happens-and-how-to-clean-it",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T10:10:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/fastlog/is-xcode-deriveddata-safe-to-delete-what-happens-and-how-to-clean-it-14o0"
  },
  "original_language": "en",
  "account": "Xcode's DerivedData folder can be safely deleted without affecting your source code or Git history. Deleting it will cause Xcode to regenerate all contents the next time you open and build a project, which may take longer due to the initial regeneration. The amount of space consumed by DerivedData varies depending on the number of projects and iOS SDKs you work with. For example, on one developer's Mac, DerivedData occupied 15.3 GB, while Xcode storage for iOS DeviceSupport and CoreSimulator/Devices was 24.1 GB and 43.0 GB, respectively.\n\nWhen deleting DerivedData, always quit Xcode first to avoid build issues or stale editor warnings. You can remove DerivedData manually via Finder or Terminal, or use a third-party tool like CleanBit, which provides options to clean Xcode storage selectively. CleanBit separates Xcode folders based on their risk level, such as rebuildable DerivedData, older DeviceSupport versions, SwiftUI Preview data, and caches from shut-down Simulator devices. It is recommended to clear DerivedData once every few weeks or whenever you finish a major project, upgrade Xcode, or encounter build glitches.\n\nDeleting DerivedData does not break Swift Package Manager dependencies, as the package list is defined in Package.swift or the .xcodeproj file, and Xcode will automatically re-resolve and rebuild packages when you open the project again. However, if you use AI coding agents or JavaScript toolchains, there might be additional storage that needs cleaning, as outlined in separate guides.",
  "summary": "Yes—Xcode's DerivedData folder is safe to delete. Xcode automatically regenerates everything inside it the next time you open and build a project. The only trade-off is that your next build and index for each project will start from scratch and take longer. On one developer Mac we measured, ~/Library/Developer/Xcode/DerivedData occupied 15.3 GB (and adjacent Xcode storage was even larger: 24.1 GB…",
  "key_points": [
    "Deleting Xcode's DerivedData folder won't affect source code or Git history.",
    "Regeneration of DerivedData contents may take longer after deletion.",
    "CleanBit tool helps selectively clean Xcode storage safely."
  ],
  "editors_take": "Treating DerivedData as disposable storage allows developers to reclaim significant disk space without risking source code integrity, provided they accept the temporary cost of longer initial build times.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}