Summary
Windows is notorious for eating away space on your SSD that you could use for more useful things like your photo backups or your favorite game. A lot of that space holds Windows itself, but a surprisingly big amount belongs to recovery and reliability features designed to save your PC when something goes wrong. These safety nets are nice to have, but if you’re cramped for space, some of them can be sacrificed. But before you go around deleting anything, it helps to understand what each one protects, how much control Windows gives you, and what you sacrifice by reclaiming its space. Hiberfil.sys is a gigabyte hoarder with a nap schedule Up to 40 percent of your RAM, parked on an SSD for a nap you never take The hiberfil.sys file lives in the root directory of your system drive and stores data needed for hibernation. Instead of shutting down completely, Windows writes the system’s memory state to the SSD so it can restore your open applications and documents later. The same file also enables Fast Startup and hybrid sleep, so it may exist even if you’ve never hibernated your PC. Windows supports full and reduced hibernation files too, according to Microsoft. A full file supports hibernation, hybrid sleep, and Fast Startup while defaulting to 40 percent of installed physical memory. A reduced file only supports Fast Startup and defaults to 20 percent instead. So if you’ve got a PC with 32 GB RAM, several gigabytes go to this feature and you might barely notice it, but on 16 GB or lower memory PCs, this becomes a problem rather quickly. Whether or not this file earns its space depends on the machine. Hibernation can be useful on laptops because it preserves your session without continuously drawing battery power. On an SSD-equipped desktop that already boots quickly, it is much less desirable. Running powercfg /hibernate off from an elevated terminal will remove the file, but also disable hibernation and Fast Startup. Disabling these features shouldn’t be much of an issue if you’ve got a relatively fast SSD, but if you’d rather keep Fast Startup enabled, you can run powercfg /hibernate /type reduced instead. Pagefile.sys is the one file you should leave alone Plenty of RAM doesn’t make it a freeloader, just a crash dump insurer The page file is frequently mistaken for emergency memory a PC uses when the physical RAM is full. So if you’ve got plenty of RAM, you might think you don’t need the page file at all. In reality, Microsoft says pagefile.sys increases Windows’ commit limit, lets the system move infrequently accessed modified memory pages out of RAM, and supports crash dumps. If committed memory reaches the combined limit of physical RAM and page-file capacity, programs can malfunction, freeze, or crash entirely. What that means is deleting your pagefile.sys file to save space isn’t a great idea, even if you’ve got 32 or 64GB of RAM. Some applications expect commit capacity beyond physical memory, while Windows itself may use the paging file to capture diagnostic information after a system crash. The sensible choice here is to leave your page file system-managed. Windows can adjust its size according to memory availability and disk capacity rather than permanently allocating an oversized block of storage you never see. This is one safety net that earns its place because the alternative can turn your heavy multi-tasking sessions into a straight up nightmare. System Restore needs a leash, not a funeral Cap the storage, keep the undo button Microsoft says System Restore creates restore points containing system files, installed applications, registry data, and important settings. If a driver, update, or configuration change breaks Windows, you get to roll back the system without deleting personal documents. Restore points may be created automatically around system events or manually before a risky change. The problem is that having multiple restore points can quickly take up a substantial amount of storage on your SSD. Windows lets you control this via its System Protection settings, where a maximum usage slider caps the amount of storage available to all restore points you have. Once the allocation fills up, older points are removed to make room for newer ones. Disabling System Restore entirely does save space, but removes one of Windows’ simplest and most reliable recovery options. Keeping it enabled with a modest storage cap is the better option, especially if you frequently experiment with your PC. Point-in-time restore is System Restore’s overachieving sibling Snapshots for 72 hours, 2 percent of your drive, and a lot of overlap Point-in-time restore is a newer Windows 11 feature that goes beyond regular System Restore. It can return your entire PC — including Windows, applications, settings, and personal files — to a recently taken automatic snapshot. According to Microsoft, Windows usually creates these every 24 hours, stores them up to 72 hours, and applies a maximum usage limit of 2 percent of the drive. This makes the feature useful in case a bad update, corrupted configuration, or accidental file change breaks something, but it also creates an overlap. System Restore protects system components over a longer period, while point-in-time captures are more complete but shorter-lived state. Microsoft says point-in-time restore also requires Windows 11 version 24H2 or later, so it won’t appear on every PC. As with System Restore, if you experiment with your PC, especially the Windows-breaking kind, it deserves space on your machine. The snapshots remain on the same PC and should not replace file history, cloud synchronization, or an external backup. If storage is tight and you already maintain reliable backups, this is the easier restore feature to reconsider. Reserved storage isn’t an undeletable file, just a pessimistic one Windows is saving room so updates don’t die mid-install You might look at reserved storage on your PC and think of it as a giant undeletable file, but that’s not the case. Microsoft says Windows estimates space for updates, caches, temporary files, and servicing operations so an update is less likely to fail because a drive ran out of storage mid-process. When there’s a space shortage on your drive, Windows can clear reserved storage and make it available to other processes. It is generally enabled on computers that come with Windows 11 out of the box or have clean Windows 11 installations. Disabling it may make the free space on your drive look bigger, but it’s just postponing the problem to the next major update. Unless you’re really cramped for space, reserved storage is worth keeping around. Cleanup works best when you pick your battles Remove the safety nets you can replace, keep the ones you can’t Windows isn’t wasting space for the sake of it, but its default settings do assume every PC needs fallback. That may or may not be true in your case, meaning you might just benefit from removing some of those safety nets. The best cleanup is therefore selective. A desktop with lots of RAM may not benefit from full hibernation, while a small laptop SSD will need a smaller system restore storage cap. The trick is to only remove protections you can replace with something better.