How to Adjust the Page File Size for Better Performance on Windows 11

Quick fix: Open Settings → System → About → Advanced system settings → Performance → Settings → Advanced tab → Virtual memory → Change. Untick Automatically manage paging file size for all drives. Pick C: drive. Pick Custom size. Initial: 1.5× RAM (MB); Maximum: 3× RAM. Click Set → OK. Reboot.

The page file (virtual memory) is Windows’s swap space on disk. Default settings work for most users. Custom sizing benefits: heavy multitasking, gaming, low-RAM PCs, or specific apps that need predictable swap. The fix is to set explicit Initial and Maximum values.

What causes this

Windows uses the page file (C:\pagefile.sys) as overflow for RAM. When physical RAM is full, Windows pages inactive data to disk to free RAM for active work. Auto-managed page file is dynamic — Windows resizes based on usage. Custom sizing locks the page file at fixed size, preventing fragmentation and resize overhead.

Common settings: Auto-managed (default; usually fine). Fixed size (Initial = Maximum, locks at one value). Custom range (Initial smaller, Maximum larger; lets Windows grow if needed).

Method 1: Set fixed page file size (recommended for most)

The standard tuning.

1. Press Win + R, type SystemPropertiesPerformance, press Enter.
2. Switch to Advanced tab.
3. Under Virtual memory, click Change.
4. Untick Automatically manage paging file size for all drives.
5. Pick C: drive. Pick Custom size:
   • Initial size (MB): 1.5 × installed RAM. For 16 GB RAM: 24576 MB.
   • Maximum size (MB): 3 × installed RAM. For 16 GB RAM: 49152 MB.
6. For better fragmentation-free performance: set Initial = Maximum (e.g., both 24576). Page file is fixed; no dynamic resize.
7. Click Set. Confirm dialog.
8. For SSDs vs. HDDs: SSDs handle page file fine. HDDs benefit from a smaller page file (avoid disk thrashing). For HDDs: Initial 4 GB, Maximum 8 GB even on 32 GB RAM systems.
9. Click OK. Reboot for changes to apply.

This is the standard performance fix.

Method 2: Move page file to a different drive

For separating system and swap I/O.

1. In Virtual Memory dialog: pick C: drive. Choose No paging file → Set. Removes from C:.
2. Pick another drive (D:, E:, etc.). Choose Custom size — same Initial/Maximum as before.
3. Click Set → OK. Reboot.
4. Trade-off: separate drive reduces C: drive I/O competition. Best when secondary drive is fast SSD.
5. For multi-drive page file: tick System managed size on all drives. Windows spreads page file across drives, balancing load.
6. For NVMe + SATA SSD setup: keep page file on NVMe (faster) for best swap performance.
7. For RAM disk (special use case): create RAM disk via SoftPerfect RAM Disk. Put page file on RAM disk — circular but fast for specific workloads. Most users don’t need this.

This is the right path for multi-drive setups.

Method 3: Disable page file entirely (high-RAM PCs)

For PCs with 32+ GB RAM and no swap need.

1. In Virtual Memory dialog: pick all drives. Choose No paging file → Set.
2. Click OK. Confirm warning. Reboot.
3. Side effects of no page file:
   • Memory dumps from BSOD won’t save (no page file to receive). Affects diagnostic capability.
   • Some apps demand a page file (older databases, certain Visual Studio builds). May fail to launch.
   • Apps requesting more memory than RAM available will be terminated by Windows.
   • On 32+ GB RAM PC running normal workloads: no measurable difference.
4. For best of both: keep small page file (1-2 GB Initial and Maximum) just for crash dumps. Disable page file’s actual swap use is rare anyway on high-RAM systems.
5. To re-enable: set automatic or custom size. Reboot.
6. Caution: most modern Windows app developers assume a page file exists. Disabling can cause subtle issues.

This is the extreme tuning option. Most users should keep at least a minimal page file.

How to verify the fix worked

• Reboot. Check Task Manager → Performance → Memory. Committed graph shows used vs. available virtual memory. Used should be steady.
• WizTree: C:\pagefile.sys shows new size matching your Initial.
• Run Get-CimInstance Win32_PageFileUsage | Format-List Name, AllocatedBaseSize in PowerShell. Shows current page file allocation.

If none of these work

If you see page file errors after tuning: Page file too small: heavy multitasking exhausts page file. Apps see “Out of memory” errors. Increase Initial size. Page file fragmented (HDD): defragment C: drive once after setting fixed size. SSDs: TRIM after resize. For gaming PCs: many games need explicit page file (Star Citizen, Cyberpunk 2077). Recreate with at least 8 GB if you disabled. For PCs reporting page file errors at boot: page file may have moved to a drive that’s no longer present. Re-add via Virtual Memory dialog. For per-app memory limits: some apps have explicit memory caps. Increase via app settings (Chrome flags, Visual Studio settings, etc.) rather than touching page file.

Bottom line: SystemPropertiesPerformance → Advanced → Virtual memory → Change. Set fixed page file size to 1.5–3× RAM. Lock Initial = Maximum to prevent fragmentation. Reboot.