Blog / For developers

Delete old iOS simulators in Xcode with simctl runtime delete

Every Xcode update leaves another 8 GB copy of iOS behind. Which ones you can remove, the command that does it, and how to check the space came back.

My Mac froze and restarted on its own on September 29, with the disk 97% full. About 64 GB of that disk was eight copies of iOS: simulator runtimes Xcode had downloaded over time and never removed.

I deleted six of them that afternoon with Apple’s own tool, and simctl and Xcode both stopped listing them. Only one left the disk. By October 15 the other five were back on simctl’s list. When I deleted four of them again on October 28, the folder they live in didn’t shrink by a single kilobyte.

TLDRSafe to remove, then check

List your runtimes with xcrun simctl runtime list -v, and delete the ones you don’t use with xcrun simctl runtime delete. Keep the one that matches your Xcode, and remove leftover devices with xcrun simctl delete unavailable. Then measure the runtime folder with du -sk before and after, because simctl’s list isn’t proof. On my Mac, most deleted runtimes stayed on disk, so that check is the only number I trust.

Why simulators take so much space

Each simulator runtime is a full copy of iOS that the Simulator app runs apps on. By simctl’s count, mine were 7.5 to 8.2 GB each. Xcode adds a new one with most updates, and it doesn’t remove the old ones.

They don’t live in your home folder or in Xcode’s folder. The images sit in /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime, a protected system folder you’d have no reason to open. There’s a separate post on what the AssetsV2 folder is and why you can’t delete it, if you want the rest of that story.

Eight had piled up on my Mac. Only two had been used in the past month.

Runtime Size Last used What I did
iOS 18.0 7.8 GB September 4, 2026 Deleted
iOS 18.1 8.0 GB July 11, 2025 Deleted
iOS 18.2 8.1 GB Not listed Deleted
iOS 18.4 8.2 GB Not listed Deleted
iOS 18.5 8.2 GB Not listed Deleted
iOS 26.1 7.8 GB Not listed Deleted
iOS 26.5 7.9 GB September 3, 2026 Kept
iOS 27.0 7.5 GB Not listed Kept, matches Xcode 27

The eight runtimes on my Mac on September 29, 2026, from simctl. “Not listed” means simctl showed no last-used date.

If you measure any of this with du, add -x. My first du -sh /Library/Developer/CoreSimulator said 186 GB, because du walked into runtime disk images macOS had mounted inside that folder and counted what was in them. With -x, which keeps du on one file system, the same folder was 3 GB.

See what you have

Open Terminal and run this. It lists every runtime with its version, ID, size, and the last time a simulator used it.

xcrun simctl runtime list -v

Each runtime gets a block like the two below, which I’ve cut down to the lines that matter here. The long string after the dash is the runtime ID you’ll need to delete it.

iOS 18.0 (22A3351) - 34EF0938-835F-40C8-B2E7-8A536E6EE207
    Last Used At: 2026-09-04 04:50:27 +0000
    Size: 7.8G
iOS 18.2 (22C150) - A423DDE3-C93D-48DF-A9B7-D080200AB7DA
    Size: 8.1G

The last line of the list is a total, Total Disk Images followed by a count and a size. Keep that line in mind for the check further down.

Which ones to keep

Keep the runtime that matches your Xcode version, plus any iOS version your app still supports. Runtimes with no “Last Used At” line are the first ones to look at.

Delete the ones you don’t need

Before you run this

Quit Xcode and the Simulator app first, so nothing is using a runtime while it’s removed.

  1. Copy the ID of a runtime you want to remove from the list.
  2. Run the delete command with that ID.
xcrun simctl runtime delete 34EF0938-835F-40C8-B2E7-8A536E6EE207

That ID is my iOS 18.0 runtime, so yours will be different. In September, each runtime switched to Deleting and dropped off the list a few minutes later. On October 28, four were off the list within fifteen seconds. Repeat for each one you want gone.

You can also have simctl pick runtimes by age. Run it with --dry-run first, which prints what it would delete and deletes nothing:

xcrun simctl runtime delete --notUsedSinceDays 90 --dry-run

Read the dry run closely before you run it for real, and make sure the runtime that matches your Xcode isn’t on it. On my Mac, iOS 27.0, the one that matches Xcode 27, showed no last-used date at all, so the dates alone won’t tell you which runtime you need. When the list looks right, run the same command without --dry-run.

The help text also lists --keep-asset, which keeps the downloaded image when the runtime is deleted. I never passed it, so by the help text, each delete should have removed the image too.

Clean up old devices

Each runtime comes with simulator devices, an iPhone or iPad on that iOS version. Once a runtime is gone, its devices are marked unavailable. This removes all of them at once:

xcrun simctl delete unavailable

Devices live in ~/Library/Developer/CoreSimulator/Devices. On September 29, mine came to 9.5 GB, and 67 of those devices belonged to runtimes I had deleted.

Get one back later

Deleting a runtime doesn’t lock you out of that iOS version. Open Xcode, go to Settings, then Components, and download it again. On a slow connection it takes a while.

Check that the space came back

After the deletes on September 29, simctl listed two runtimes. Xcode’s Components settings agreed, with only iOS 27.0 and the iOS 26.5 Simulator left.

By every tool’s count, six runtimes were gone. Then I measured the folder where the images live:

du -shx /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime
 57G	/System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime

And compared it with simctl’s own total:

xcrun simctl runtime list
== Disk Images ==
-- iOS --
iOS 27.0 (24A434) - 9AC2BBF1-6EAC-4F75-962C-50A29F64A30E (Ready)
iOS 26.5 (23F77) - 2038C521-9C29-4D5D-AB6D-BCC78E940A5B (Ready)

Total Disk Images: 2 (15.4G)

Two runtimes at 15.4 GB, in a folder of 57 GB. The difference was five of the six runtimes I had deleted, still on disk:

Deleted runtime Still on disk
iOS 18.0 8.0 GB
iOS 18.1 8.2 GB
iOS 18.2 8.4 GB
iOS 18.4 8.5 GB
iOS 18.5 8.5 GB
iOS 26.1 Gone

Measured with du -x in the AssetsV2 folder on September 29, 2026, after the deletes. 41.6 GB in total.

Run the same two commands on your Mac, and compare the folder with the iOS runtimes in simctl’s list. If the two are close, your deletes worked. If the folder is much bigger, you have leftovers too.

By October 15, they were back on the list

When I measured AssetsV2 on October 15, xcrun simctl runtime list showed all five leftovers as Ready again: iOS 18.0, 18.1, 18.2, 18.4 and 18.5, next to iOS 26.5 and 27.0. They were still on the disk, and simctl listed them again.

By October 28 the list had changed again. iOS 26.5 was off it, and its folder was gone from AssetsV2. simctl listed six runtimes at 47.8 GB, and I measured the folder before touching anything:

du -sk /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime
51553840	/System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime

That’s 51,553,840 KB, about 49 GB, in six .asset folders, one for each runtime on the list.

Then I deleted iOS 18.1, 18.2, 18.4 and 18.5 a second time, each by its ID with xcrun simctl runtime delete, after a --dry-run. iOS 18.0 stayed, because it had been used on October 24. Fifteen seconds later, simctl listed two runtimes, iOS 18.0 and 27.0, at 15.3 GB.

Ten minutes later, du printed the same 51,553,840 KB. All six .asset folders were still there. Later that afternoon I ran it once more and got the same number again.

October 28, 2026 simctl’s total du on the folder
Before the second delete 47.8 GB, 6 runtimes 51,553,840 KB
After the second delete 15.3 GB, 2 runtimes 51,553,840 KB

simctl’s total dropped by 32.5 GB. The folder didn’t change by a kilobyte.

So on my Mac, a simctl delete freed a runtime’s folder once, for iOS 26.1 in September. The other five stayed after the first delete, and the four I deleted again stayed after the second. If du doesn’t drop on your Mac either, the files are in a protected folder, and turning off System Integrity Protection to clear them isn’t worth the risk.

What not to do about leftovers

Leave the protected folder alone

On my Mac, ls -ldO /System/Library/AssetsV2 shows the folder marked restricted. Apple’s page About System Integrity Protection on your Mac lists /System as protected and says only Apple-signed processes can change it, not even the root user. Turning SIP off to get around that trades a security feature for disk space. I’m not doing it, and I wouldn’t suggest it.

Deleting runtimes with simctl or in Xcode’s Components settings is the supported way. On my Mac, the leftovers it couldn’t clear stay where they are.

What I do: measure the simulator folder with du -sk before any runtime delete, and again a few minutes after. If the two numbers match, the delete only changed the list, whatever simctl’s total says.

What Diskling does here

Diskling lists every runtime with its size and when it was last used, and runs this same simctl command after you’ve reviewed the list.

After the cleanup it measures the disk again and compares it with what was expected. When space doesn’t come back, like runtimes that stay in AssetsV2, it says how much, where it is, and who owns it.

Get Diskling

What I got back

In September I kept iOS 27.0, which matches Xcode 27, and iOS 26.5, and deleted the other six. simctl had listed those six at 48.1 GB. Only iOS 26.1, at 7.8 GB, actually left the disk.

The second round on October 28 took simctl’s total down by another 32.5 GB. On disk, it gave back nothing du could see.

So run the check after any cleanup. It’s one du before and one after, and twice now it’s the only thing that told me what a delete really did on my Mac.

Questions people ask

How do I delete old iOS simulators?

Run xcrun simctl runtime list -v, copy the ID of a runtime you don’t need, and run xcrun simctl runtime delete with that ID. Then run xcrun simctl delete unavailable to remove the simulator devices that belonged to them.

Where are iOS simulator runtimes stored on a Mac?

In /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime, one .asset folder per runtime. The simulator devices you create live separately, in ~/Library/Developer/CoreSimulator/Devices.

Will deleting old simulators break Xcode?

Not if you keep the runtime that matches your Xcode and any iOS version your app still supports. If you need one back, download it again in Xcode’s settings, under Components.

Why didn’t deleting a simulator free any space?

On my Mac, runtimes that showed up on simctl’s list again after an earlier delete kept their files in AssetsV2 when I deleted them a second time. Compare du -sk on the simulator folder before and after a delete to see what really came back. The folder is protected by System Integrity Protection, so you can’t remove what’s left by hand.

Know someone with a full Mac? Send them this.
Nazmoon Munny
Nazmoon Munny Chief Overthinker at Dotbrain

I'm the product manager for Diskling, which mostly means asking "but what if" until nothing breaks. I studied soil science before software, and outside work it's family, farming and whatever I'm learning next.

Comments

No comments yet. Tried this on your Mac? Tell me how it went.

Please add your name.

That email doesn’t look right.

Add a few words first.

I read every comment before it shows up.