How to Free Up 20 GB Fast for a macOS Update — 2026 Walkthrough

Apple's macOS installers routinely demand 12–20 GB of free space, and the message "Your disk does not have enough free space" tends to appear at the worst possible moment. If you need to free up space for a macOS update fast, this walkthrough covers what to clear first, what is safe to delete, and what to leave alone — so you can get the installer running in minutes, not hours.

Why macOS Updates Need So Much Space

The installer downloads a full OS image, unpacks it alongside your existing system, migrates your data, and only then removes the old copy. At peak, macOS 15 Sequoia and later require roughly 13–20 GB depending on your current version. That number is not negotiable — the installer checks before it begins and will refuse to proceed if you fall short.

The good news: a typical Mac accumulates 10–30 GB of recoverable waste in caches, logs, and purgeable space that can be cleared without touching a single document or photo.

How to Free Up Space for a macOS Update Fast: The Quick Method

If you have five minutes, the fastest path is to let a tool handle the scan and cleanup for you. Crumb is a native macOS menu-bar app that runs a one-click Clean covering system caches, user caches, logs, temp files, and purgeable space — all the categories below, in one pass.

1. Download Crumb and open it from your menu bar.
2. Click Clean. Crumb scans and shows you exactly how much it will recover before removing anything.
3. Confirm the cleanup. Most Macs recover 5–15 GB in under a minute.
4. Return to System Settings → General → Software Update and retry the download.

Cleaning is permanent — files removed cannot be recovered from Trash. Crumb is explicit about what it will delete, so review the summary before confirming.

What Crumb's Clean Actually Removes

• System caches — /Library/Caches/ and derived data macOS rebuilds automatically.
• User caches — ~/Library/Caches/, populated by browsers, Xcode, Spotify, and most apps you use regularly.
• Log files — /var/log/, ~/Library/Logs/, and unified-log archives. Logs are never needed for normal use.
• Temp files — /private/tmp/ and /private/var/folders/ staging areas.
• Purgeable space — space macOS has already marked safe to reclaim (APFS optimized storage, iCloud stubs) but has not yet freed.

None of these categories contain documents, photos, or application data. Caches are rebuilt the next time you open the relevant app — you may notice slightly slower first-launch times for a day or two, which is normal.

Manual Steps if You Prefer the Terminal

If you would rather do it by hand, these commands are safe on macOS 12 Monterey through macOS 26 and later.

1. Clear your user cache

rm -rf ~/Library/Caches/*

This is the single highest-yield manual step. Close all apps first, then run it in Terminal. Expect 2–8 GB on a well-used machine.

2. Remove system logs

sudo rm -rf /private/var/log/asl/*.asl
sudo log erase --all

The second command erases the unified log store. You will be prompted for your password. This is safe; Console.app will simply start a fresh log after the next boot.

3. Flush the DNS and temp folder

sudo rm -rf /private/tmp/*
sudo dscacheutil -flushcache

4. Check purgeable space

macOS may be sitting on gigabytes of purgeable space that Finder does not surface. You can trigger a flush with:

du -sh ~/Library/CloudStorage 2>/dev/null

If you use iCloud Drive with "Optimize Mac Storage" enabled, open Finder, right-click large folders inside iCloud Drive, and choose Remove Download. The files stay in iCloud; only the local copy is removed.

Larger Wins: What Else Eats Space

Caches and logs may not be enough if your disk is severely constrained. Here is a comparison of common space hogs by risk level:

Removing old macOS installers

If a previous installer (e.g. Install macOS Sonoma.app) is still sitting in /Applications, delete it from Finder. Each one is 12–20 GB and is no longer needed once the update completes.

Deleting Xcode derived data

rm -rf ~/Library/Developer/Xcode/DerivedData

Safe on any developer Mac. Xcode regenerates this the next time you build a project. If you are not a developer, this folder likely does not exist.

After Clearing Space: Re-check Before You Update

Once you have freed up space, verify the total before relaunching the installer:

1. Open the Apple menu → About This Mac → More Info (macOS 13+) or Storage tab.
2. Look for "Available" space. The number updates within a few seconds of clearing files.
3. Add a 3–5 GB buffer beyond the installer's stated requirement — some updates expand further during installation.

If you are still short after clearing caches and logs, revisit the table above and look at iOS backups or unused apps. Crumb's Visualize tab shows a full disk map and sorts your largest folders, which makes it easy to spot what is consuming the most space without guessing.

What Not to Delete

A few locations look deletable but are not:

• ~/Library/Application Support/ — contains app databases, preferences, and saved state. Delete per-app folders only if you are fully uninstalling that app.
• /Library/Extensions/ and /System/Library/ — system files; leave these alone entirely.
• ~/Library/Keychains/ — passwords and certificates. Never delete.
• Time Machine backup drives — clearing these does not free internal disk space.

Conclusion

Clearing caches, logs, and purgeable space is the fastest and safest way to make room for a macOS update without touching any of your actual files. On most Macs, these categories alone recover enough space to get the installer running. If you want to skip the manual steps, a one-click Clean with Crumb covers all of them in under a minute — then you can get back to the update.