Xcode Download Cache
During SDK, simulator runtime, DeviceSupport, documentation, and package downloads, Xcode stores HTTP response bodies, partial transfer data, metadata indexes, and temporary archive files under com.apple.dt.Xcode so it can resume downloads and avoid fetching the same content again. Those cache files can become stale or corrupted after interrupted transfers, Apple server-side changes, or Xcode updates, leading to repeated verification failures or downloads that never finish. Kudu removes the disposable Xcode download cache while leaving projects, signing assets, derived data, preferences, accounts, and keychain items untouched.
Why clean Xcode Download Cache?
- Interrupted simulator runtime or platform downloads leave partial .dmg or archive data behind, and Xcode then loops on extracting or verifying the same package without ever completing
- Stale HTTP metadata in the download cache can point Xcode at outdated package contents, which shows up as repeated 'download failed' or checksum and signature verification errors
- Corrupted resumable transfer data causes paused downloads to restart incorrectly, so Components and Platforms screens appear stuck with progress bars that jump backward or never move
- After an Xcode update, cached package indexes may no longer match the current downloader logic, leading to missing simulator runtimes in the UI until the cache is rebuilt
- Large leftover temporary archives from old iOS, watchOS, tvOS, or visionOS downloads consume tens of gigabytes, and users notice macOS storage filling even though no new tools were installed
- If cached documentation or package payloads are malformed, Xcode may repeatedly re-fetch the same content on launch or when opening Settings, causing network activity and long waits before install options appear
Cache paths Kudu targets
macOS
~/Library/Caches/com.apple.dt.Xcode |
Common questions about Xcode Download Cache
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.