16, 32 or 64GB RAM for Windows 11, WSL and gaming?
Size Windows 11 memory by workload, understand committed memory and page file, and test XMP/EXPO stability instead of trusting a “RAM cleaner”.
Tested onPro (26H2) · Build 26300.9457 · x64
E1- Build
- 26300.9457
- Edition
- Pro (26H2)
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-28
- Page type
- Concept
The short answer
Section titled “The short answer”- 16GB: browser, Office, light gaming, one VM.
- 32GB: gaming + browser/Discord, WSL2, containers, photo editing. The power-user sweet spot.
- 64GB: local LLMs, large VMs, 8K video, heavy CAD. Buy it for a named workload, not “future-proofing”.
More RAM does not make a CPU/GPU faster. Too little RAM makes everything feel broken.
Match to workload
Section titled “Match to workload”| Workload | Comfortable | Notes |
|---|---|---|
| Web/Office/video | 16GB | 8GB is painful with a modern browser |
| 1080p gaming | 16GB | 32GB if you keep a browser/Discord open |
| 1440p+ gaming + streaming | 32GB | Capture/overlays add memory |
| WSL2/containers | 32GB+ | WSL can consume a lot; cap it in .wslconfig |
| Local LLM | 64GB+ | Model size + context + OS |
| VMs | 32–64GB | RAM is often the first limit |
Read the right numbers
Section titled “Read the right numbers”- In use is not the whole story; Windows caches aggressively.
- Committed (Task Manager → Performance → Memory) shows commit charge vs limit.
- Hard faults/sec and paging activity indicate pressure.
- A “RAM cleaner” that frees standby memory usually makes performance worse.
Get-Counter '\Memory\Available MBytes','\Memory\% Committed Bytes In Use'Dual channel and speed
Section titled “Dual channel and speed”- Two matched sticks in the correct slots > one stick.
- Enable XMP/EXPO only if the kit and motherboard support it.
- Test stability after enabling: boot, stress, no WHEA/random crashes.
- A fast kit running unstable is worse than a slower stable kit.
Page file
Section titled “Page file”Do not disable the page file to “save SSD writes”. It can cause crashes/low-memory errors and breaks some apps. Let Windows manage it, or set a sane fixed size if you have a specific reason.
Test before blaming RAM
Section titled “Test before blaming RAM”- Windows Memory Diagnostic (
mdsched.exe) for a basic pass. - MemTest86 (third-party) for a longer test if you overclock.
- One stick at a time to isolate a bad module.
- Check QVL for the motherboard/CPU if buying an extreme kit.
Related hardware guides
Section titled “Related hardware guides”- XMP/EXPO: enable it, then prove it is stable
- ECC and WHEA: what Windows can tell you
- Memory compression and the page file
- Channels, ranks and shared graphics memory
- Memory fault finding, from symptom to RMA