SiftMac
Who it’s for · Updated 21 November 2026

What fills an iOS or Mac developer’s Mac, and what Xcode makes again

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What fills an iOS developer’s Mac
  2. What’s safe to clear, and what to keep
  3. How SiftMac helps with Xcode
  4. A cleanup routine for Xcode users
  5. Questions

1. What fills an iOS developer’s Mac

Almost all of it sits in ~/Library/Developer, which Finder hides. The parts, and what happens when each one goes:

What fills itWhere it livesComes back?More
Build data and indexes, one folder per project~/Library/Developer/Xcode/DerivedDataYes, on the next buildDerivedData
Simulators, with their installed apps and data~/Library/Developer/CoreSimulator/DevicesRecreated emptySimulators
Simulator runtimes, one per OS versionListed in Xcode › Settings › ComponentsDownloaded againSimulators
Debug symbols from devices you’ve connected~/Library/Developer/Xcode/iOS DeviceSupport, and a folder like it per platformCopied again when that device connectsDevice support
Archives of builds you exported or uploaded~/Library/Developer/Xcode/ArchivesNoArchives
SwiftUI preview simulators~/Library/Developer/Xcode/UserData/PreviewsRecreated when a preview runs—
Swift packages~/Library/Caches/org.swift.swiftpm, and each package’s .buildYes, resolved and built againSwiftPM caches
CocoaPods~/Library/Caches/CocoaPods, each project’s PodsYes, with pod installCocoaPods
A second Xcode, often a betaApplicationsOnly by downloading it again—
Restore images for iPhones and iPads~/Library/iTunes/iPhone Software UpdatesDownloaded again when needed.ipsw files

Their sizes, biggest last; folders you don’t have are skipped:

du -sh ~/Library/Developer/Xcode/DerivedData ~/Library/Developer/Xcode/Archives ~/Library/Developer/Xcode/*DeviceSupport ~/Library/Developer/Xcode/UserData/Previews ~/Library/Developer/CoreSimulator ~/Library/Caches/org.swift.swiftpm ~/Library/Caches/CocoaPods 2>/dev/null | sort -h

Then the simulators and runtimes themselves:

xcrun simctl list devices
xcrun simctl runtime list

2. What’s safe to clear, and what to keep

Clear freely

Think before deleting

3. How SiftMac helps with Xcode

SiftMac’s developer files know Xcode’s folders, and judge each by how long you’ve left it alone: 1, 3 or 6 months, your choice.

It doesn’t list archives or simulator runtimes: archives are yours, and runtimes belong to Xcode’s Components settings. Developer items start unticked and are deleted rather than shelved, since Xcode makes them again.

4. A cleanup routine for Xcode users

  1. Note the OS versions your test devices and deployment target need. Device support and runtimes for anything older are candidates.
  2. Quit Xcode and Simulator.
  3. Clear DerivedData, or only the stale projects SiftMac lists.
  4. Run xcrun simctl delete unavailable, then check xcrun simctl list devices for simulators you never boot.
  5. In Xcode › Settings › Components, delete runtimes for OS versions you no longer test on.
  6. Delete older device support folders, keeping the newest for each device you test on.
  7. In the Organizer, delete archives of builds nobody runs, keeping one for each live version.
  8. Open your current project and build it once, so it’s indexed before you need it.

Questions

Will deleting DerivedData lose code or settings?

No. DerivedData holds build products, indexes and logs that Xcode makes from your code. Your projects, schemes and Xcode settings live elsewhere. The cost is one slower build and a re-index per project.

Is it safe to delete iOS DeviceSupport?

Yes. It’s debug symbols Xcode copied from devices you’ve connected, one folder per OS version. If you connect a device running a version you removed, Xcode copies its symbols again, so that first connection is slower.

Can I delete the whole CoreSimulator folder?

Better not by hand. Simulators are tracked by simctl and runtimes are managed in Xcode’s Components settings, so delete simulators with xcrun simctl delete and runtimes in Xcode. Quit Simulator first either way.

How SiftMac handles it. SiftMac lists DerivedData per project, older device support folders and unused or unavailable simulators, removes simulators through simctl, and never lists archives, simulator runtimes or a simulator that’s running.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works