Windows manages virtual memory automatically, and on a modern NVMe SSD that default behavior is usually closer to correct than most forum threads claim. Still, gamers chasing every last frame and every gigabyte of free disk space keep tweaking the pagefile, often making things worse — crashing games, breaking crash dumps, or killing SSD longevity with pointless churn. The goal here is simple: set a pagefile that is stable, large enough for modern games and memory-heavy launchers, positioned on your fastest drive, and then left alone. Prioritize stability over micro-optimization. A pagefile that’s too small causes hard crashes in games like flight simulators or heavily modded titles; a pagefile that’s “optimal” in some YouTube video’s benchmark saves you nothing measurable.
Two things matter most in 2026: letting Windows scale the file instead of handicapping it, and making sure it lives on the drive with the fastest random-write performance — which, on a gaming PC with an NVMe SSD, is almost always your OS drive. Everything else is secondary.
Quick Recommended Settings
| Setting | Recommended value | Why |
|---|---|---|
| Automatically manage paging file size | Checked (default) for most users | Windows expands the file on demand; modern NVMe drives handle the churn easily |
| Manual initial size | Equal to installed RAM (e.g., 32768 MB for 32 GB) | Prevents resizing mid-game; covers full crash dumps |
| Manual maximum size | 1.5× installed RAM (e.g., 49152 MB for 32 GB) | Headroom for memory-heavy games, mods, and browsers without wasting hundreds of GB |
| Drive location | C:\ (the NVMe SSD holding Windows) | Fastest random I/O; required for kernel memory dumps |
| System managed size on secondary drives | None (set to “No paging file”) | Avoids split I/O across drives and orphaned pagefile.sys files |
| Clear pagefile at shutdown | Disabled (0) | Clearing adds 30–60 seconds to shutdown with no security benefit for home PCs |
| Memory compression | Enabled (default) | Reduces paging volume to the SSD, extending drive life |
Setting-by-Setting
Pagefile location: keep it on your NVMe system drive
The single biggest mistake is moving the pagefile to a slower secondary drive “to save SSD wear.” Your NVMe SSD — the one Windows boots from — has vastly higher random 4K write performance than a SATA SSD or HDD, and paging traffic is dominated by small random writes. What causes the myth: old advice from the HDD era when the pagefile competed with the OS on a slow spinning disk. How to check: open Settings > System > About > Advanced system settings, click Performance > Settings > Advanced > Virtual memory > Change, and see which drive is listed as “Managed by system.” What to do: ensure the pagefile sits on the drive with C:\ and your Windows folder. If you have two NVMe drives, the system drive is still the safest choice because kernel crash dumps require a pagefile on the boot volume. What to undo: if you previously moved it to D:\ or an HDD, select that drive, choose No paging file, click Set, then assign the system drive and reboot.
Size: system-managed, or manual at 1×–1.5× RAM
What causes undersizing: guides that say “delete the pagefile, you have 32 GB of RAM.” Windows commits more memory than physical RAM across all processes; a game pulling 20 GB plus a launcher, Discord, browser tabs, and overlay apps can exceed physical capacity, and the result is an “out of memory” crash even with “free” RAM showing in Task Manager. How to check: open Task Manager > Performance > Memory and look at “Committed.” If the committed peak approaches the committed limit during gaming sessions, your pagefile is too small. Also check Reliability Monitor (type reliability in Start) for app crashes around memory pressure. What to do: either leave Automatically manage paging file size for all drives checked, or uncheck it and set Initial size equal to your RAM in MB and Maximum size to 1.5× RAM, then click Set and reboot. The trade-off: the manual fixed-initial approach guarantees the file never has to grow mid-session, at the cost of reserving that disk space permanently — on a 1 TB or 2 TB NVMe, 48 GB is an acceptable reservation. What to undo: re-check “Automatically manage” and reboot.
System-managed vs. fixed size
What causes the debate: Windows starts its managed pagefile small and grows it, which older advice claimed caused stutter. On an NVMe SSD, file growth is nearly instant and rare. The trade-off is purely about predictability: a fixed initial size eliminates the (rare) growth event, while system-managed reclaims space on disk when not needed. If you play large-scale simulators, modded RPGs, or keep 100+ browser tabs open, use the manual 1×–1.5× values above. If disk space is tight, use system-managed.
Crash dump compatibility
What causes broken dump analysis: setting the pagefile below the size needed for a kernel memory dump, or disabling the pagefile entirely. How to check: press Win + R, run sysdm.cpl, go to Advanced > Startup and Recovery > Settings, and look at “Write debugging information.” If it’s set to “Automatic memory dump,” your pagefile on C:\ must be large enough for Windows to create a dump after a blue screen. What to do: keep the pagefile on C:\ at your RAM size or larger, or set the dump type to “Small memory dump (256 KB)” if you insist on a tiny pagefile. What to undo: restore the automatic setting or resize the pagefile back up.
Memory compression
What causes it to be disabled: old “debloat” scripts that run Disable-MMAgent -mc. Compression trades a little CPU for far less data written to the pagefile. How to check: open PowerShell as administrator and run Get-MMAgent; look for MemoryCompression : True. What to do: run Enable-MMAgent -mc if false. What to undo: Disable-MMAgent -mc. Leave it on unless you have a specific, measured reason not to.
By Hardware Tier
Low-end (8–16 GB RAM, budget NVMe, 256–512 GB drive)
Low RAM is exactly when the pagefile matters most. Leave it system-managed on C:\, and don’t delete it to free space — a missing pagefile on an 8 GB machine means crashes in modern open-world games. If disk space is critically short, set a manual initial size of 8192 MB and maximum of 16384 MB. Do not move the pagefile to an HDD to save SSD space; the stutter penalty is severe.
Mid-range (32 GB RAM, 1 TB NVMe)
The sweet spot for manual configuration. Set initial size to 32768 MB and maximum to 49152 MB on C:\. This covers any current game plus streaming or recording software, and the reserved space is a rounding error on a 1 TB drive. Verify your committed peak in Task Manager once after a heavy session; if it never exceeds ~40 GB, you could trim the maximum, but there’s little benefit.
High-end (64–128 GB RAM, PCIe 4.0/5.0 NVMe, 2 TB+)
With this much RAM, paging is rare, but keep the pagefile anyway for crash dumps and applications that require committed memory. Set a fixed initial size equal to RAM (65536 MB for 64 GB) with a maximum of 1.5×. If you run RAM disks, heavy virtualization, or AI workloads alongside gaming, lean toward the top of the range. Avoid the temptation to disable the pagefile — some games and anti-cheat systems misbehave without one.
Common Mistakes
Disabling the pagefile entirely. What causes it: “you have enough RAM” advice. How to check: in the Virtual Memory dialog, see if “No paging file” is selected. What to do: restore a system-managed or manual pagefile and reboot. What to undo: not applicable — this is the fix. Symptoms of the mistake include random app crashes and “your computer is low on memory” popups despite free RAM.
Putting the pagefile on an HDD or SATA drive. What causes it: wear-reduction myths. How to check: the Virtual Memory dialog lists per-drive pagefile sizes; look for a value on a non-NVMe drive. What to do: set that drive to “No paging file,” click Set, and ensure C:\ has the active pagefile. What to undo: if a game regresses after you also moved other caches around, revert drive by drive.
Deleting pagefile.sys manually. What causes it: trying to reclaim disk space by deleting the file in File Explorer — Windows locks it, or worse, third-party tools force-delete it and corrupt memory management. How to check: look for low-disk-space warnings plus instability. What to do: shrink it properly through the Virtual Memory dialog instead, then reboot. What to undo: restore your previous size values.
Splitting the pagefile across every drive. What causes it: guides claiming multiple pagefiles improve performance. Windows writes to pagefiles roughly in drive-priority order; splitting adds complexity and gains nothing on a single fast NVMe. How to check: multiple drives showing nonzero pagefile sizes. What to do: keep one on C:\, set the rest to “No paging file.” What to undo: re-add secondaries only if a specific application’s vendor documentation requires it.
Stale pagefile.sys after downsizing. What causes it: reducing the maximum size without rebooting — the old file lingers until restart. How to check: compare the file size in C:\ (enable hidden system files via View > Show > Hidden items and Folder Options) against your configured values. What to do: reboot. What to undo: nothing needed.
FAQ
Should I disable the pagefile since I have 32 GB of RAM?
No. Windows uses the pagefile for commit accounting, crash dumps, and memory that apps have reserved even if never touched. Disabling it causes out-of-memory crashes in heavy games and can break error reporting. Keep it system-managed or at 1×–1.5× RAM on your NVMe SSD.
Will the pagefile wear out my NVMe SSD?
Negligibly. Modern NVMe drives are rated for hundreds of terabytes written; typical pagefile traffic is a few gigabytes per day. A rough sanity check: open Task Manager > Performance > your SSD and note the “Total bytes written” trend over a month. Memory compression further reduces paging volume. SSD wear is not a reason to relocate or shrink the pagefile.
Can I put the pagefile on a second NVMe drive for better performance?
You can, but gains are essentially unmeasurable in games, and you lose the ability to write full kernel memory dumps (those require a pagefile on the boot volume). Keep it on C:\ unless your C:\ drive is nearly full and you can’t resize partitions.
Does a bigger pagefile improve FPS?
No — a correctly sized pagefile prevents crashes and stutter from memory exhaustion, but it doesn’t create performance. If you see FPS improvements after changing pagefile settings, the previous configuration was causing paging stalls or crashes, and you’ve fixed a problem rather than gained speed. Aim for “never think about it again,” not benchmarks.
