Fix "Not Enough Disk Space" to Install Xcode — The Real Solution

The App Store says Xcode is 12GB. Your Mac has 25GB free. But the install fails with "not enough disk space." Here's why Xcode actually needs 40-60GB to install, and how to free that space fast.

You check the App Store. Xcode is listed as a 12GB download. You have 25GB free. That should be more than enough, right?

You tap "Update" (or "Get"), wait for the download, and then: "Not enough disk space to install Xcode."

This is one of the most frustrating experiences in iOS development, and it happens to nearly every developer at least once. The App Store's listed size is misleading — it shows the compressed download size, not the total space Xcode needs during installation. The real requirement is typically 40-60GB of free space, even though the final installed app is only about 12-15GB.

In this guide, we'll explain exactly why this happens, give you emergency fixes to free space right now, and set up a long-term strategy so you never hit this wall again.

Why Xcode Needs 3-5x Its Listed Size to Install

The gap between Xcode's App Store listing and its actual installation space requirement comes from several factors:

1. Compressed Download vs. Extracted Size

The App Store shows the compressed download size (approximately 12GB). But Xcode is heavily compressed for distribution. The extracted application bundle is 14-16GB. During installation, macOS needs both the compressed download AND the extracted version simultaneously on disk, which means you need at least 26-30GB just for the app itself.

2. Temporary Extraction Working Space

The App Store extraction process uses temporary working space in addition to the source and destination files. macOS creates intermediate files during the decompression and verification process. This adds another 5-10GB of temporary space requirement.

3. Old Version Isn't Removed Until After New Version Is Ready

If you're updating Xcode (not installing fresh), macOS keeps the old version on disk until the new version is fully extracted and verified. This means you need space for both the old Xcode (12-15GB), the new download (12GB compressed), the new extraction (14-16GB), and working space. That's 43-53GB of space needed during an update, even though the net change is only a few gigabytes.

4. First Launch Component Downloads

After installation, Xcode downloads additional components on first launch: simulator runtimes, platform support files, and toolchains. A single iOS simulator runtime adds 5-7GB. If Xcode automatically installs the latest runtime, your post-installation space requirement grows further.

5. macOS Needs Breathing Room

macOS itself needs free space for virtual memory (swap), system caches, and Time Machine local snapshots. Apple recommends keeping at least 10-15GB free at all times for system stability. If your free space drops below this threshold during installation, macOS may abort the process even if there's technically enough room for the files.

The Bottom Line

For a clean install, plan for 40GB free. For an update from a previous version, plan for 50-60GB free. Yes, it's absurd. No, Apple hasn't fixed this messaging in the App Store.

Emergency Fixes: Free Space RIGHT NOW

If you're stuck right now trying to install Xcode, here are the fastest, safest ways to reclaim space. We've ordered them by safety (safest first) and impact (biggest space savings first).

Fix 1: Delete DerivedData (Safe, Immediate, 5-30GB)

DerivedData is Xcode's build cache. Deleting it is completely safe — Xcode rebuilds it the next time you open a project. This is the single best quick win for freeing developer storage.

# Check current size
du -sh ~/Library/Developer/Xcode/DerivedData/

# Delete everything
rm -rf ~/Library/Developer/Xcode/DerivedData/*

Expected recovery: 5-30GB depending on how many projects you've worked on. If you've never cleaned DerivedData, this alone might solve your problem.

Fix 2: Delete Old iOS Simulators (Safe, 5-20GB)

Simulator devices accumulate over time. Each one stores its own filesystem, installed apps, and caches. Old simulators for iOS versions you no longer target are dead weight.

# Delete simulators whose runtimes are no longer installed
xcrun simctl delete unavailable

# List remaining simulators
xcrun simctl list devices

# Delete specific simulators you don't need
xcrun simctl delete <DEVICE-UUID>

You can also delete unused simulator runtimes (the OS images themselves):

# List installed runtimes
xcrun simctl runtime list

# Delete old runtimes (each is 5-7GB)
xcrun simctl runtime delete <RUNTIME-IDENTIFIER>

Expected recovery: 5-20GB. If you have 3+ runtimes installed, deleting all but the latest can free 10-15GB.

Fix 3: Delete Device Support for Old iOS Versions (Safe, 3-15GB)

Every time you connect a physical iPhone or iPad to your Mac, Xcode downloads debug symbols for that device's iOS version. These files are 2-5GB per iOS version and accumulate forever.

# See what's there
ls -lh ~/Library/Developer/Xcode/iOS\ DeviceSupport/

# Delete support for old versions
# Keep only the version running on your current test device
rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/15.*
rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/16.*
rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/17.*

Expected recovery: 3-15GB. If you've connected devices running 3+ different iOS versions over the years, this is substantial. Xcode will re-download the symbols the next time you connect a device with that iOS version.

Fix 4: Delete Old Archives (Review First, 2-20GB)

Every time you archive a build (Product > Archive in Xcode), the full build is saved. These archives are used for App Store submissions and crash report symbolication. Old archives are rarely needed.

# Check how much archives are using
du -sh ~/Library/Developer/Xcode/Archives/

# List archives by date
ls -la ~/Library/Developer/Xcode/Archives/

# Delete archives from previous years
rm -rf ~/Library/Developer/Xcode/Archives/2024*
rm -rf ~/Library/Developer/Xcode/Archives/2023*
rm -rf ~/Library/Developer/Xcode/Archives/2022*

A word of caution: If you have an app on the App Store and need to symbolicate crash reports for older versions, you'll need the dSYM files from those archives. If in doubt, keep archives for your most recent release and delete the rest. You can also extract just the dSYM files (much smaller) and delete the rest of the archive.

Expected recovery: 2-20GB depending on how many apps you've archived and how often.

Fix 5: Clear Swift Package Manager Cache (Safe, 1-5GB)

Swift Package Manager caches downloaded dependencies. This cache can be safely deleted — packages will be re-downloaded when needed.

# Check size
du -sh ~/Library/Caches/org.swift.swiftpm/

# Delete
rm -rf ~/Library/Caches/org.swift.swiftpm/

Expected recovery: 1-5GB. More if your projects use many SPM dependencies.

Fix 6: Clear SwiftUI Previews Cache (Safe, 5-80GB)

# Check size
du -sh ~/Library/Developer/Xcode/UserData/Previews/

# Clean
xcrun simctl --set previews delete all

Expected recovery: 5-80GB. This is often the single biggest surprise — developers who haven't checked this directory before sometimes find 40-60GB of Preview cache.

Fix 7: Empty Trash and Clear Downloads (Obvious but Often Forgotten)

# Check Downloads folder size
du -sh ~/Downloads/

# Check Trash size
# (No Terminal command; use Finder > Empty Trash)

# Also check for large .dmg and .zip files you've forgotten about
find ~/Downloads -name "*.dmg" -o -name "*.zip" -o -name "*.pkg" | head -20

Fix 8: Purge Time Machine Local Snapshots (If Needed)

macOS keeps Time Machine snapshots locally even when the Time Machine drive isn't connected. These can consume 10-50GB.

# List local snapshots
tmutil listlocalsnapshots /

# Delete all local snapshots
tmutil deletelocalsnapshots /

Note: This deletes your local backup safety net. Only do this if you have a current Time Machine backup on an external drive or if you don't use Time Machine.

The Quick Command Sequence

If you want to run all the safe cleanup steps at once, here's a single script:

#!/bin/bash
echo "=== Xcode Emergency Cleanup ==="

echo "1. DerivedData..."
du -sh ~/Library/Developer/Xcode/DerivedData/ 2>/dev/null
rm -rf ~/Library/Developer/Xcode/DerivedData/*

echo "2. Unavailable simulators..."
xcrun simctl delete unavailable 2>/dev/null

echo "3. SwiftUI Previews cache..."
du -sh ~/Library/Developer/Xcode/UserData/Previews/ 2>/dev/null
xcrun simctl --set previews delete all 2>/dev/null

echo "4. SPM cache..."
du -sh ~/Library/Caches/org.swift.swiftpm/ 2>/dev/null
rm -rf ~/Library/Caches/org.swift.swiftpm/

echo "5. Old Device Support (keeping latest)..."
du -sh ~/Library/Developer/Xcode/iOS\ DeviceSupport/ 2>/dev/null
# Uncomment and adjust versions as needed:
# rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/16.*
# rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/17.*

echo "=== Done ==="
echo "Free space: $(df -h / | tail -1 | awk '{print $4}')"

Save this as xcode-emergency-cleanup.sh, make it executable (chmod +x xcode-emergency-cleanup.sh), and run it whenever you need quick space recovery.

Alternative: Download Xcode from developer.apple.com

If you keep hitting App Store installation failures, there's an alternative approach: download Xcode directly from Apple's developer portal as a .xip file.

Why This Can Help

  • More control over the process: You download the .xip file first, then extract it manually. This lets you manage the extraction location and timing.
  • Choose where to extract: You can extract on an external drive, verify it works, and then move only the Xcode.app to /Applications.
  • No App Store overhead: The App Store installation process has its own temporary file management that can require extra space. Direct download avoids this.
  • Resume-able downloads: If the download fails partway through, you can resume it (or use a download manager). The App Store often restarts from scratch.

How to Do It

  1. Go to developer.apple.com/download/all/ (requires free Apple Developer account)
  2. Search for the Xcode version you need
  3. Download the .xip file (approximately 8-12GB)
  4. If space is extremely tight, download directly to an external drive: 
    # Download to external drive using curl (if you have the direct URL)
cd /Volumes/ExternalSSD/
# Or simply use Safari and choose the external drive as download location
  5. Extract the .xip file: 
    # Extract in current directory
xip -x Xcode_17.2.xip

# This creates Xcode.app in the current directory
  6. Move Xcode.app to /Applications: 
    # Remove old Xcode first to save space
sudo rm -rf /Applications/Xcode.app

# Move new Xcode
mv Xcode.app /Applications/
  7. Delete the .xip file to reclaim download space: 
    rm Xcode_17.2.xip
  8. Run first launch setup: 
    sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -runFirstLaunch

The key advantage: by removing old Xcode before extracting the new one and using an external drive for the download/extraction, you need much less internal free space than the App Store method requires.

Long-Term Prevention: Never Hit This Error Again

Once you've successfully installed Xcode, set yourself up so this doesn't happen next time:

1. Monitor Free Space Proactively

Don't wait until the App Store tells you there's a problem. Check your free space before every major Xcode update:

df -h /

If you have less than 60GB free and an Xcode update is coming (check the developer.apple.com release notes or wait for WWDC each June), run a cleanup first.

2. Set Up a Monthly Cleanup Routine

The best defense is regular maintenance. Once a month, clean DerivedData, Previews cache, and old Device Support files. This takes 5 minutes and prevents the gradual space creep that leads to "not enough disk space" errors.

3. Use Alerts

macOS will warn you when storage is very low, but by that point you're already in trouble. Use a tool that alerts you earlier — say, when free space drops below 50GB, giving you time to clean up before it becomes an emergency.

4. Keep Archives Off Your Main Drive

Archives are the most wasteful category for most developers. Unless you're actively submitting to the App Store, move old archives to an external drive or cloud storage. A single year's worth of archives for 2-3 apps can easily be 10-15GB.

5. Plan for Xcode Updates

Major Xcode versions (released each fall) tend to be the largest and require the most space to install. Mark your calendar for September/October each year and do a thorough cleanup before the new Xcode drops. Minor updates (17.1, 17.2, etc.) are smaller but still need temporary space.

What If Nothing Works?

If you've cleaned everything listed above and still don't have enough space, you have a few remaining options:

  • Delete other large applications: Check System Settings > General > Storage > Applications and sort by size. Games, video editors, and design tools can be surprisingly large.
  • Offload media to iCloud: Enable "Optimize Mac Storage" for Photos and iCloud Drive. This keeps only thumbnails and recently accessed files on your Mac.
  • Use the external drive method: Download and extract Xcode entirely on an external drive, then move only the final Xcode.app to your internal drive.
  • Consider Xcode alternatives for specific tasks: If you're installing Xcode just for Command Line Tools (git, clang), you can install them standalone with xcode-select --install — that only needs 2-4GB instead of 40-60GB.