Overprovisioning for SATA or NVMe SSDs: what it is and why it matters.
What is SSD overprovisioning (OP)?
Technical definition:
Overprovisioning (OP) is the practice of setting aside a specific portion of an SSD’s total flash storage capacity for the exclusive use of the drive’s controller. This space is not used by the operating system for storing data – it’s either unformatted or completely invisible to the operating system (explained below).
Plain English:
With all the marketing “play” related to 1024 MB vs 1000 MB in one Gigabyte (and gibibytes etc.), you are likely to buy a “2 TB” NVMe SSD that will in fact show just 1.8 TB size when you install it, will have some extra 100 GB that your operating system can’t use or “see”, and you can “manually” format it to only 1.6 TB thus providing extra 200 GB of OP (leaving a total of ~ 300 GB of unallocated storage space, 200 GB of which are visible as unallocated/unformatted).
Yes, crazy and counterintuitive. Read on. 🙂
What it achieves
SSD performance degrades as the drive fills up. Because flash memory can only be written to in pages but must be erased in larger blocks, the controller needs extra room to move data around during maintenance tasks.
Overprovisioning provides a “workspace” for the controller to perform two vital functions (both very important):
- Garbage collection: Reorganizing data to clear out invalid pages and free up entire blocks for new writes.
- Wear leveling: Ensuring that write cycles are distributed evenly across all flash cells to prevent any single cell from wearing out prematurely.
Why that matters
What’s been implied above shall be explicitly explained below. 🙂
1. Sustained performance
Without OP, when a drive is nearly full, the controller must “read-modify-write” every time you save a file. This creates a bottleneck. Overprovisioning ensures there are always empty blocks available, maintaining high write speeds even under heavy workloads.
2. Increased endurance (lifespan)
Related to the above, by giving the controller more room to manage data efficiently, OP reduces write amplification – a phenomenon where the actual amount of data written to the flash is higher than the data sent by the OS. Lower write amplification directly translates to a longer physical lifespan for your drive.
3. Reliability
The reserved space also acts as a pool for “bad block replacement.” If a portion of the flash memory fails, the controller can map that data to a healthy cell in the overprovisioned area, preventing data loss and drive failure.
Should you do it?
Yes, most good-quality SSDs have some OP built in from the factory. For consumer grade it is often around 7% of the drive’s total storage, while enterprise grade drives often come with more than 20% OP from the factory. This factory built-in OP can never be used for storage (you don’t see that even as unformatted/unallocated space).
Still, especially for consumer grade SSDs, it is a good idea to set around 10% more of the (visible) storage space as unformatted – for OP.
Here is an example of my overprovisioning my drives (high-quality Samsung SSDs):
In the picture above, the factory-set OP is completely invisible, while the yellow-marked unallocated (and unformatted) space is visible and that is what I had “manually” set for some extra OP space.
Note that the Disk 0 is a HDD (not an SSD), so it doesn’t need OP.
Conclusion
If you want your SSDs to last as long as possible and work stably and reliably, OP is one of the simplest “set it and forget it” optimizations you can perform. It’s a small trade-off in capacity for a significant gain in long-term reliability and snappiness.
Keep that in mind when considering what size drive to buy and remember: there is no amount of storage space that can’t be filled up with human stupidity! 🙂
And yes, I have had very good experience with Samsung SSDs over the past decade – in case that’s not obvious. 🙂
Sources
- Samsung info on their drive overprovisioning:
https://download.semiconductor.samsung.com/resources/others/Samsung_SSD_845DC_04_Over-provisioning.pdf
Last updated:
Originally published:
