System
CoreSimulator Caches
Xcode’s CoreSimulator service keeps per-device and shared cache data under ~/Library/Developer/CoreSimulator/Caches to speed up iOS, watchOS, and tvOS simulator boots. This directory can accumulate derived runtime assets, temporary launch services metadata, icon and image caches, and other simulator support files that become stale after Xcode, Simulator runtime, or macOS updates. Kudu removes only these disposable CoreSimulator cache files so the simulator can rebuild them cleanly without touching your apps, device data, accounts, or saved settings.
Why clean CoreSimulator Caches?
- Stale runtime support caches after an Xcode or simulator runtime update can make a device hang on “Booting” or take far longer than usual to start until the cache is rebuilt
- Outdated launch services and app metadata caches can leave simulator home screen icons blank, duplicated, or missing even though the app is still installed
- Cached image and asset data from an older simulator state can cause black screenshots, incorrect previews, or delayed rendering when opening Simulator windows
- Corrupted temporary CoreSimulator cache files can trigger repeated “Unable to boot device” or service connection errors that disappear after the cache is regenerated
- Old support files from removed runtimes continue consuming disk space, so developers notice tens of gigabytes used in Library even after deleting simulator devices
- Version-mismatched cached components after a macOS update can cause Simulator to relaunch repeatedly or close immediately when opening a specific device
What gets cleaned
Cache paths Kudu targets
macOS
~/Library/Developer/CoreSimulator/Caches |
Frequently asked
Common questions about CoreSimulator Caches
Related cleaners
Free & open source
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.