How to delete old iOS simulators and simulator runtimes
Simulator runtimes and old simulator devices are some of the biggest things Xcode leaves on a Mac. Here's how to see what you have and remove it with Xcode's own tools. Updated 14 November 2026.
Three different things
"Simulators" covers three things that live in different places and are removed in different ways:
- Simulator devices: each iPhone, iPad, Apple Watch or other device in Xcode's run destination menu. Each one has its own data, such as the apps you installed in it and its settings, in a folder inside
~/Library/Developer/CoreSimulator/Devices. - Simulator runtimes: the copy of iOS, watchOS, tvOS or visionOS that devices run on. Each runtime is large, and new Xcode versions bring new ones. Recent versions of Xcode keep runtimes as disk images under
/Library/Developer/CoreSimulator(the top-level Library, not the one in your home folder) and mount them when needed. - Simulator caches in
~/Library/Developer/CoreSimulator/Caches: files the Simulator prepares so devices start faster.
Most of the space is usually in runtimes and in old devices full of app data. The commands below need Xcode installed. xcode-select -p shows which Xcode they use.
See what you have
xcrun simctl list devices
xcrun simctl runtime list
du -sh ~/Library/Developer/CoreSimulator/Devices
The first command lists every simulator device, grouped by runtime, and marks the ones whose runtime is no longer available. The second lists the runtime disk images, with their total size at the top; add -v for more detail. The third shows how much space your devices' data takes. All three only read.
1. Delete unavailable simulators
xcrun simctl delete unavailable
This removes every device the current Xcode can't run, usually because its runtime was removed or came with an older Xcode. In the command's own words, it removes "devices that are not supported by the current Xcode SDK". It's the safest first step, because you couldn't use those devices anyway. Each device's data goes with it, including apps installed in it and files saved there.
2. Delete devices you no longer use
To remove one device, copy its UDID (the long ID in brackets) from xcrun simctl list devices:
xcrun simctl delete <UDID>
You can do the same in Xcode: choose Window → Devices and Simulators, click Simulators, then Control-click a device and choose Delete.
If you want to keep a device but clear the test data inside it, xcrun simctl erase <UDID> resets its contents and settings. A running device has to be shut down first, with xcrun simctl shutdown <UDID>.
Avoid xcrun simctl delete all and xcrun simctl erase all unless you really want every device, or every device's data, gone at once.
3. Remove simulator runtimes you don't need
This is usually where the most space comes back. Apple's documented way is in Xcode's settings (Installing additional simulator runtimes):
- Choose Xcode → Settings, then click Components (called Platforms in some older versions).
- Select a runtime you no longer test on. Xcode shows how much storage you get back by removing it.
- Click the Delete button (-) in the lower-left corner, then click Delete to confirm.
From Terminal, xcrun simctl runtime delete does the same job. Preview first with --dry-run, which prints what would be removed without removing anything:
xcrun simctl runtime delete <identifier> --dry-run
xcrun simctl runtime delete --notUsedSinceDays 90 --dry-run
Take the identifier from xcrun simctl runtime list. The second form picks runtimes that haven't been used in the number of days you give it. Run the command again without --dry-run to remove them. Any running simulators on that runtime are shut down first. The command also accepts all in place of an identifier, which removes every runtime, so leave that one alone unless that's what you mean.
What it costs: if you need a runtime again, Xcode downloads it again, which is a large download. Keep the runtime that matches your current Xcode. Apple notes you can run projects on older runtimes, but you need the current one to build them.
4. Clear simulator caches
~/Library/Developer/CoreSimulator/Caches holds files the Simulator prepares so devices start faster. With Simulator and Xcode quit, it's safe to move to the Trash. The next device you start takes longer while the Simulator prepares them again.
Two folders nearby behave the same way. SwiftUI preview devices in ~/Library/Developer/Xcode/UserData/Previews come back the next time you open a preview, and test devices in ~/Library/Developer/XCTestDevices come back the next time you run tests.
What not to delete in Finder
/Library/Developer/CoreSimulator, the top-level one. Runtime disk images are mounted from here, and Xcode keeps its own records of them. Deleting files by hand can leave Xcode listing runtimes that are no longer there. Use Components orsimctl runtime delete.- Folders inside
Deviceswhile Xcode or Simulator is open.simctl deleteremoves the device and updates the device list at the same time. - Xcode Archives in
~/Library/Developer/Xcode/Archives. They aren't simulator files, but they sit nearby and they can't be rebuilt. They hold the dSYMs you need to read crash reports from your shipped builds.
If the space doesn't come back
Run xcrun simctl runtime list again to check the runtime is gone, then restart your Mac, which releases any disk images that were still mounted. Free space can also take a little while to show in Finder and Storage settings. If a runtime keeps reappearing in Components, remove it from there once more with Xcode's other windows closed, and check that xcode-select -p points at the Xcode you're using.
What CheckMac does here
CheckMac's Suggested Cleanup finds simulator caches, SwiftUI preview devices and test simulator devices that haven't changed in a week or two, and shows what rebuilds each one and what you lose. It doesn't suggest your simulator devices or runtimes: devices hold apps and data, and runtimes cost a long download, so you remove those with Xcode's tools as above. The disk map shows ~/Library/Developer/CoreSimulator at its real size, so you can tell whether simulators are worth your time before you start. Nothing moves until you've reviewed it in the Discard Pile. For DerivedData and device support files, see how to delete Xcode DerivedData, simulators and device support files. For every other developer folder, see the developer checklist.


See it on your own Mac. CheckMac maps any folder or drive as a sunburst or treemap, and Suggested Cleanup lists the caches and build output a tool can rebuild, with what each one costs you. Scanning is free, and Suggested Cleanup is free for its first three runs.
More guides
- What is System Data on Mac, and how do you reduce it?
- How to delete Xcode DerivedData, simulators and device support files safely
- Is it safe to delete node_modules, caches and build folders on a Mac?
- Looking for a CleanMyMac alternative?
- Mac storage almost full on a 256 GB Mac: what to do
- How to see what's taking up space on your Mac
- Free up disk space on a Mac for developers: a checklist
- Docker taking up space on Mac: Docker.raw explained
- How to delete local AI models on a Mac: Ollama, LM Studio and Hugging Face
- Purgeable space on a Mac: what it is and how to clear it