What Is SSD Over-Provisioning and Free Space Headroom

The reserve the controller cannot live without

An SSD cannot overwrite NAND in place: a block must be erased before it is written, and erase blocks are large — often megabytes — while host writes arrive in 4 KB pages. The controller therefore constantly shuffles valid data out of partially-filled blocks to reclaim them, and that shuffle needs free blocks to write into. That working reserve is the spare area: physical NAND that exists in the drive but is not exposed as user capacity — a drive sold as 240 GB typically contains 256 GB of raw flash.

On top sits a second, dynamic layer: the blocks TRIM tells the controller no longer hold live data. When you delete a file, Windows sends a TRIM, and the controller is free to erase and recycle those blocks in the background ahead of need. The practical consequence: a half-empty drive with working TRIM behaves like a heavily over-provisioned one, because the controller sees all those free blocks as its own playground.

• Sustained large writes: copying hundreds of gigabytes in one go, where garbage collection cannot keep up
• A drive kept above roughly 90 percent full, where the spare area shrinks to near nothing
• Environments without TRIM: old operating systems, some USB bridges and RAID controllers
• Write-heavy workloads: databases, video scratch disks, continuous logging
• A drive late in its wear life, as retired blocks quietly consume the reserve

The manual ritual is mostly obsolete — the headroom is not

The old advice — partition only 90 percent of the drive and leave the rest unallocated — dates from early SSDs without working TRIM, where a hidden reserve was the only way to guarantee the controller free blocks. On any modern drive with TRIM the separate unallocated slice adds little: the controller already recycles every block the file system has released. The ritual persists because it once worked and because partition tools make it easy, not because the physics still demands it.

What has not changed is the cost of a drive filled to the brim. Past roughly 90 percent occupancy the controller's options narrow: every write triggers extra shuffling, write amplification climbs, and sustained write speed sags — that is the real-world version of exhausting the spare area, and it happens on a perfectly healthy drive. The practical rule is simpler than any partition math: keep about 10 to 15 percent of an SSD free, more on disks that absorb heavy writes, and let the controller handle the rest. Monitoring tools reading SMART attributes will show rising wear-leveling counts long before this becomes a problem worth acting on.

Questions and Answers

Read next