What is simdiskimaged, and why is it using disk and CPU on my Mac?
Last reviewed: 19 November 2026. Path, launchd job, running user and simctl runtime commands checked with Xcode 26.6 on macOS 26.3.1.
simdiskimaged is a root daemon installed with Xcode that manages simulator runtimes, such as iOS or watchOS, which are stored as disk images: it stages, verifies and mounts them so simulators can boot. It is busy when Xcode downloads or installs a runtime, when you add or delete one, and when images are mounted at boot. Deleting runtimes you no longer use with xcrun simctl runtime delete is the main way to reduce its work and reclaim space.
simdiskimaged at a glance
| simdiskimaged | |
|---|---|
| Made by | Apple (part of Xcode, CoreSimulator) |
| Type | System daemon (simulator runtime disk images) |
| Location | /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Resources/bin/simdiskimaged |
| Runs as | root |
| Started by | launchd job com.apple.CoreSimulator.simdiskimaged |
| Can you quit it? | Not usefully. launchd starts it again, and simulators that need a runtime image cannot boot without it. |
What is simdiskimaged?
Simulator runtimes are large, so Xcode installs them as disk images in a secure storage area managed by this daemon. xcrun simctl runtime add describes the process: the image is staged, verified and mounted, and cloned when possible so no extra disk space is used. Mounted runtimes appear under /Library/Developer/CoreSimulator/Volumes, for example iOS_23F77 for iOS 26.5.
It runs as root from the system launchd job com.apple.CoreSimulator.simdiskimaged, because mounting disk images needs administrator rights. Your simulators themselves are managed by the per-user CoreSimulatorService.
Is simdiskimaged safe?
Yes. It is part of Apple's CoreSimulator framework installed by Xcode in /Library/Developer/PrivateFrameworks, and signed by Apple. It only handles simulator runtime images.
Why does simdiskimaged use so much disk and CPU?
- Installing a runtime. When Xcode downloads a new iOS, watchOS, tvOS or visionOS simulator runtime, the image is copied or cloned into storage and verified, which reads the whole image.
- Verifying images. Verification checks the integrity of multi-gigabyte images, which takes CPU as well as disk reads.
- Mounting and unmounting. Runtimes are mounted so simulators can use them, and unmounted or removed when deleted, which shows as bursts of disk activity.
- Deleting runtimes. Deleting a runtime shuts down simulators that use it, unmounts the image and removes it from storage.
How much disk is normal for simdiskimaged?
Idle almost all the time. Activity during an Xcode or runtime update, or right after the Mac starts, is expected.
Its disk footprint is the runtime images themselves; xcrun simctl runtime list prints the total. On the Mac used for checking, two runtimes took 11.6 GB.
How do you reduce simdiskimaged's disk use?
- List installed runtimes. Run
xcrun simctl runtime listto see each runtime image, its build, its state and the total size. - Preview unused runtimes. Run
xcrun simctl runtime delete --notUsedSinceDays 90 --dry-runto see which images have not been used for 90 days without deleting anything. - Delete what you do not need. Run the same command without
--dry-run, orxcrun simctl runtime delete <identifier>for one image. Simulators using it are shut down first. - Unmount without deleting.
xcrun simctl runtime unmount <identifier>unmounts an image you want to keep but are not using now.
When should you worry about simdiskimaged?
Long, repeated disk activity with no Xcode update or runtime install in progress is unusual; check xcrun simctl runtime list for an image that is not in the Ready state.
A simdiskimaged outside the CoreSimulator framework path is not Apple's.
How do you check simdiskimaged in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type simdiskimaged in the search field. The Disk tab shows its Bytes Written and Bytes Read. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every simdiskimaged process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'simdiskimaged' | grep -v grep
sudo fs_usage -w -f filesys simdiskimaged
How can Thrum help with simdiskimaged?
Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list simdiskimaged with the rest. macOS does not give per-process disk counters for processes owned by root or other users to an app without administrator rights, so Thrum shows simdiskimaged by CPU and memory, not by bytes written. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about simdiskimaged
Why does simdiskimaged run as root?
Mounting and managing disk images in the shared storage area needs administrator rights, so the daemon runs as root and does that one job for every user's simulators.
Will deleting a runtime break my simulators?
Devices that use that runtime become unavailable. xcrun simctl delete unavailable then removes those devices.
Sources
- simctl runtime help: run xcrun simctl runtime in Terminal
- launchctl(1) man page: run man launchctl in Terminal