Where to Change the Paging File in Windows (And What It Actually Controls)
The paging file — sometimes called the virtual memory file or pagefile.sys — is one of those Windows settings that sits quietly in the background until something goes wrong. Whether you're seeing sluggish performance, low memory warnings, or you've just added a new drive and want to optimize how your system uses storage, knowing where to find and adjust the paging file is genuinely useful knowledge.
What Is the Paging File?
When your PC runs low on RAM, Windows doesn't just crash — it temporarily offloads less-active data to a reserved space on your storage drive. That reserved space is the paging file. It acts as an overflow buffer, letting the system keep more processes running than physical RAM alone could support.
The trade-off is speed. RAM operates in nanoseconds; even a fast NVMe SSD operates in microseconds. So while the paging file prevents hard failures, leaning on it heavily does slow things down. It's a safety net, not a substitute for adequate RAM.
Where to Find the Paging File Settings in Windows 10 and 11
The setting is buried a few layers deep, but the path is consistent across modern Windows versions:
- Press Windows key + R, type
sysdm.cpl, and press Enter - Go to the Advanced tab
- Under the Performance section, click Settings
- In the Performance Options window, click the Advanced tab
- Under Virtual memory, click Change
Alternatively, you can search for "Adjust the appearance and performance of Windows" in the Start menu — it leads to the same Performance Options panel.
This is the Virtual Memory dialog, and it's where all paging file configuration happens.
What You Can Actually Change Here
Once inside the Virtual Memory dialog, you'll see a list of every drive connected to your system. For each drive, you have three options:
| Setting | What It Does |
|---|---|
| Custom size | You manually set the initial and maximum size in MB |
| System managed size | Windows automatically adjusts the paging file as needed |
| No paging file | Removes the paging file from that drive entirely |
By default, Windows places the paging file on your system drive (C:) and manages the size automatically. This works fine for most people, but there are legitimate reasons to move or resize it.
Why You Might Want to Move the Paging File
🖴 Moving to a Faster or Less-Used Drive
If you have a secondary SSD that sees less read/write activity than your OS drive, placing the paging file there can reduce I/O contention. The OS drive is constantly busy with system processes, app installs, and temp files — offloading the paging file distributes that workload.
On the other hand, if your secondary drive is a traditional HDD, moving the paging file there will likely make things worse. HDDs are dramatically slower than SSDs for the random read/write patterns the paging file generates.
Protecting Drive Lifespan
SSDs have a finite number of write cycles. On systems where the paging file is accessed heavily — workstations running memory-intensive software, for example — some administrators prefer to move it to a drive specifically designated for high-write tasks or a larger drive with more write endurance to spare.
Resolving Low Disk Space Issues
If your C: drive is running tight on space and the paging file is consuming several gigabytes, relocating it to a larger drive frees up room without requiring a full storage upgrade.
Variables That Affect the Right Configuration for You
There's no universal "correct" paging file size or location. What makes sense depends on several factors:
Amount of installed RAM Systems with 32GB or more RAM rarely touch the paging file under normal workloads. Systems with 8GB or less may rely on it regularly. The lower your RAM, the more the paging file's location and size actually matters to day-to-day performance.
Type of storage available An NVMe SSD as a secondary drive is ideal for hosting the paging file. A SATA SSD is a reasonable choice. An HDD is a last resort, not an improvement.
Your workload Video editing, virtualization, database work, and running multiple VMs are all memory-hungry tasks. General web browsing and document work rarely stress the paging file at all.
Whether you've manually set RAM limits Some developers and IT administrators set explicit paging file sizes to prevent Windows from dynamically expanding it — useful in environments where predictable disk usage matters more than flexibility.
💡 One Common Mistake: Deleting It Entirely
Some guides recommend removing the paging file on systems with large amounts of RAM to "speed things up." This is risky. Certain applications and Windows components explicitly check for or write to the paging file regardless of available RAM. Removing it can cause crashes, failed memory dumps, and application errors that are difficult to diagnose. Unless you have a very specific reason and understand the implications, leaving at least a small paging file in place is generally the safer path.
How Drive Configuration Shapes the Decision
If your system has only one drive, there's no meaningful choice to make — the paging file stays on C:, and the main question is whether to let Windows manage the size or set it manually.
If you have multiple drives, the decision becomes more nuanced. A second NVMe drive creates a genuine opportunity for optimization. A mix of SSD and HDD storage raises questions about which tasks benefit most from each drive type. And on workstations with RAID configurations or storage pools, paging file placement interacts with how the storage controller distributes reads and writes.
The right answer in each case depends on how those drives are configured, what they're used for, and how much the paging file actually gets used on that specific machine — which varies more than most guides acknowledge.