1. Identify what is taking the space
An iPhone simulator is a virtual device with its own installed apps and state. A simulator runtime supplies the operating-system version used by one or more virtual devices. Deleting a device does not mean you have removed its shared runtime. Conversely, removing a runtime can leave you unable to run devices that depend on it.
Start by writing down the OS versions and device sizes you actually test. Include the oldest supported version and any reproduction environment for an unresolved bug. The newest runtime alone may not cover your project’s requirements. An old release is not automatically an unused release.
2. Remove an individual unused device
Stop the simulator session and any active tests. In Xcode, choose Window → Devices and Simulators, then select Simulators. Inspect the name, device type and OS version of the entry you plan to remove. If you use custom names, make sure the name still matches what the device is used for.
Control-click the selected simulator, choose Delete, and confirm after reviewing the dialog. Treat the device’s app data as lost when the device is deleted. Export any test documents or fixtures you still need first; reinstalling the app later is not a way to recover its old local state.
3. Remove an unused operating-system runtime
Open Xcode → Settings and look for Components. Apple’s current component guide lists platform support, optional components and installed runtimes separately. Review the installed versions and the storage Xcode says each removal would recover. Choose only a runtime outside your current testing needs.
Depending on the Xcode release, removal uses an information button followed by Delete, or a selected runtime and a minus button. Older versions may group downloads under Platforms. Follow the matching control and confirmation in your installed release rather than trying to delete an internal runtime folder in Finder.
4. Check what must stay available
Removing a downloaded runtime usually means downloading it again before you can test that OS. Plan around connection speed, offline work and compatibility with the Xcode version you use. Before a trip or a release deadline, the cost of recreating a test environment may outweigh the recovered space.
Keep source projects and release archives outside this decision. Simulator cleanup does not require deleting all of CoreSimulator, removing Xcode itself, or changing protected macOS folders. If a runtime appears in a disk scan but not in Xcode’s management interface, collect the path and installed Xcode version for support instead of forcing removal.
5. Verify your remaining test destinations
Return to a project and check its available run destinations. Launch a retained simulator and run the relevant tests. Confirm the particular device and OS combination you intended to keep still works. This is a more useful check than simply seeing a smaller folder total.
Compare available Mac storage after the removal completes. If development storage is still large, inspect Derived Data separately. Keep a small record of which runtimes you intentionally retain and why; that makes the next Xcode update easier to review without rebuilding your entire test setup from memory.
References & further reading
These guides combine the linked official guidance with ClearDisk’s documented behavior. Your files and app settings determine the right next step.