Yes, NVMe SSDs slow down as they fill up, and the drop is steeper than most people expect. A drive that writes at 5,000 MB/s when empty can fall to 800-1,500 MB/s once it is past roughly 85-90% capacity. Understanding why this happens helps you size a gaming drive correctly and avoid the stutter that shows up when a Steam library creeps toward the edge.
Why a Full SSD Gets Slower
Two mechanisms are at play, and they compound each other. The first is the SLC write cache. Modern TLC and QLC drives temporarily treat a slice of their flash as fast single-bit (SLC) storage to absorb bursts. When the drive is nearly full, that cache region shrinks or disappears, so writes land directly on slower native flash.
The second is garbage collection. NAND cannot overwrite data in place; it must erase whole blocks first. On a full drive the controller has fewer free blocks to shuffle data into, so it spends time consolidating before it can accept new writes. That housekeeping steals bandwidth exactly when you least want it.
How Big Is the Slowdown?
| Drive fill level | Typical sequential write | Behavior |
|---|---|---|
| 0-50% | Full rated speed (e.g. 5,000-7,000 MB/s Gen4) | Large SLC cache available |
| 50-75% | 90-100% of rated | Minor cache shrink |
| 75-90% | 40-70% of rated | Cache shrinking fast |
| 90-100% | 10-30% of rated | Direct-to-TLC/QLC, heavy GC |
Read speeds hold up far better than writes, so games that are already installed keep loading quickly. The pain appears when you install or update large titles, copy footage, or run a shader compilation pass on a drive that is nearly stuffed.
How Much Free Space Should You Keep?
A practical rule is to leave 15-20% of an NVMe drive unused. On a 1 TB drive that means treating about 800-850 GB as your working ceiling. This headroom keeps the SLC cache healthy, gives garbage collection room to breathe, and preserves the drive’s rated endurance because the controller wears cells more evenly.
Over-Provisioning as an Alternative
If you would rather not babysit free space, you can deliberately leave a slice unpartitioned. Setting aside 10% as raw, unallocated space gives the controller a permanent scratch area. Many enthusiasts do this on secondary QLC drives that hold write-once media libraries, where the goal is steady behavior rather than peak burst speed.
Does This Affect Gaming Specifically?
For pure gameplay, a full drive rarely tanks frame rates because textures stream via reads. Where you notice it is during 40-120 GB game updates, moving a title between drives, or recording gameplay to the same disk you are playing from. If your capture and game drive are the same nearly-full SSD, expect dropped frames in the recording. Splitting capture onto a second drive solves it cleanly.
FAQ
Will filling my SSD damage it permanently?
No. The slowdown is temporary and reverses the moment you free space and let the drive idle so garbage collection can catch up. Running consistently full does accelerate wear slightly, but a quality TLC drive rated for 600 TBW per terabyte will still outlast most gaming builds.
Does TRIM help with a full drive?
TRIM tells the SSD which blocks are deleted so it can pre-erase them. Windows runs it automatically, and it does help the controller recover speed after you delete files. It cannot create free space you do not have, though, so it is a supplement to keeping headroom, not a replacement.
Bottom Line
NVMe SSDs absolutely slow down when full, mostly on writes, because the SLC cache shrinks and garbage collection has less room to work. Keep 15-20% free, split heavy write tasks like game capture onto a second drive, and let TRIM and idle time do their job. Size your drive so your real library sits comfortably below that 80-85% line and you will never feel the cliff.
