What this tool helps you work out
The pagefile is one part of Windows memory management. It can extend the system commit limit and may also support crash-dump creation, but there is no single manual size that suits every computer.
This calculator shows the traditional custom-sizing rule of 1.5 times installed RAM for the initial value and three times that initial value for the maximum. That rule remains useful when documenting a fixed organisational standard, but it should not be mistaken for Microsoft's current universal recommendation. Microsoft states that pagefile sizing depends on crash-dump requirements and the system's peak commit charge, both of which vary by workload.
Enter system memory
Before you change the pagefile
For most Windows 10 and Windows 11 computers, leave Automatically manage paging file size for all drives enabled unless you have a specific reason to change it. A manually fixed pagefile can be useful for controlled testing, predictable disk allocation or a documented support standard, but setting it too small can cause commit failures and can prevent some memory dumps from being written.
RAM is physical memory. The pagefile does not turn a slow disk into extra RAM. It provides backing for committed memory and gives Windows more room to manage memory pressure.
How this calculator works
The calculator uses a traditional rule:
Initial size = installed RAM × 1.5Maximum size = initial size × 3The result is shown in both megabytes and gigabytes. Windows normally expects a custom pagefile value in megabytes.
This is a planning formula, not a workload measurement. A more defensible manual size is based on the computer's peak committed memory, desired safety margin and crash-dump setting.
Worked example: a computer with 16 GB RAM
Using the traditional rule:
- Initial size: 16 GB × 1.5 = 24 GB
- Maximum size: 24 GB × 3 = 72 GB
Those values are deliberately generous and may reserve far more disk space than the machine needs. On a typical modern PC, system-managed sizing is usually the more sensible starting point.
Common pagefile mistakes
- Disabling the pagefile because plenty of RAM is installed. Some workloads, commit patterns and crash-dump configurations still depend on it.
- Using the same fixed value on every computer. Two machines with identical RAM can have very different peak commit requirements.
- Confusing allocated size with current use. A large pagefile file does not mean Windows is constantly reading and writing all of it.
- Leaving too little free disk space. Windows must be able to create or expand the file and write any required dump.
- Changing several memory settings at once. When troubleshooting, make one controlled change and measure the result.
Frequently asked questions
Should I use a custom pagefile in Windows 11?
Usually not. Start with system-managed sizing. Use a custom value only when you have a measured requirement, a support standard or a specific crash-dump need.
Does a computer with 32 GB or 64 GB RAM still need a pagefile?
It may. Installed RAM alone does not determine the answer. The important factors include peak commit charge, application behaviour and crash-dump settings.
Will putting the pagefile on an SSD damage it?
Normal pagefile activity is not usually a reason to avoid an SSD. Modern SSD endurance is generally adequate for normal client workloads, although unusually write-heavy systems should still be monitored.
Can a small pagefile make Windows faster?
Not by itself. A pagefile that is too small can cause failures. Performance problems should be investigated with Task Manager, Resource Monitor or Performance Monitor rather than guessed from file size.
Why did Windows make the pagefile larger than expected?
A system-managed pagefile can grow when commit demand or crash-dump requirements increase. Check committed memory and the active dump configuration before reducing it.
Related Windows and technology tools
References
These sources support the Windows behaviour or command guidance discussed on this page.
- Microsoft: How to determine the appropriate page file size for 64-bit Windows
- Microsoft: Introduction to page files
- Microsoft: Troubleshoot performance problems in Windows
External documentation can change. Check the linked source before applying a setting to an important system.