Apple's installer tells you it needs around 12–14 GB of free space to update macOS, but real-world installs routinely stall or fail at that margin. The actual headroom required — accounting for the download, a temporary unpack area, a Recovery snapshot, and breathing room for the system journal — is meaningfully higher. This guide gives you the honest numbers by Mac model and shows you exactly how to get there.
Why Apple's Stated Requirement Is Too Low
The figure Apple displays in Software Update reflects the compressed installer payload, not the total disk activity the update triggers. During a macOS Sequoia install, the system simultaneously needs room for:
- The full installer bundle (12–14 GB compressed, 22–26 GB expanded on disk during extraction)
- A new local Time Machine "before" snapshot (APFS Snapshot), which can consume 5–10 GB on an active system
- Swap and VM files that grow during the multi-stage boot process
- Temporary delta caches and kernel collections written to
/private/var/foldersand/Library/Updates
If the disk fills during any of these phases, the installer either rolls back or, worse, leaves the system in an incomplete state requiring a Recovery Mode reinstall. Giving yourself real headroom is not overcautious — it is the only reliable path.
How Much Free Space to Update macOS Sequoia: A Real-World Reference Table
The numbers below are based on observed install behavior across Mac models. "Minimum safe" means installs have succeeded at this level with a freshly rebooted Mac and minimal background processes. "Recommended" leaves enough room to avoid swap pressure and snapshot bloat.
| Mac model / storage capacity | macOS Sequoia installer size | Minimum safe free space | Recommended free space |
|---|---|---|---|
| Any Mac (256 GB SSD) | ~13 GB | 20 GB | 30 GB |
| Any Mac (512 GB SSD) | ~13 GB | 20 GB | 30 GB |
| Any Mac (1 TB+ SSD) | ~13 GB | 20 GB | 30 GB |
| Mac with Time Machine (local snapshots enabled) | ~13 GB | 25 GB | 35 GB |
| Mac with Optimized Storage on (iCloud Drive offloading) | ~13 GB | 22 GB | 32 GB |
Key takeaway: regardless of total disk size, you need at least 20 GB free before starting, and 30 GB if you want a comfortable margin. If Time Machine is writing local snapshots, budget 5 GB more.
How to Check Your Current Free Space
Open Terminal and run:
df -h /
Look at the Avail column. This reflects the true available space on your APFS volume, including purgeable space macOS can reclaim on demand. Also check System Settings → General → Storage for a breakdown by category.
To see how much space APFS local snapshots are consuming (Time Machine overhead), run:
tmutil listlocalsnapshots /
Each line is a snapshot. You can delete a specific snapshot with:
tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS
Replace YYYY-MM-DD-HHMMSS with the timestamp shown. Deleting local snapshots is safe as long as you have an external Time Machine backup or another backup strategy — local snapshots are an additional convenience layer, not your only backup.
What You Can Safely Clear Before Updating
These locations are safe to empty before an OS update. Nothing below removes user data or application preferences.
User caches
Most app caches live in ~/Library/Caches. Applications rebuild these automatically on next launch. To see what is in there:
du -sh ~/Library/Caches/*
To remove the contents (not the folder itself) of a specific app's cache, for example Safari:
rm -rf ~/Library/Caches/com.apple.Safari
Do not delete the entire Caches folder. Some apps write lock files there that break if the parent directory disappears. Clear individual subdirectories you recognize.
System-level caches
System caches live at /Library/Caches and /private/var/folders. The safest approach is to let macOS clear /private/var/folders on reboot — these are managed temp files and the OS purges them as needed. You can force a flush of font and dyld caches with:
sudo atsutil databases -remove
sudo update_dyld_shared_cache
These commands require your administrator password and are safe to run, though the system may take a few minutes to rebuild shared caches on next boot.
Old iOS device backups
iTunes and Finder store iPhone and iPad backups in ~/Library/Application Support/MobileSync/Backups. Old backups from devices you no longer own can safely be deleted. Check the size first:
du -sh ~/Library/Application\ Support/MobileSync/Backups/*
Duplicate downloads and large files
The Downloads folder is the single fastest win. Sort by size in Finder (View → Show View Options → Sort by Size) and remove anything you no longer need. Old disk images (.dmg files) from already-installed apps are safe to delete.
What to leave alone
Do not manually clear /System/Library, /usr/lib, or anything inside the macOS system volume — these are sealed in macOS Sequoia and protected by System Integrity Protection (SIP). Do not delete ~/Library/Application Support wholesale; it contains application data you likely want.
Hitting the Number Faster with a Dedicated Tool
Manually hunting through caches and Downloads works, but it is slow and easy to miss large items buried deep in the file system. Crumb was built specifically for this situation: a single-click Clean pass removes system caches, user caches, logs, temp files, and purgeable space across every user account. The Visualize tab shows a whole-Mac disk map so you can immediately see what is consuming the most space — useful for spotting large orphaned files or a bloated application support folder before an update.
If you also have apps you have been meaning to remove, the Uninstall tab finds an application's leftover files (preferences, caches, containers, launch agents) alongside the app bundle, so you reclaim the full footprint rather than just the app itself.
Cleaning is permanent — there is no undo for cleared caches short of restoring from a backup — so review what Crumb finds before confirming. The tool's "Is this safe to delete?" AI explains any unfamiliar folder before you commit.
The Update Checklist
- Confirm you have an external backup (Time Machine to an external drive, or another verified backup).
- Run
df -h /in Terminal. If Available is below 30 GB, proceed with the steps above. - Delete old local Time Machine snapshots with
tmutil deletelocalsnapshotsif they are eating space. - Clear
~/Library/Cachessubdirectories for apps you recognize, and purge your Downloads folder. - Optionally, run a one-click Clean pass with Crumb to handle system caches, logs, and purgeable space automatically.
- Reboot once before starting the macOS update — this flushes swap files and lets the OS reclaim VM space.
- Open System Settings → General → Software Update and begin the install with confidence.
Frequently Missed Space Hogs
If you have cleared the obvious locations and still fall short, check these:
- Xcode derived data:
~/Library/Developer/Xcode/DerivedData— can reach 20–40 GB on an active development machine; safe to delete entirely. - Simulator runtimes:
~/Library/Developer/CoreSimulator/Cryptex/Images— old iOS simulator images you no longer use. - GarageBand / Logic sound libraries:
/Library/Application Support/GarageBandand/Library/Audio/Apple Loops— instrument packs can total 50+ GB; you can re-download any you delete later. - Mail attachments:
~/Library/Mail/V10/— Mail downloads every attachment it has ever received; old large attachments accumulate invisibly. - Trash across all volumes: Empty the Trash from every mounted external drive, not just the main volume.
Conclusion
The honest minimum for a smooth macOS Sequoia update in 2026 is 20 GB free, and 30 GB if your Mac has Time Machine local snapshots or heavy swap usage. Apple's displayed requirement is accurate for the installer alone — not for the full install process. Clear your caches, prune old backups and downloads, and reboot before you start. Those steps alone get most Macs across the line without any additional tooling. If you want the fastest path, a clean pass with Crumb handles the cache and log side of things in a single step, leaving you free to focus on the actual update.