macOS Tahoe Storage Requirements: Space Needed vs Sequoia

If you have opened Software Update recently and seen macOS Tahoe waiting for you, the first question most Mac users ask is a practical one: do I have enough room? The macOS Tahoe storage requirements are real, the installer will refuse to proceed if you fall short, and the space you need is not just the installer download — the OS itself expands on disk during installation. This guide walks you through exactly how much free space Tahoe needs, how its footprint compares to Sequoia, and what to delete (and what not to) when your Mac comes up short.

macOS Tahoe Storage Requirements at a Glance

Apple's official guidance for macOS Tahoe lists a minimum of 20 GB of free space to install the upgrade. In practice, the installer downloads roughly 12–14 GB, but it also needs working room to unpack, stage the update volume, and retain a recovery snapshot — which together demand significantly more headroom than the raw download size suggests.

On an APFS volume (the default since High Sierra), macOS uses a sealed system volume, meaning the OS itself lives on a read-only snapshot separate from your data. During an upgrade, a second snapshot is created temporarily, so your free space requirement spikes at the moment the installer does its work. If you are tight on space, even showing 20 GB free can sometimes trigger a warning; 25–30 GB of free space gives the installer comfortable room to finish without interruption.

What "Free Space" Actually Means on APFS

APFS pools space across volumes on the same container, so Finder's "available" figure already accounts for shared space. However, macOS also maintains purgeable space — files it considers safe to reclaim automatically (iCloud-offloaded documents, cached downloads, old Time Machine local snapshots). The installer can use some purgeable space, but it is not guaranteed to clear it before deciding whether to proceed. The safest approach is to have your available figure, not just available-plus-purgeable, meet the requirement.

To check your true available space:

df -h /

Look at the Avail column for your root volume. You can also run:

diskutil info / | grep -E "Free|Available|Purgeable"

Tahoe vs Sequoia Storage: How the Footprints Compare

The installed size of macOS grows gradually with each major release due to new frameworks, updated language models for on-device AI, and expanded system assets. The table below reflects measured installed sizes on a typical MacBook Pro (Apple silicon); your numbers will vary slightly by model and language pack selection.

The delta between Sequoia and Tahoe is modest in raw GB — Tahoe's larger on-device intelligence components account for most of the growth. The bigger concern is usually not the OS footprint itself but the state of your disk before the upgrade: caches that have accumulated over months, developer derived data, and old iOS device backups are the usual culprits that push available space below the threshold.

Why the Installer Says "Not Enough Space to Update macOS"

"Not enough space to update macOS" is one of the most common Mac upgrade errors. It happens for a few distinct reasons:

• Actual free space is genuinely low. Your drive is full. Deletion is the only path forward.
• Purgeable space is counted in Finder but not by the installer. You may see 22 GB "available" in Finder while the installer sees only 11 GB truly free.
• A previous failed upgrade left a partial installer. The /Applications folder may hold an old Install macOS bundle that is taking 13+ GB.
• Time Machine local snapshots are large. Run tmutil listlocalsnapshots / to see how many are present.

How to Free Space Before Installing Tahoe

Work through these steps in order. Each one is reversible in concept, but in practice most of these deletions are permanent — do not remove anything you have not backed up or are not certain about.

1. Delete any old macOS installer in /Applications.
   If /Applications/Install macOS Sequoia.app (or an earlier version) is present, trash it. These are typically 13 GB each and serve no purpose once the upgrade is complete.
2. Clear user cache files.
   Open Finder, press Cmd+Shift+G, navigate to ~/Library/Caches, and delete the contents of app-specific subdirectories you recognize. Do not delete the entire Caches folder or subfolders whose purpose is unclear — some caches are rebuilt automatically, but others contain data that looks like cache but is not.
3. Clear system-level caches and logs.
   In Terminal:

   sudo rm -rf /Library/Caches/*
   sudo rm -rf /private/var/log/*
   sudo rm -rf /private/tmp/*

   These are safe to remove. macOS rebuilds them as needed. Restart after running these commands.
4. Remove Xcode derived data if you are a developer.
   

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

   This can recover 5–30 GB on an active development machine. Xcode rebuilds it on next build.
5. Delete iOS device backups you no longer need.
   iTunes/Finder backups live at ~/Library/Application Support/MobileSync/Backup/. Each backup is typically 3–10 GB. Open Finder, connect your device, and manage backups from there rather than deleting raw folders, so the entries are removed cleanly.
6. Prune Time Machine local snapshots.
   

   tmutil listlocalsnapshots /

   Delete individual snapshots with:

   tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS

   Or delete all at once (only do this if you have a remote Time Machine or another backup):

   tmutil deletelocalsnapshots /

7. Remove apps you no longer use — along with their leftovers.
   Dragging an app to the Trash leaves behind preference files, caches, and Application Support folders that can collectively add up to hundreds of MB per app. A proper uninstaller removes those alongside the app binary.

The One-Click Alternative

If running through each of the above steps manually sounds tedious, Crumb covers most of them in a single pass. Its Clean tab removes system and user caches, logs, and temp files, and its Uninstall tab finds leftover files from apps you have already deleted. If you are unsure whether a folder is safe to remove, Crumb's "Is this safe to delete?" AI explains what the folder contains and flags any real risk before you commit. You can download Crumb and run one free cleanup to see how much it recovers before deciding whether to go further.

That said, Crumb is not magic: nothing replaces deleting a 30 GB iOS backup you genuinely no longer need, or removing an old macOS installer sitting in Applications.

What NOT to Delete

Cleaning is permanent. A few categories that look like good candidates but are not:

• ~/Library/Application Support as a whole — contains saved app state, mail data, browser profiles, and other irreplaceable data. Target only specific subfolders for apps you have already uninstalled.
• /System/Library — never touch this. It is protected by System Integrity Protection (SIP) on modern macOS, but attempting to delete from it can cause serious problems.
• ~/Library/Mail — deleting this removes your local mail database. Back up before touching it.
• Anything in /private/var/db — system databases. Leave these alone.
• Core ML or on-device model files — Tahoe and Sequoia use these for Apple Intelligence features. They will simply re-download if deleted, consuming bandwidth and time right after the upgrade.

After Freeing Space: Confirming You Have Enough

Once you have cleaned up, restart your Mac so APFS can release purgeable space and finalize the freed blocks. Then verify again:

df -h /

If the Avail column shows 25 GB or more, open System Settings → General → Software Update and let the Tahoe installer download. If it still complains about space, check for a partial installer download at /Applications/Install macOS Tahoe.app — the installer sometimes leaves a partial bundle that it counts as used rather than available.

Is Tahoe Worth Upgrading To?

Storage requirements aside, macOS Tahoe brings meaningful improvements to Apple Intelligence, a refreshed design language, and continued security hardening. If your Mac is on the compatibility list and you have cleared the space, the upgrade is straightforward. If your machine is already tight on storage and you would need to do major housekeeping just to reach 20 GB free, that is a signal worth paying attention to: a disk that is perpetually full will cause slow performance, failed backups, and degraded iCloud sync regardless of which macOS version you are running.

Taking an hour to understand and clean your disk before upgrading is time well spent. The steps above give you a clear, methodical path — whether you do them manually in Terminal and Finder, or use a tool like Crumb to handle the repetitive parts. Either way, go in with a backup, know what you are deleting, and you will have a smooth upgrade.