Your Windows 11 default hibernation file is quietly eating 32GB of SSD write cycles, and here is the one-command fix

Published Sep 6, 2026, 8:00 AM EDT Jasmine is Software and PC Hardware Author at XDA with years of tech reporting experience ranging from AI chatbots right down to gaming hardware, she's covered just about everything. Whether it's breaking news about the latest AMD NPUs or creating video tutorials on social media platforms, Jasmine has contributed to the world of AI and tech in a variety of ways including interviewing the CEO of Razer, AMD's Director of Product Marketing and the VP of Lenovo. Passionate about gaming and PC technology, she has built countless computers, keyboards and other peripherals - knowing them inside and out. One issue PC builders might face is installing Windows 11 on a fresh 1TB or 2TB NVMe SSD. You install a handful of essential apps, Open TreeSize or WizTree, and suddenly you discover a massive locked system file called hiberfil.sys quietly devouring 16GB to 32GB of root C: partition space. This isn't just wasted capacity. It can also lead to wear and tear on your SSD as every time Windows initiates fast startup, hybrid sleep, or full system hibernation, it dumps the entire contents of your active system RAM directly into that file on your flash storage. This is a feature that was designed decades ago for slow mechanical spinning hard drives and low-power laptops and is now enabled by default on high-end desktop gaming rigs and workstation PCs equipped with 32GB, 64GB, or 128GB of high-speed RAM and blazing Gen 4 or Gen 5 NVMe SSDs. The Windows 11 default hibernation file is an outdated legacy mechanism that consumes dozens of gigabytes of prime NVMe real estate and silently wastes TBs of written endurance on your SSD. By executing a single administrative command in your terminal, you can either shrink hiberfil.sys by 60% or kill it entirely in order to reclaim your storage and protect your drive's lifespan in the long term. What is the point of the hiberfil.sys file? It's not needed for most modern devices What does hiberfil.sys? actually do? Under the hood, it's a clear RAM-to-disk dumping ground. This is because when hibernation is activated, the Windows kernel compresses and dumps active volatile system memory into non-volatile storage, otherwise known as hiberfil.sys. This lets the PC reach a full 0W power state and resume later. By default, Windows reserves a hibernation file size equal to 40% to 100% of your total installed RAM. If your workstation runs 64GB of RAM, then hiberfil.sys can reserve a staggering 25GB to 50GB of static SSD storage. This is also the case with fast startup. Even if you're not using the hibernate feature directly, fast startup also utilizes the hibernation boot feature. Even if you never click hibernate in the Start menu, Windows 11 uses fast startup by default. This means when you click the standard shutdown option, Windows doesn't actually perform a clean cold shutdown. Instead, it logs off your user session, hibernates the core Windows kernel and drives to hiberfil.sys, and then powers down. As a result, every single standard PC shutdown triggers a multi-gigabyte write cycle to your SSD's NAND flash blocks, which can cause wear and tear over time. This can cause long-term damage to your SSD Fast startup doesn't make as much of a difference as you may assume The wear and tear caused here isn't something to brush off. It has a serious impact on flash memory and can affect your SSD's long-term health. This is because SSD NAND flash cells have finite write endurance rated in TBW (terabytes written). By dumping 10GB to 30GB of kernel and session state to the drive one to two times a day, you're adding up to 5TB to 10TB+ of unnecessary host writes over a couple of years. This leads to SSD performance degradation on full drives. SSDs rely on free space for dynamic SLC caching, level algorithms, and garbage collection. Choking a 500GB or 1TB boot drive by locking away 32GB for an unused hibernation file restricts the drive's ability to maintain peak burst writes and shortens the lifespan of any ND blocks. Realistically, when it comes to modern NVMe drives, using fast startup makes very little difference. On a modern PCIe 4.0 or 5.0 NVMe drive that boots a clean, cold Windows session, you will be able to boot this in under 10 seconds. Fast startup will likely give you a couple of seconds of a speed advantage, but this is virtually indistinguishable in day-to-day use. Run a single command to fix the problem You have two options for the command Luckily, there is a way to fix this, and all it takes is one singular command. Before you start, note that you can run this command in two ways. The first is a complete desktop nuclear option that lets you reclaim 100% of the space and stop all writes. The second is a bit more of a compromise, which allows you to keep Fast Startup and cut the file size of hiberfil.sys by 60%. If you are opting for the nuclear option, which is best for desktops, gaming PCs, and workstation rigs that don't need hibernation and prefer a true clean shutdown, then the first thing you want to do is right-click the Start Menu and then select Terminal or PowerShell. Make sure, whichever one you click, you run it as Admin so you have full permissions. Next, run the command: powercfg.exe /hibernate off When running this command, the hyperfil.sys file is instantly deleted, freeing 16GB to 32GB of disk space immediately, with no reboot required. It can free even more disk space if your device has more RAM. If you want to instead run the compromised version, which is best for mobile laptops where you want to keep fast startup kernel caching but want to strip the multi-gigabyte user session hibernation payload, then again open either PowerShell or Terminal as an administrator and run: powercfg /type reduced Instead of completely eradicating hiberfil.sys, this shrinks it to its minimum kernel-only footprint, about 3 GB to 6 GB (depending on how much RAM you have), while still retaining fast startup. Lastly, you can verify it works by using a file explorer with "Show protected operating system files" checked, or by using the powercfg /a command to inspect supported sleep states. You don't need a vintage sleep state Your PC is likely fast enough without it Modern desktop PCs equipped with ultra-fast NVMe storage don't need mid-2000s sleep-state band-aids that can burn through your SSD's write endurance and hog tens of GB of disk space. It's super simple to take back your NVMe real estate by opening an administrative terminal window right now and firing off a single-line command. That way, you reclaim 30GB of storage (or sometimes more based on your RAM) in under 30 seconds.