What the Pagefile Actually Does in Windows — and How Big Yours Should Be

What pagefile.sys actually does

When a program allocates memory, it receives a commitment from Windows, and the guarantee behind every commitment is RAM plus the pagefile — together they set the commit limit. Physical RAM holds the hot data; when memory gets tight, the memory manager writes the least-used pages out to pagefile.sys so RAM keeps serving what matters. A big part of the file's job is simply to exist as a guarantee: that is why a machine with "plenty of free RAM" starts throwing out-of-memory errors the moment the pagefile is disabled.

Windows also needs the file for crash analysis: after a blue screen, the memory dump is written there on the next boot. Hibernation is a different file — hiberfil.sys — and has nothing to do with paging. And since Windows 10, memory compression squeezes cold pages in RAM before anything hits the disk, which reduces paging traffic but does not remove the need for the file.

Sizing: the rules that hold up

For 95 percent of machines the right answer is the default: leave the file system-managed. If you do have a measured reason to set it manually, these are the rules that survive contact with reality. The one input that matters is your own peak committed memory, and Task Manager shows it to you for free.

• Leave it system-managed unless you have a measured reason — Windows sizes the file from real usage and crash-dump requirements
• Before typing numbers, watch Task Manager > Performance > Memory > Committed for a few busy days; your peak commit is the only honest input
• If you set it manually, make minimum and maximum the same number, so the file stops growing, shrinking and fragmenting
• Keep at least a small pagefile on C: even if you move the bulk elsewhere, or crash dumps stop working
• A second physical drive is a fine home for it; another partition of the same spinning disk makes paging slower, not faster
• The old 1.5×RAM rule is 1990s folklore — a 64 GB office machine does not need a 96 GB pagefile

The myths that refuse to die

"Disable it and Windows will be forced to use RAM" — no. RAM usage was never limited by the pagefile, and with it gone, programs that ask for more commit than RAM alone can back simply fail to start or crash mid-session. You also lose crash dumps, so the next blue screen leaves you with nothing to analyze.

"Keep it off the SSD or the drive dies" is equally stale: pagefile traffic is a rounding error next to a browser cache, and we break the numbers down in our pagefile SSD wear piece. The last zombie is ClearPageFileAtShutdown, the old "wipe the pagefile at shutdown" tweak — it stretches every shutdown by minutes to protect data that full-disk encryption already covers.

Questions and Answers

Read next