Xcode Not Enough Disk Space on macOS: Check Storage Safely

Published Nov 18, 2019 2 minute read

Content edited Oct 13, 2026. This editorial update does not represent a new runtime test.

On this page

When Xcode reports not enough disk space, check available storage and large developer artifacts before deleting files. An installation can require space beyond the final application size for downloading and unpacking its contents.

Mac workstation illustration

Scope of the original case

The original note concerned Xcode 11 on macOS Catalina in 2019. It suggested clearing developer directories but incorrectly described DeviceSupport as simulator models. This revision distinguishes the types of data rather than recommending blanket deletion.

Check available storage

Use macOS’s storage view and compare the installation requirement with the volume where Xcode is being installed. Apple’s storage guidance describes ways to inspect and reclaim space. A Finder estimate, purgeable storage and immediately available installation space are not always the same view.

Read-only size inspection can help identify candidates:

df -h /
du -sh "$HOME/Library/Developer/Xcode/Archives"
du -sh "$HOME/Library/Developer/Xcode/iOS DeviceSupport"

A missing directory simply means that candidate is not present at that path. Do not replace it with a guessed system path and delete its contents.

Decide what is safe to remove

Archives: inspect them in Xcode Organizer. Preserve release archives and symbols required for distribution or crash investigation.
Simulator runtimes: manage unused runtimes through the relevant Xcode settings. They are distinct from physical-device support files.
DeviceSupport: evaluate data for device/OS combinations you no longer use; removing it may require Xcode to prepare support again.
Old installers and unrelated downloads: review these first if developer artifacts are still required.

Keep a backup before removing irreplaceable files. The original claim that a fixed number of gigabytes will always be recovered has been removed.

Verify the result

Check storage again, retry the intended installation, and launch Xcode. Confirm an existing project still builds and required devices or simulators remain usable. This revision did not remove files or install Xcode to reproduce the issue.

Related: Read-only root paths are a permissions and volume-layout problem, not evidence of a full disk.

← All articles