How Much Free Storage Should a Mac Have?

There's no single number Apple publishes for this. You won't find a support document that says "keep exactly 40GB free" or "never go below 10%" — macOS doesn't enforce a minimum and won't stop you from filling a drive to the last megabyte. That said, "it depends" isn't a very useful answer either, so this article lays out the reasoning that experienced Mac users and IT people actually use to decide how much headroom is worth keeping, and why it changes depending on what you do with your Mac.

Why free space matters at all

Free disk space isn't just empty room for new files — macOS actively uses it in the background, and that's the real reason running low causes problems.

The biggest one is virtual memory. When your Mac's physical RAM is full, macOS swaps some of what's in memory out to disk to make room, then swaps it back in when needed. This happens on every Mac, even ones with a lot of RAM, and it needs free disk space to work. If there isn't enough, the system has nowhere to put that swap data, and things slow down or become unstable.

Time Machine is another one. macOS keeps local snapshots on your startup disk between backups, letting you restore recent file versions even before the next backup to an external drive or network location completes. Those snapshots live in free space, and macOS is designed to delete older ones automatically to reclaim room when a disk gets tight — which is a sign the system is already under pressure, not a sign everything is fine.

Free space is also the scratch area for ordinary operations you don't think about: installing or updating apps and macOS itself, exporting a video, unzipping a large archive, or even just saving a big file. Many of these operations create a temporary copy before finishing the job, which briefly needs more space than the final result. If there isn't room for that temporary copy, the operation can fail outright instead of just running slowly.

A reasonable rule of thumb

Since there's no official figure, here's the reasoning that's commonly used, worth stating honestly as practical guidance rather than an Apple rule: aim to keep somewhere around 10-15% of your total disk free, with a rough floor of 20-30GB free on smaller drives even if that's more than 10-15% of the total.

The logic behind both numbers is the same thing covered above — swap needs room to breathe, Time Machine needs snapshot space it isn't constantly fighting to reclaim, and installers and updates need working room that doesn't eat into what you actually use day to day. The percentage matters more on larger drives (15% of a 2TB SSD is 300GB, plenty of slack), while the flat floor matters more on smaller ones, where 15% of a 256GB drive is under 40GB — not a lot of margin once you account for a large macOS update downloading in the background.

Treat these as a sensible starting point, not a hard line. A Mac sitting at 8% free with light, predictable usage can run fine for months. A Mac at 12% free that's constantly exporting large files or running several memory-hungry apps can feel tight well before that. The number is less important than understanding why it's there.

How the right amount scales with what you do

The honest answer to "how much free space do I need" depends heavily on your workload, because the things that consume headroom — swap and temporary scratch space — scale with what you're actually doing.

If you mostly browse the web, use email, write documents, and watch video, your demands on free space are modest. Swap usage stays low because you're not running many large apps simultaneously, and you're rarely creating huge temporary files. In that case, sitting near the lower end of the 10-15% guidance is usually fine.

If you edit 4K or 8K video, work with large RAW photo libraries, run virtual machines, compile large codebases, or keep several memory-intensive apps open at once, you need meaningfully more headroom. Video editing software in particular often creates large temporary render and cache files during export — on top of needing room for the exported file itself. Virtual machines reserve substantial disk space just to exist, separate from whatever's inside them. For workloads like these, treating 20% or more free as a practical minimum, rather than 10-15%, avoids running into trouble mid-task.

The pattern is simple: the heavier and more disk-intensive your work, the more buffer you want between "used" and "full." There's no universal number that fits a student's MacBook Air and a video editor's Mac Studio equally well.

It's also worth thinking about how your usage might change, not just how it looks today. Someone who mostly browses and emails but occasionally exports a long screen recording, backs up a phone locally, or installs a large game, still needs enough free space to absorb that occasional spike without it becoming an emergency. Keeping a bit more free than your everyday usage strictly requires is cheap insurance against the one week a year your disk usage looks nothing like the other fifty-one.

What happens when you cut it too close

macOS doesn't fail silently when storage gets critically low — it tells you. You'll typically see a system alert warning that your disk is almost full, and "About This Mac" will flag the startup disk in red. That warning is worth taking seriously rather than dismissing, because what follows tends to get progressively more disruptive.

Apps can start refusing to save files once there's no room for them to write, which is one of the more frustrating ways to lose work. Time Machine backups can fail if there isn't enough free space on the destination, or local snapshots get aggressively purged on the source disk, reducing your short-term recovery options. And because swap needs free space to operate, a disk that's nearly full often means macOS is fighting for room to swap memory at the same time everything else is competing for that same sliver of space — a combination that shows up as general sluggishness, apps taking longer to launch, and the whole system feeling heavier than usual, sometimes well before the disk actually hits 100%.

None of this means a nearly-full disk will necessarily crash or corrupt anything — plenty of people run close to the edge without incident. But the margin for error shrinks fast, and the failures tend to show up at inconvenient moments: mid-export, mid-backup, or mid-save, rather than giving advance warning you can act on calmly.

How to find out how much you actually have free

All of this is only useful if you know where you currently stand. The quickest built-in check is the Apple menu → About This Mac → Storage, which shows total capacity, how much is used, and a rough category breakdown. It's a reasonable starting point, but it's coarse — it won't tell you which apps have bloated caches or which specific files are worth reviewing.

We cover the full process, including the less obvious places space tends to hide, in how to check storage on Mac. For a clearer, more detailed picture than the built-in panel gives you, a dedicated Mac storage analyzer breaks down exactly what's using space, category by category, so you're not guessing. And if "System Data" is the mysterious chunk eating your margin, our article on why System Data is so large on Mac explains what actually makes up that catch-all category.

Once you know what's actually using your space, deciding how much headroom to keep becomes a lot more concrete — you're reacting to real numbers for your Mac and your workload, not a generic rule pulled from somewhere else.