What is com.apple.CoreSimulator.CoreSimulatorService, and why is it running?
Last reviewed: 19 November 2026. Path, launchd job and simctl commands checked with Xcode 26.6 on macOS 26.3.1.
com.apple.CoreSimulator.CoreSimulatorService is the Xcode background service that manages simulated devices: it creates, boots, shuts down and erases simulators and installs apps on them for Xcode, the Simulator app and xcrun simctl. It is busy while devices boot, apps install or a test run starts many simulators. It stays running after Xcode quits, but uses little CPU when no simulator is in use.
com.apple.CoreSimulator.CoreSimulatorService at a glance
| com.apple.CoreSimulator.CoreSimulatorService | |
|---|---|
| Made by | Apple (part of Xcode, CoreSimulator) |
| Type | XPC service (simulator manager) |
| Location | /Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc/Contents/MacOS/com.apple.CoreSimulator.CoreSimulatorService |
| Runs as | your user |
| Started by | launchd job com.apple.CoreSimulator.CoreSimulatorService |
| Can you quit it? | Yes, but running simulators lose their connection to Xcode and Simulator; it starts again on the next simulator request. |
What is com.apple.CoreSimulator.CoreSimulatorService?
CoreSimulator is installed with Xcode into /Library/Developer/PrivateFrameworks. This service is the per-user manager: every request from Xcode, Simulator or xcrun simctl (list, boot, install, erase, add a runtime) goes through it. Each booted device then runs its own launchd_sim and the simulated system's processes.
Simulated devices are stored in ~/Library/Developer/CoreSimulator/Devices, one folder per device with its own data. Simulator runtimes, such as iOS 26.5, are disk images mounted by the root helper simdiskimaged.
Is com.apple.CoreSimulator.CoreSimulatorService safe?
Yes. It is part of Apple's CoreSimulator framework installed by Xcode, signed by Apple, and runs as your user.
Why does com.apple.CoreSimulator.CoreSimulatorService use so much CPU, disk and memory?
- Booting simulators. Starting a device sets up its runtime and launches its system. Test runs that start several devices at once multiply the work.
- Creating, cloning and erasing devices. Each device has its own data folder; creating, cloning or erasing devices writes to
~/Library/Developer/CoreSimulator/Devices. - Installing and launching apps. Every Run from Xcode installs the app bundle into the simulator's data folder and launches it.
- Many devices and runtimes. Keeping track of dozens of devices across several runtimes adds to its memory.
How much CPU is normal for com.apple.CoreSimulator.CoreSimulatorService?
Near 0% CPU when no simulator is booting or installing apps. Bursts when you press Run in Xcode or start a test run are normal.
It remains in the process list after Xcode quits; that is normal and costs little.
How do you reduce simulator load on your Mac?
- See what is running. Run
xcrun simctl list devices bootedin Terminal to list the simulators currently booted. - Shut down simulators you are not using. Run
xcrun simctl shutdown allto stop every running device, including devices booted by Xcode or by test runs. - Delete devices you no longer need.
xcrun simctl delete unavailableremoves devices whose runtime is no longer supported by the current Xcode. - Remove unused runtimes.
xcrun simctl runtime listshows installed runtimes and their size;xcrun simctl runtime delete --notUsedSinceDays 90 --dry-runshows which ones have not been used in 90 days, and the same command without--dry-rundeletes them.
When should you worry about com.apple.CoreSimulator.CoreSimulatorService?
Sustained CPU with no simulators booted, or the same device booting repeatedly, can come from an automated test run or a tool that drives simulators. Its parent and xcrun simctl list devices booted show what is active.
A process with this name outside the CoreSimulator framework path is not Apple's.
How do you check com.apple.CoreSimulator.CoreSimulatorService in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type com.apple.CoreSimulator.CoreSimulatorService in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every com.apple.CoreSimulator.CoreSimulatorService 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 'com.apple.CoreSimulator.CoreSimulatorService' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with com.apple.CoreSimulator.CoreSimulatorService?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when com.apple.CoreSimulator.CoreSimulatorService is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click com.apple.CoreSimulator.CoreSimulatorService in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 com.apple.CoreSimulator.CoreSimulatorService
Why is CoreSimulatorService running when Xcode is closed?
It is a background service for your user that Xcode, Simulator and command-line tools share. It stays available after Xcode quits and uses almost no resources while idle.
How much disk space do simulators use?
Device data lives in ~/Library/Developer/CoreSimulator/Devices, and xcrun simctl runtime list prints the total size of installed runtime disk images. On the Mac used for checking, two runtimes took 11.6 GB.
Sources
- simctl help: run xcrun simctl help in Terminal