Windows 11's Hibernation File Can Eat 32GB of SSD Space, Here's How to Reclaim It

The hidden file eating your disk space

If you build a PC and install Windows 11 on a fresh NVMe SSD, then open a tool like WizTree or TreeSize, you may spot a large, locked system file called hiberfil.sys sitting on your C: drive. As XDA Developers' Jasmine Mannan detailed, this file can reserve anywhere from 16GB to 32GB, and more on machines with lots of RAM. By default Windows sizes it at roughly 40% of your installed RAM, so a 64GB workstation can see hiberfil.sys claim 25GB or more of static storage.

What hiberfil.sys actually does

The file is where Windows dumps the contents of RAM when the PC hibernates, letting it reach a full zero-watt power state and resume later exactly where you left off. Crucially, it is also used by Fast Startup, the feature on by default that makes Windows boot quickly. When you click Shut Down, Windows does not fully cold-shut down; it logs you off and hibernates the Windows kernel and drivers into hiberfil.sys, then powers off. So even if you never click Hibernate, the file is still in use.

The SSD-wear claim, and the pushback

XDA's article frames this as a threat to your SSD's lifespan, arguing that repeatedly dumping gigabytes to the drive burns through its finite write endurance (measured in terabytes written, or TBW). It is worth being straight with you: this framing was strongly disputed in the article's own comments by readers who work with this hardware. Several pointed out that on a 1TB drive, 32GB is about 3% of capacity, that modern SSD endurance runs into hundreds of terabytes, and shared real-world data, one reporting a laptop hibernated daily for five years that used only about half its rated endurance, another still at 99% drive health after years of hibernating two to three times a day. One commenter also flagged a genuine error: Fast Startup only writes the kernel and drivers, not your full user session, so the piece overstated how much gets written on a normal shutdown.

The real reason to do it: space, not fear

So the honest takeaway is this: reclaiming that 16-32GB is a legitimately useful move if you are tight on boot-drive space or simply want a true clean shutdown, and SSDs also benefit from having free space for caching and garbage collection. But if your only worry is 'am I destroying my SSD,' the evidence suggests that for typical use, the impact is small and your drive will very likely outlast its usefulness regardless. Treat this as a storage-reclaiming tip, not an emergency.

The one-command fix (two options)

Either way, the fix is quick. Right-click the Start menu, open Terminal or PowerShell as Administrator, and choose one: To remove hiberfil.sys entirely and reclaim all the space (best for desktops that do not need hibernation), run powercfg.exe /hibernate off. The file is deleted immediately, no reboot required, but note you then lose both hibernate and Fast Startup. To keep Fast Startup but shrink the file to a kernel-only footprint of roughly 3-6GB, run powercfg /h /type reduced instead. You can confirm your sleep states afterward with powercfg /a.

Do you even need it?

For a modern desktop with fast NVMe storage, a clean cold boot already completes in well under ten seconds, so Fast Startup often saves only a second or two, an advantage most people will never notice. That makes disabling it a reasonable choice on desktops. On a laptop, though, full hibernation is genuinely useful: it preserves your entire working session through a battery-dead or power-loss situation, which is exactly why many people keep it on. As always, match the choice to how you actually use the machine rather than optimizing for a number.

Related on Skillo

See also: Windows 11 version 24H2 feature update, Will RAM prices go down in 2027?.

Sources

• Your Windows 11 default hibernation file is quietly eating 32GB of SSD write cycles (Jasmine Mannan, XDA Developers, 6 Sep 2026)

Published date reflects the original event date (2026-09-24). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.