Skip to content

Xcode needs far more space than the download, and keeps needing it

How much space Xcode takes, why it keeps growing, and what to delete when it is too much, with the folders and commands to check your own Mac.

5 min read

Seen on X, 1.2K views
Was struggling with macbook storage these past few months then i find out FAT ASS XCODE WAS TAKING UP 60 GIGABYTES OF SPACE

Xcode itself is around 20 GB, it needs roughly twice that free while it installs, and it keeps growing after that, because simulators, build caches and device files live outside the app. The App Store shows one number, and it is the least useful of several.

How much space does Xcode take?

Three figures matter: the space to install it, the space it occupies afterwards, and the space it takes over the following year.

StageSpace neededNotes
Download and expandRoughly double the final sizeBoth exist at once during install
Xcode itselfAround 20 GBThe application bundle
One additional simulator runtime5 to 8 GB eachiOS, watchOS and tvOS are separate
DerivedData after a few projects5 to 30 GBGrows with every build
Device support after a few devices1 to 3 GB per iOS versionKept per device version connected
ArchivesHundreds of MB per releaseNever regenerable

Why does Xcode take up so much space?

Because most of it is not in Xcode.app. Simulator runtimes, DerivedData, device support and archives all live in other folders, so checking the size of the app tells you a fraction of the total. Simulators are usually the largest part.

This measures the folders on your own Mac:

du -sh /Applications/Xcode.app ~/Library/Developer/Xcode/DerivedData \
  ~/Library/Developer/Xcode/Archives ~/Library/Developer/Xcode/iOS\ DeviceSupport \
  /Library/Developer/CoreSimulator 2>/dev/null
xcrun simctl runtime list

Do I need all of Xcode, or just the Command Line Tools?

If you only need git, a compiler or Homebrew, the Command Line Tools are enough, and they are far smaller: about 1.3 GB, measured on macOS 27.0.1 in October 2026. Full Xcode is for building iOS and Mac apps and running simulators. Command Line Tools or full Xcode covers switching.

What can I delete when Xcode takes too much space?

Three folders grow all the time, and two of them are safe to clear whenever you like. DerivedData is the largest and rebuilds itself. Simulator devices and runtimes build up per iOS version. Archives and device support is the one to be careful with, because archives contain the symbols that make crash reports from shipped builds readable.

  • Delete simulator runtimes for platforms you do not target, with xcrun simctl runtime delete. They download again on demand, so this is the cheapest large win.
  • Clear ~/Library/Developer/Xcode/DerivedData. Xcode rebuilds what it needs on the next build.
  • Remove device support folders for iOS versions you no longer test on.
  • Keep archives for anything you shipped. Treat them as work, not as cache.

How do I install Xcode on a Mac that is short of space?

  • Clear space before starting, since a failed install leaves a partial download behind.
  • Install Xcode without additional platforms, then add only the simulator runtimes you need.
  • Keep DerivedData on the internal drive; it is written constantly and an external drive is a poor trade for it.

Is a 256 GB Mac enough for Xcode?

It works, with a routine. An external SSD is fine for source, simulators and archives, but not for DerivedData, which is written to constantly during a build. On a 256 GB Mac doing iOS work, Xcode plus two simulator runtimes plus a year of caches will use most of the drive, so clearing DerivedData regularly is not optional.

Related: Xcode.

Common questions

How much disk space does Xcode need?

Around 20 GB for the application, plus roughly double that during installation because the download and expanded copy coexist. Each additional simulator runtime is 5 to 8 GB, and caches grow continuously after that.

Why is Xcode using more space than it says?

Because DerivedData, simulator runtimes, device support and archives all live outside the application bundle. On one measured Mac, simulator storage alone was 35 GB across two locations.

How much space do the Xcode Command Line Tools take?

About 1.3 GB, measured on macOS 27.0.1 in October 2026, compared with around 20 GB for Xcode itself. They are enough for git, compilers and Homebrew.

Can I install Xcode on an external drive?

The application and simulator runtimes work from one, but DerivedData is written constantly during builds and belongs on the internal drive. Splitting it that way is the usual arrangement on a small Mac.

How do I reduce Xcode's disk usage?

Clear DerivedData regularly, delete simulator runtimes for platforms you do not target with xcrun simctl runtime delete, and remove device support folders for iOS versions you no longer test on.

Read next