Why Does an SSD Get Slow When It's Full?
Copy files onto a nearly full SSD and it can suddenly feel like a much older drive. It's not your imagination. Here's what's actually happening, and how much free space you need to avoid it.
The Short Answer
Fast, steady writes
Plenty of free space
Full SLC cache absorbs writes
vs
Falls to native speed
Drive nearly full
Cache shrinks, writes stutter
A nearly full SSD loses most of its fast write cache and runs out of free blocks for housekeeping, so writes fall from cache speed to the drive's much slower native NAND speed. On a budget drive that can mean a 5 to 10x drop, and it shows up as stutters and inconsistent copy speeds rather than just a lower number on a benchmark.
Why Free Space Matters to an SSD
Most SSDs write incoming data first to a small, fast pseudo-SLC cache built out of spare NAND cells, then move it to slower long-term storage in the background once things are idle. That cache is carved out of free space. The less free space there is, the smaller the cache, and the sooner a large write burns through it and drops to the NAND's native speed.
Free space also feeds two other jobs the controller runs constantly: TRIM, where the operating system tells the drive which blocks are no longer in use, and garbage collection, where the controller consolidates partially used blocks back into clean, writable ones. Both need slack space to work with. On a nearly full drive there is very little slack, so garbage collection has to compete with your actual writes instead of running ahead of them, which is what produces the stutters and latency spikes rather than just a lower peak speed.
Performance at Different Fill Levels
| Free Space | What Happens |
|---|---|
| Under 50% full | Full SLC cache available, TRIM and garbage collection keep up easily, consistent peak speeds |
| 80%+ full | Cache shrinks noticeably, large writes drop to native NAND speed sooner, garbage collection starts competing with active writes |
| 95%+ full | Cache is minimal or gone, sustained writes run near native NAND speed, latency spikes become common |
QLC Drives Feel It More Than TLC
This hits QLC drives harder than TLC ones. QLC NAND's native write speed is much slower than TLC's, so QLC drives lean more heavily on the SLC cache just to hit their advertised speeds in the first place. When a QLC drive fills up and that cache shrinks, the fallback speed it drops to is lower than a TLC drive's fallback speed, so the slowdown is more noticeable on the drives that are already cheaper and more capacity-oriented.
This isn't the same problem as HDD slowdown, which comes from physical seek time and fragmentation instead. See why a hard drive gets slow when it's full for that side of it.
How Much Free Space to Actually Leave
A common rule of thumb is to keep at least 10 to 20% of an SSD free. On a drive that also runs the operating system, lean toward the higher end of that range, since the OS itself writes to the drive constantly in the background even when you are not actively copying files. On a drive used mainly for storage that sits mostly idle, the lower end is usually fine.
Is It Reversible?
Yes, and no permanent damage is done by running a drive full. Deleting files does not instantly restore performance, though. The drive needs a TRIM pass and some idle time to actually erase the newly freed blocks and rebuild its cache before speeds return to normal. This is separate from wear: how full a drive is has no effect on its long-term lifespan, which comes down to total data written over time instead.
Frequently Asked Questions
Does over-provisioning help?
Yes. A drive with more spare area, either built in or created by partitioning less than the full capacity, keeps a bigger backstop for the cache and garbage collection even when the visible capacity reads as full.
Will deleting files immediately fix it?
Not instantly. Freeing space helps only once the drive has run TRIM and reclaimed those blocks, which normally happens automatically but needs a bit of idle time.
Does this mean the drive is wearing out?
No. Filling a drive up does not wear out NAND on its own, it just leaves the controller less room to work with. Wear comes from total data written over the drive's life, not from how full it is at any given moment.