Last Updated: September 11, 2026
To add more virtual memory to a laptop, open Advanced System Settings, go to Performance → Settings → Advanced → Virtual Memory → Change, and review the paging-file setting. For most Windows 10 and Windows 11 laptops, the safest choice is to leave Automatically manage paging file size for all drives enabled. Use a custom size only when an application, troubleshooting procedure, or crash-dump requirement gives you a specific reason.
Quick Answer
Press Win + R, type sysdm.cpl, and press Enter. Open Advanced → Performance Settings → Advanced → Virtual Memory → Change. Keep automatic management enabled unless you have a specific reason to use a custom paging-file size. A larger page file can prevent out-of-memory failures, but it does not turn storage into RAM or guarantee a faster laptop.
Key Takeaways
- Virtual memory uses Windows paging files to support committed memory; it is not the same as physical RAM or GPU VRAM.
- System-managed paging is the best default for most laptops.
- There is no universal “1.5× RAM” or “3× RAM” custom-size rule that fits every PC.
- Check Task Manager’s Committed memory reading before assuming the page file is your performance problem.
- Custom sizing is most defensible when an application, technician, memory-allocation problem, or crash-dump requirement calls for it.
- Restart if Windows requests it, then verify that the intended setting is active.
At a Glance
| Time Required | 5 to 10 minutes, plus a restart if Windows requests one |
| Difficulty | Easy to moderate |
| Tools Needed | Windows System Properties, Performance Options, Task Manager, or the Run dialog |
| Best Default | Automatically manage paging file size for all drives |
| Cost | Free |
What Does Virtual Memory Do on a Laptop?
Windows uses a page file, also called a paging file, to support committed memory and to move some infrequently accessed modified memory pages out of physical RAM. This frees physical memory for data that needs faster access. Because the page file lives on storage, accessing it is normally slower than accessing RAM.
The page file also extends the system’s commit limit. Microsoft explains that the commit limit is based on physical memory plus page-file capacity. If committed memory reaches that limit, Windows or individual applications may be unable to allocate more memory, which can cause freezes, crashes, or out-of-memory errors.
That is why increasing virtual memory can improve stability when memory capacity is genuinely the problem. It does not make a low-RAM laptop perform like a machine with more physical RAM. If your laptop constantly pages data to storage, adding RAM where supported, closing unnecessary applications, or disabling unnecessary background apps may provide a more meaningful improvement.
Note: Virtual memory is different from VRAM. Virtual memory supports system committed memory, while VRAM is graphics memory used by the GPU.
Should You Increase Virtual Memory or Leave It Automatic?
For most laptops, leave Windows on automatic paging-file management. Microsoft states that page-file sizing depends on peak committed-memory usage and crash-dump requirements, which differ from one system to another. A fixed multiplier based only on installed RAM cannot account for those differences.
| Your Situation | Best Starting Action |
| Laptop is stable and you have no low-memory errors | Leave Automatically manage paging file size for all drives enabled. |
| You see out-of-memory errors or committed memory approaches its limit | Confirm automatic management is enabled, check free disk space, and identify the apps consuming memory before choosing a custom size. |
| An application or support technician requires a specific page-file size | Use the documented custom value and keep enough free storage available. |
| You need a specific system crash dump | Size the page file or dedicated dump file for the selected dump type. A complete memory dump requires at least RAM + 257 MB. |
| Your SSD is nearly full | Free storage before forcing a larger custom maximum. Do not use page-file changes as a substitute for adequate free space. |
How to Add More Virtual Memory to a Laptop
The quickest route on current Windows systems is the Run dialog:
- Press Win + R.
- Type sysdm.cpl and press Enter.
- Open the Advanced tab in System Properties.
- Under Performance, click Settings.
- Open the Advanced tab in Performance Options.
- Under Virtual memory, click Change.
You can also search Windows for View advanced system settings or use Control Panel → System and Security → System → Advanced system settings. The exact visual path can vary slightly between Windows builds, but the Virtual Memory dialog remains under Performance Options.
Before changing anything, note whether Automatically manage paging file size for all drives is currently selected. Microsoft’s page-file guidance explains that system-managed files grow or shrink according to factors including physical RAM, committed-memory demand, and crash-dump requirements. Microsoft Learn therefore provides workload-based guidance rather than one universal custom size.
When Should You Disable Automatic Management of Virtual Memory?
Clear Automatically manage paging file size for all drives only when you have a defined reason to control the page file manually. Examples include an application requirement, a technician-directed troubleshooting procedure, a specific crash-dump configuration, or a documented memory-allocation problem.
To switch to manual control:
- Open System Properties with Win + R → sysdm.cpl.
- Choose Advanced → Performance → Settings.
- Open Advanced → Virtual Memory → Change.
- Clear Automatically manage paging file size for all drives.
- Select the drive you want to configure.
- Choose Custom size only if you have an appropriate initial and maximum value.
Do not disable automatic paging-file management simply because a generic guide tells you to use a multiple of your RAM. Manual sizing should solve a specific requirement or diagnosed problem.
After entering custom values, click Set, then OK. Windows may request a restart before the new configuration is fully active.
Warning: Do not set the paging file unnecessarily low or disable it without understanding the consequences. An inadequate commit limit can contribute to failed memory allocations, freezes, application crashes, and problems creating some crash dumps.
[Amazon Products Picked for You]
NONSTOP SPEED: Race through projects with our fastest SSD for creators; Load, edit and transfer with sustained read and write speeds of up to 2,000MB/s1; The T9 Portable SSD performs at high speeds even during longer processes
Customize your drive’s RGB lighting with the downloadable WD_BLACK Dashboard (Windows only) to show off your style and make every play personal.
✅ On-the-Go Convenience: Slipdrive ssd external hard drive sleeve allows for effortless storage right on your laptop or tablet, ensuring that your precious data is always within reach. It eliminates the risk of misplacing your SSD and the hassles of awkwardly dangling drives during use or transport.
How Much Virtual Memory Should You Set?
There is no single page-file size that is correct for every laptop. Microsoft says sizing depends primarily on the required system crash dump and the system’s peak commit charge. Two laptops with the same amount of RAM can therefore need different paging-file capacities.
Windows normally handles this automatically. Microsoft documents that a system-managed page file can grow when the system commit charge rises above 90% of the commit limit. Its documented system-managed maximum is generally 3× physical RAM or 4 GB, whichever is larger, subject to volume-size, free-space, and crash-dump considerations.
If you require a Complete memory dump, Microsoft specifies that the page file or dedicated dump file must be at least RAM + 257 MB. That number is a crash-dump requirement; it is not a universal recommendation for ordinary laptop performance.
Recommended Virtual Memory Ranges
Instead of choosing a random range, start with the setting that matches your situation:
| Best choice for most users | Automatically managed / system-managed paging |
| Use a custom size when | A documented app requirement, diagnosed memory-allocation issue, support procedure, or crash-dump requirement calls for it |
| Use Task Manager when | You want to see whether committed memory repeatedly approaches the current commit limit during your real workload |
| Avoid | Very small page files, disabling paging without a defined reason, oversized values on low-storage drives, or copying arbitrary settings from another PC |
To check committed memory, open Task Manager → Performance → Memory and find the Committed value. It appears as a current amount and a limit. If the current value repeatedly approaches the limit during the workload that causes errors, memory capacity deserves investigation. If the value stays comfortably below the limit, increasing the paging file may not address the real bottleneck.
Understand GB, GiB, MB, and MiB Before Entering Values
The Virtual Memory dialog labels custom values in MB, but storage and memory documentation sometimes mixes decimal and binary terminology. These units are not technically identical.
- 1 GB = 1,000 MB under the SI definition.
- 1 GiB = 1,024 MiB under the IEC binary-prefix definition.
- For example, 48 GB = 48,000 MB, while 48 GiB = 49,152 MiB.
NIST documents the distinction between decimal prefixes such as GB/MB and binary prefixes such as GiB/MiB. If an application or administrator gives you a required paging-file value, use the exact unit and number specified rather than assuming that every “GB” value should be multiplied by 1024.
Microsoft does not require a fixed RAM multiplier for normal page-file sizing. If you do not have a documented custom requirement, leave Windows in control.
Pro Tip: Before changing the paging file manually, write down your current configuration. If stability gets worse, you can restore automatic management quickly.
How to Enter a Custom Paging-File Size
If you have a verified reason to use custom values, enter them conservatively instead of trying to maximize the page file.
- Open the Virtual Memory dialog.
- Clear Automatically manage paging file size for all drives.
- Select the drive you intend to configure.
- Choose Custom size.
- Enter the required Initial size (MB) and Maximum size (MB).
- Click Set.
- Click OK through the remaining dialogs.
- Restart the laptop if Windows requests it.
Keep adequate free storage on the selected drive. If you have no application requirement, crash-dump requirement, or diagnosed memory problem that calls for custom values, return to automatic management instead of guessing.
How to Apply the New Virtual Memory Settings
After selecting a custom configuration, click Set before closing the Virtual Memory dialog. Then click OK through the remaining windows. If Windows displays a restart prompt, restart the laptop before evaluating the new configuration.
If you are returning to Windows-managed paging, select Automatically manage paging file size for all drives, apply the setting, and restart if requested.
Reboot for Changes
Some paging-file changes require a restart because Windows must change the size, location, or management state of the paging file outside the current session. Follow the restart prompt when one appears rather than assuming every change is active immediately.
- Save open work before restarting.
- Reopen your normal workload after startup.
- Do not judge the result from one brief test; reproduce the workload that originally caused the problem.
Verify the New Settings
After the restart, return to System Properties → Advanced → Performance → Settings → Advanced → Virtual Memory → Change. Confirm that automatic management is enabled or that the intended custom values are displayed.
Then open Task Manager → Performance → Memory and review the Committed reading during your normal workload. The goal is not to make paging-file usage disappear; the useful question is whether the laptop remains stable and whether committed memory has enough headroom below the commit limit.
When Is a Restart Required?
Restart your laptop when Windows prompts you after changing paging-file settings. Use Start → Power → Restart rather than shutting down applications abruptly.
A restart provides a clean point from which to verify the active paging-file configuration. It can also clear temporary application state, so compare performance using the same apps and workload you were running before the change.
How Do You Know If the Virtual Memory Change Helped?
Do not judge a page-file change by a single “faster” or “slower” impression. Compare the symptoms that led you to change it: out-of-memory warnings, application crashes, committed-memory pressure, and excessive disk activity.
| What to Monitor | What It Tells You |
| Task Manager → Memory → Committed | Shows current committed memory versus the system commit limit. Repeatedly approaching the limit can point to insufficient commit capacity or an unusually memory-heavy workload. |
| Low-memory or out-of-memory errors | If these continue, check the app’s memory use, page-file configuration, available disk space, and whether a process is consuming abnormal amounts of memory. |
| Disk activity | Sustained heavy disk activity while memory is pressured can indicate paging or another storage bottleneck. A larger page file does not make storage access as fast as RAM. |
| Application stability | Reproduce the same editing, gaming, browser, spreadsheet, or other workload and note whether memory-related crashes recur. |
| Free storage space | A page file consumes disk capacity and needs room to grow when system-managed. If space is tight, use the disk space guide before forcing a larger custom file. |
If committed memory remains well below its limit but the laptop is still slow, look elsewhere. High CPU use, startup programs, background applications, low free disk space, thermal throttling, storage problems, or insufficient physical RAM may be more important than the page file.
[Amazon Products Picked for You]
Actual memory speed may vary depending on the system, CPU, motherboard, BIOS settings, and supported memory configuration. DDR4 3200MHz modules may operate at lower speeds such as 2933MHz or 2666MHz when supported by the host system. Please check your device specifications and compatibility before purchase.
[Specs] DDR3L / DDR3 1600MHz PC3L-12800 / PC3-12800 204-Pin Unbuffered Non ECC 1.35V CL11 Dual Rank 2Rx8 based 512x8
[Specs] DDR3L / DDR3 1600MHz PC3L-12800 / PC3-12800 204-Pin Unbuffered Non ECC 1.35V CL11 Dual Rank 2Rx8 based 512x8
Troubleshooting Common Virtual Memory Problems
If your laptop still feels slow or unstable after changing virtual memory, use the symptom rather than the page-file number to choose your next step.
| Problem | What to Try |
| Low disk space warning | Free storage and avoid an unnecessarily large custom maximum. Automatic paging also needs adequate free space when Windows grows the file. |
| Apps still report out-of-memory errors | Check Task Manager’s Committed value, confirm the page file is not disabled or undersized, review the app’s requirements, and check for unusually high memory use. |
| Laptop feels slower after a custom setting | Return to automatic paging-file management, then check Task Manager for CPU, memory, disk, and startup-app bottlenecks. |
| Games or creative apps lag | Close unnecessary apps, verify the workload is not exhausting physical RAM, update relevant software or drivers, and consider a physical RAM upgrade if your laptop supports one. |
| The setting changes back after restart | On a work or school laptop, device-management policy may control the setting. Check with your administrator before repeatedly overriding it. |
When Should You Leave Virtual Memory System-Managed?
Leave virtual memory on automatic management when your laptop is stable, you do not need a special crash-dump configuration, and an application or support procedure has not given you a specific page-file requirement. Windows is designed to adjust a system-managed page file according to memory demand and other system requirements.
This is also safer than copying a fixed number from another computer. Page-file needs vary with installed RAM, workload, peak committed memory, crash-dump settings, and available disk capacity.
Manual settings make the most sense when you can state exactly why you need them. If you cannot identify that reason, automatic management is usually the better configuration.
Frequently Asked Questions
How to add more virtual RAM to laptop?
Press Win + R, type sysdm.cpl, open Advanced → Performance Settings → Advanced → Virtual Memory → Change, and review the paging-file setting. Leave automatic management enabled for most laptops. Use a custom size only when you have a documented reason, click Set, and restart if Windows requests it.
How to increase virtual memory in computer?
Open System Properties → Advanced → Performance Settings → Advanced → Virtual Memory. Windows-managed paging is the best default for most PCs. If an app, technician, or crash-dump requirement calls for a custom size, clear automatic management, enter the required values, click Set, and restart if prompted.
How to increase VRAM on Windows 7?
VRAM is not the same as virtual memory. VRAM is graphics memory controlled by the GPU and its hardware, firmware, or shared-memory design. Changing the Windows paging file does not increase dedicated GPU VRAM. Microsoft ended Windows 7 support on January 14, 2020, so an unsupported Windows 7 system should be migrated to a supported operating system.
How do I enable virtual memory in Windows 7?
Open System Properties, choose Performance Settings, open the Advanced tab, and adjust Virtual Memory. However, Windows 7 support ended on January 14, 2020. For a current PC, use a supported Windows version and follow its page-file guidance.
Does increasing virtual memory make a laptop faster?
Not necessarily. A larger page file can prevent memory-allocation failures when the existing commit limit is too low, but storage is slower than physical RAM. If the laptop constantly depends on paging, reducing memory use or adding physical RAM where supported can be more effective.
Should I set initial and maximum virtual memory to the same value?
Most users do not need to set either value manually. Windows can manage the paging file dynamically. Use equal fixed values only when a specific application, troubleshooting procedure, or administrator requires that configuration rather than as a general performance tweak.
How do I know if my page file is too small?
Open Task Manager → Performance → Memory and watch the Committed value during the workload that causes trouble. If committed memory repeatedly approaches the displayed limit and you see allocation failures, freezes, or out-of-memory errors, the system may need more commit capacity. Also check for an app using abnormal amounts of memory before changing the page file.
Can I disable the page file if I have a lot of RAM?
A computer with a large amount of RAM may not need much page-file capacity for ordinary committed-memory demand, but a page file or dedicated dump file can still be needed for crash dumps, and some applications expect paging support. Unless you have a specific reason to disable it, leave Windows page-file management enabled.
Conclusion
For most laptops, the best way to manage virtual memory is to let Windows manage the paging file automatically. A custom size is useful when you have a specific application requirement, diagnosed memory-allocation issue, support procedure, or crash-dump requirement—not simply because a generic formula tells you to multiply your RAM.
If you change the setting, click Set, restart when Windows requests it, verify the configuration, and watch Task Manager → Performance → Memory → Committed during your real workload. That gives you a more meaningful measure than judging the change by a single speed test.
Virtual memory supports physical RAM but does not replace it. If the laptop remains slow while committed memory is well below its limit, investigate CPU usage, storage space, startup apps, background processes, thermals, and whether your model supports a physical RAM upgrade.
Sources
- Microsoft Learn: How to determine the appropriate page file size for 64-bit versions of Windows — supports system-managed sizing, commit-limit guidance, page-file growth behavior, and crash-dump requirements.
- Microsoft Learn: Introduction to page files — supports page-file functionality, committed-memory concepts, Task Manager monitoring, and crash-dump context.
- NIST: Prefixes for binary multiples — supports the distinction between GB/MB and GiB/MiB.
- Microsoft Learn: Windows 7 lifecycle — supports the Windows 7 end-of-support status.
- Microsoft Learn: Windows 7 end of support FAQ — supports the January 14, 2020 end-of-support date and migration guidance.
