pagefile.sys grows when committed memory approaches the system limit, so a large paging file is usually a sign of RAM pressure or a memory leak rather than a broken file. Check the commit figure in Task Manager, then set a sensible custom size or move the paging file to a faster drive. Reducing leaks and adding RAM keeps disk activity low over the long term.
This guide walks through the process in clear illustrated steps, from the first preparation to a finished result. Each step has its own picture, so you can compare your progress as you go.
How to use this guide
Work through the steps in order. Method 1 of 3 covers the basics, and the later methods offer alternatives and finishing touches. If you only have a minute, skim the Quick steps box above and come back for the details.
Related guides
- How to Fix high disk usage caused by delivery optimization
- How to Eat more vegetables every day
- How to Beat jet lag
- How to Fix low memory warnings when you have ram free
- Browse all Windows Troubleshooting guides
- All 52runoob guides
Trusted external resources
- Microsoft Learn — Memory allocation errors from slow page file growth
- Microsoft Learn — Low system memory and paging file settings
- Microsoft Support — Free up drive space in Windows
A note on sources
We check each guide against the official resources listed in References at the end of this article. External links open in a new tab; the related guides above stay on this site.
Quick steps
- Check the commit value and commit limit in Task Manager Performance.
- Find which process has the largest commit size.
- Set a custom paging file size with a realistic maximum.
- Move the paging file to a faster SSD if the system drive is slow.
- Close or fix leaking applications and update drivers.
- Add more RAM if commit regularly stays near the limit.
Things you'll need
- A Windows 11 PC with administrator access
- Task Manager and the virtual memory settings dialog
- A second drive if you plan to move the paging file
- An optional compatible memory module if pressure is chronic
Step-by-step
Method 1 of 3: Measure the Paging Load
Step 1: Open Task Manager
Open Task Manager and switch to the Performance tab for memory details.
Step 2: Read commit and limit
Note the commit value and total commit limit shown under memory.
Step 3: Check disk activity
Look at the disk usage figure to see if paging is saturating the drive.
Step 4: Add commit size column
In the Details tab, add the commit size column to sort processes by reserved memory.
Step 5: Find the top consumer
Identify the process with the largest commit size that is driving paging.
Step 6: Watch over time
Leave Task Manager open and see whether commit keeps climbing during normal use.
Step 7: Note the peak commit
Write down the highest commit figure reached during a busy session for later comparison.
Method 2 of 3: Resize or Move the Paging File
Step 8: Open system properties
Search for advanced system settings and open the performance section.
Step 9: Open virtual memory
Choose to change virtual memory from the Advanced tab of Performance Options.
Step 10: Disable automatic management
Clear the option to manage all paging files automatically so you can set a custom size.
Step 11: Set initial and maximum
Enter an initial size and a realistic maximum based on your peak commit figure.
Step 12: Choose the drive
Select a faster or less full drive for the paging file if appropriate.
Step 13: Apply and restart
Confirm the settings and restart so the new paging file size takes effect.
Step 14: Check free space on the target drive
Verify the drive you picked has enough free room to hold the paging file.
Step 15: Let Windows manage the other drive
Keep a small system-managed paging file on the system drive for crash dumps.
Step 16: Reapply and restart
Confirm the changes and restart so the relocated paging file becomes active.
Method 3 of 3: Reduce Pressure Permanently
Step 17: Close heavy applications
Close programs you are not using to lower committed memory immediately.
Step 18: Fix the leaking app
Update or reinstall the application whose commit size keeps growing.
Step 19: Update device drivers
Install optional driver updates through Windows Update for chipset and storage.
Step 20: Free drive space
Run storage cleanup so the drive has room for the paging file to grow.
Step 21: Install more RAM
Add a compatible memory module if commit regularly approaches the limit.
Step 22: Verify the result
Recheck commit and disk usage in Task Manager after the changes.
Tips
- A large pagefile.sys is normal when apps reserve more memory than physical RAM can hold.
- Placing the paging file on an SSD cuts the disk latency caused by paging.
- Watch the commit ratio over a full work session, not just right after boot.
Warnings
- Do not delete pagefile.sys manually because Windows recreates and manages it.
- Setting the paging file too small can cause out-of-memory errors in heavy apps.
- Moving the paging file off the system drive can still leave a small dump file there.
Frequently asked questions
Is it safe to delete pagefile.sys?
No, pagefile.sys is a system file that Windows uses as virtual memory and may recreate automatically. Deleting it by hand does not free meaningful space and can cause memory errors. To change its size or location, use the virtual memory settings in System Properties instead.
Why is my pagefile.sys so large?
The file expands when the commit charge rises, which happens when open programs reserve more memory than your RAM can hold. A memory leak or many heavy tabs can push commit upward until the pagefile reaches its maximum. Reducing those loads or installing more RAM lowers the amount of paging needed.
Should I move the paging file to another drive?
Moving the paging file to a faster SSD can reduce disk stalls if your system drive is a slow hard drive. Keep it on a drive with plenty of free space and good health. If the system drive is already an SSD, moving it rarely helps and can complicate crash dumps.
Will adding RAM stop the paging file from growing?
Adding RAM raises physical memory available, so Windows needs to page less and the file often settles at a smaller size. It does not stop paging entirely, because Windows still uses the pagefile for committed memory and crash dump support. Fixing a leaking app remains important even after a memory upgrade.
References
- Microsoft Learn — Memory allocation errors from slow page file growth. https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/slow-page-file-growth-memory-allocation-errors
- Microsoft Learn — Low system memory and paging file settings. https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/ide/visual-studio-unresponsive-resources-consuming-memory
- Microsoft Support — Free up drive space in Windows. https://support.microsoft.com/en-us/help/4026616/windows-10-disk-cleanup
- wikiHow — How to Fix Windows 11 Paging File Using Too Much Disk (pagefile.sys). https://www.wikihow.com/Free-Up-RAM-on-Your-Computer
Every guide is reviewed against its sources. See our editorial policy.
Reader comments
0 so farFinished this guide? Tell other readers what worked, what didn't, and what you would change.