You clicked "Update Now," watched the installer download for twenty minutes, and then hit a wall: "macOS cannot be installed because there is not enough space available." If you're struggling with cant update macos not enough space errors, you're not alone — and the fix is more straightforward than Apple's vague error message suggests. This guide explains exactly how much room the installer really needs, why the estimate looks so alarming, and the precise steps to clear enough space to let the update proceed.
How Much Space Does a macOS Update Actually Need?
The short answer is: more than the download size implies. A lot more.
The installer you download is a compressed package, typically 8–14 GB for a major release. But when the installer expands and prepares to write to disk, it needs room for:
- The expanded installer payload (often 2–3× the download size)
- A full snapshot of your current system volume (used to roll back if something goes wrong)
- Scratch space for the update process itself
The practical result is that macOS commonly asks for 20–40 GB of free space even if the final installed update only occupies a few extra gigabytes. If you're wondering how much space is needed for a macOS update, plan for at least 20 GB of headroom regardless of the stated download size.
| macOS Version | Typical Download | Space Required at Install Time |
|---|---|---|
| macOS Sequoia (15) | ~12 GB | ~25–35 GB |
| macOS Sonoma (14) | ~12 GB | ~25–35 GB |
| macOS Ventura (13) | ~11 GB | ~20–30 GB |
| Minor point releases | 1–4 GB | ~8–15 GB |
These are real-world ranges observed by users — Apple does not publish official "required space" figures, and the number the installer shows you is a worst-case estimate that includes the rollback snapshot.
Why the "Not Enough Disk Space" Error Can Be Misleading
macOS distinguishes between available space and purgeable space. In About This Mac (or System Information), you may see something like "150 GB used, 40 GB available, 20 GB purgeable." The installer's required-space check sometimes counts purgeable space and sometimes does not, depending on the macOS version you're running.
Purgeable space includes items that iCloud Drive has already synced remotely and can evict from local storage, plus optimized storage candidates. The OS should clear purgeable space automatically before installing, but in practice this doesn't always happen — especially if iCloud sync is stalled or the drive is nearly full. That's one of the main reasons the not enough disk space to update macOS error appears even when Finder seems to show adequate free space.
Step-by-Step: Free Enough Space to Run the macOS Update
Work through these in order. After each section, relaunch System Settings → General → Software Update to see whether the installer will now proceed.
1. Delete the Partial Installer (If You Already Downloaded It)
If the download completed but the install failed, the installer app may still be sitting in /Applications, consuming 12+ GB. Delete it first so the space is available before you attempt to free more.
- Open Finder and go to Applications.
- Look for "Install macOS [version]" and drag it to the Trash.
- Empty the Trash.
Then restart the download from Software Update. This alone sometimes resolves the issue because the system can now allocate that reclaimed space as scratch space.
2. Clear System and User Caches
Caches accumulate quickly — browsers, Xcode derived data, app caches — and can easily reach 10–20 GB on an actively used Mac. These are safe to delete; apps rebuild their caches on next launch.
User caches live at:
~/Library/Caches
System caches live at:
/Library/Caches
To inspect and clean them manually:
- In Finder, press Shift + Cmd + G and enter
~/Library/Caches. - Sort by size. Large folders from apps you don't use (old browser profiles, game launchers, etc.) are good candidates.
- Move unwanted cache folders to the Trash and empty it.
If you'd rather not dig through folders manually, Crumb scans both user and system cache locations in one pass and shows you exactly what each folder contains before you delete anything — useful when you're not sure whether a given cache is actively used.
3. Remove Old iOS Device Backups
iTunes and Finder backups of iPhones and iPads can each be several gigabytes. Find them at:
~/Library/Application Support/MobileSync/Backup
Or remove them cleanly through Finder: connect your device (or go to Finder → your device in the sidebar) and click Manage Backups. Delete any backup you no longer need.
4. Clear Xcode Derived Data and Archives (Developers Only)
If you have Xcode installed, derived data alone can consume 20–50 GB:
~/Library/Developer/Xcode/DerivedData
~/Library/Developer/Xcode/Archives
DerivedData is entirely safe to delete — Xcode recreates it on the next build. Archives are your signed app builds; only delete old ones you're certain you no longer need for distribution.
From the Terminal:
rm -rf ~/Library/Developer/Xcode/DerivedData
5. Empty the Trash and Check Downloads
It sounds obvious, but a full Trash and a bulky Downloads folder frequently hold gigabytes of forgotten disk images, zip files, and installers. Empty the Trash, then sort Downloads by size and delete anything you no longer need.
6. Remove Large Unused Applications
Identify the largest apps on your system via Terminal:
du -sh /Applications/* | sort -rh | head -20
If you find applications you no longer use, simply dragging them to the Trash leaves behind support files, preferences, and caches scattered throughout ~/Library. For a cleaner removal that also catches leftover files, use a dedicated uninstaller. Download Crumb — its Uninstall tab finds the full set of files associated with an app so nothing is orphaned.
7. Let macOS Purge Its Own Purgeable Space
If iCloud Drive is your main suspect, you can nudge macOS to evict local copies of files it has already uploaded. Open Terminal and run:
sudo periodic daily weekly monthly
This runs the standard maintenance scripts. For purgeable space specifically, the most reliable method is simply to let macOS handle it: quit all apps, then launch a large file copy that fills the disk — the system will purge as needed. A less drastic option is to check System Settings → Apple ID → iCloud → iCloud Drive → "Optimize Mac Storage" and confirm it is enabled.
8. Check for Hidden Large Files with Terminal
Some large files hide in unexpected places — virtual machine disk images, Logic Pro sample libraries, old Time Machine local snapshots. Find the biggest directories on your startup disk:
sudo du -sh /* 2>/dev/null | sort -rh | head -20
Run this, look for unexpected entries, then investigate before deleting. Time Machine local snapshots appear under /.MobileBackups (older macOS) or inside the APFS volume. You can list and delete them with:
tmutil listlocalsnapshots /
tmutil deletelocalsnapshots [snapshot-date]
Local snapshots are safe to delete if you have a full Time Machine backup on an external drive. Do not delete your live Time Machine backup destination or any folder in /System — those are not safe to touch.
What You Should NOT Delete
A few areas that look large but should be left alone:
- /System — Protected by System Integrity Protection (SIP) for good reason. Leave it entirely alone.
- ~/Library/Application Support — Contains app data (save files, databases, licenses). Review carefully; don't bulk-delete.
- Active virtual machine disk images — Deleting a running or recently used VM disk can corrupt its state.
- Current Time Machine backups — Do not delete your backup set to free space on the same drive you're trying to update.
- Anything in /private/var/db — System databases; not safe to modify manually.
Remember: cleaning is permanent. If you are unsure whether a folder is safe to remove, use the "Is this safe to delete?" feature in Crumb's AI assistant, which explains what a folder does and what the risk of removing it would be — without ever sending your file contents anywhere.
After Cleaning: Retry the Update
Once you've reclaimed 20–40 GB, go to System Settings → General → Software Update. If the installer was already downloaded, it may attempt to restart the install immediately. If not, it will re-download. Allow the process to run without interrupting it — especially the "Preparing macOS" phase, which is when the system performs its final space check and expands the payload.
If the error persists after freeing space, restart your Mac and try again. A restart clears temporary swap files and gives the installer a clean environment for its space calculations.
Conclusion
The macos update needs more space error is frustrating because the amount the installer demands far exceeds what the final update actually occupies on disk. The culprit is almost always accumulated caches, old iOS backups, Xcode derived data, or purgeable iCloud content that the system failed to evict automatically. Work through the steps above methodically — caches first, then large applications and developer artifacts — and you'll typically recover the 20–40 GB the installer needs within an hour, without touching anything that matters.