Why a macOS update needs more space than it says

A macOS upgrade needs far more free space than the installer download. The download arrives compressed and unpacks before anything installs, so two copies sit on disk at once. The file system also takes a snapshot first. The installer also counts free space more strictly than Finder does, which is why the error appears on Macs that look like they have room.

Apple has shipped a major macOS release every September for years. MacOS 27 is due this one. The same complaint follows within days, exactly as it did for Tahoe, Sequoia, Sonoma and Ventura before it, from people who checked their storage, saw plenty and got refused anyway.

Major upgrades only. A point release or a security update is a fraction of the size and rarely causes this problem. If the error appeared while installing something like 26.4, the cause is more likely a disk that was already close to full rather than the update itself.

How much free space a macOS update actually needs

Search for the requirement and the answers range from 34GB to 60GB. That looks like sloppiness. It is not.

The figures below are what people measured on macOS Tahoe, which is macOS 26, since nobody has measured the next release yet. Major releases have landed in the same range for several years, so treat them as the shape of the answer rather than a specification.

Each figure in circulation is somebody's true answer for their own Mac. The requirement is not a property of the release. It is a property of your machine, its current system version and how much of your disk is already spoken for.

The working answer is 50GB, with 40GB as the floor. That sits above almost every published figure. It is the one that survives contact with real machines.

There is a second reason nobody can settle it. Apple used to publish a number and stopped. Big Sur was the last release with a clear one, asking for 35.5GB of available storage or up to 44.5GB coming from an older system. Nothing since has carried a comparable figure, so every page you find is estimating from measurements rather than quoting a specification.

One tester's numbers are worth more than any published minimum. An upgrade attempted with 28GB free failed partway through. The same machine, cleared further, completed without trouble. That gap between failing and working sits well above every official figure.

Why the macOS installer sees less free space than Finder

This is the part that makes the error feel unfair. You checked, you had room and the installer disagreed anyway.

Finder is optimistic. It counts space it could reclaim, snapshots it could release and caches it could drop. It reports the total as available, because from your point of view you could write that much. The installer is pessimistic. It counts what is free at this moment, because it cannot rely on space the system has not yet let go of.

What Finder tells you

Roughly 38GB

• Counts space it could reclaim
• Counts snapshots it could release
• Counts caches it could drop
• Answers what you could write

What the installer sees

23.86GB

• Counts only what is free now
• Cannot rely on unreleased space
• Cannot wait for macOS to catch up
• Answers what it can use today

So the number to check is not the one in Finder. For the figure the installer will use, look in Disk Utility. It reports what is genuinely there rather than what you could free. The three tools count differently on purpose. An upgrade is the moment that difference bites.

Where the space goes during a macOS install

1. Download 13GB to 17GB The compressed installer arrives and sits on your disk.
2. Expand Another 17GB to 25GB It decompresses. The packed and unpacked copies both exist for a while.
3. Install Plus a snapshot The file system records a point to fall back to, which holds the old blocks.
4. After Around 10GB The new system needs working room. A disk that ends full behaves badly.

Read more: What System Data on a Mac is.

The snapshot macOS takes before the install

Before a major upgrade APFS records a snapshot, which is what gives a failed install something to fall back to. That is a good thing. It costs space.

Read more: Why deleting files does not free space on a Mac.

A snapshot does not copy your disk. It pins the blocks in use at that moment, so anything the installer replaces stays put while the snapshot exists. During an upgrade, when the installer rewrites large parts of the system, that adds up.

It is also why free space can look worse immediately after an upgrade than before it. The snapshot is still there. macOS releases it in its own time, normally within a few days.

What happens when a macOS install runs out of space midway

Running short before the install starts is harmless. Software Update refuses in System Settings and nothing has changed, so you can clear space and try again.

Running short partway through is different. It is the outcome worth avoiding. Reports follow a pattern. The install reaches the end and fails. The Mac then restarts into a screen asking which startup disk to use and rebooting repeats it.

This is recoverable and it is not a data loss event. The system volume is in a half written state the Mac cannot start from. Your files are on a separate volume and are untouched. Booting into macOS Recovery and reinstalling repairs the system side without erasing anything.

What changes the number for your Mac

Fifty gigabytes is the planning figure. Two things move it. Both move it upwards.

• Upgrading from two or more versions back replaces more of the system, so add headroom rather than trimming it.
• A drive under 256GB makes 50GB a fifth of everything you have. On those machines the upgrade is a planning exercise rather than a click.

Check the figure in Disk Utility rather than Finder, for the reason above. And check it after a restart, since a restart releases space that running applications were holding open.

If you cannot free enough space at all

On a 128GB or 256GB Mac that is genuinely full of things you need, clearing 50GB is not a tidying exercise. Two routes exist and neither is a cleanup list.

• Install from a bootable installer on an external drive. Put the installer on an SSD or stick of 128GB or more, boot from it and install from there. On Apple silicon, hold the power button at startup and pick the external disk. On Intel, hold the Option key. This is a route for confident users and it needs a backup first.
• Back up, erase, clean install, restore. Take a Time Machine backup, erase the Mac, run a clean install on the empty disk and restore your files afterwards. Slow and disruptive. It always works, because the installer starts with the whole disk to itself.

Both are worth reaching for only after the ordinary options are gone. Both need a verified backup before you begin, not one you assume is fine.

If the macOS update is already stuck

Take these in sequence. The last step is the one people reach for first. It is the one to arrive at rather than start with.

1. Wait longer than feels reasonable. An install that looks frozen is nearly always still working. An hour on a progress bar is not unusual on an older Mac.
2. If the Mac is genuinely unresponsive, force a restart. Hold the power button for about ten seconds, wait, then press it again.
3. If it boots normally, stop and clear space properly. Get well clear of the number that failed rather than just above it.
4. If it asks which startup disk to use, boot into macOS Recovery instead. Hold the power button on Apple silicon or Command and R on an Intel Mac.
5. Reinstall macOS from Recovery. This repairs the system without touching your files.
6. Only then try the upgrade again. With more room than you think you need.

One thing not to do is delete files while the installer is running. Space released mid install is not visible to it, so the effort achieves nothing and the interruption adds risk. Cancel properly, clear the space, restart and begin again.

How to avoid the problem entirely

Nothing obliges you to upgrade on release day. Waiting three or four weeks costs nothing, lets the first point release land and gives you time to clear space without a progress bar waiting on you.

If you do upgrade early, do the storage work the week before rather than the morning of. The failure mode people write about afterwards is almost always someone who started with just enough.