Open Task Manager on a Windows 11 system with 16 GB of RAM and you might see “7.4 GB used” — yet the Memory section in Resource Monitor shows something called Compressed taking up 1.2 GB of that. What is that, where does it come from, and is it hurting your performance? This article answers all of it.
What Is Windows Memory Compression?
Memory compression is a feature built into the Windows Memory Manager that compresses in-RAM data before writing it to the pagefile on disk. The goal is to keep more data in fast RAM rather than swapping it to a comparatively slow storage device.
When physical RAM fills up, Windows has two choices:
- Move memory pages to the pagefile (swap) on disk — even on an NVMe SSD, this is much slower than RAM
- Compress those pages and keep them in RAM — slower than uncompressed RAM access, but much faster than any storage medium
Memory compression was introduced in Windows 10 and has been refined in Windows 11. The compression/decompression work is handled by the System process, specifically the Memory Compression component visible in Task Manager’s Details tab.
How to See Memory Compression in Action
Open Task Manager (Ctrl+Shift+Esc) and click the Performance tab, then Memory. You’ll see a breakdown that includes:
- In use — RAM actively mapped to running processes
- Compressed — Data currently held in compressed form in RAM
- Available — RAM free for immediate use
- Cached — Disk cache held in RAM (released when needed)
- Committed — Total virtual memory committed by all processes
For a more detailed view, open Resource Monitor (Win+R, type resmon). The Memory tab shows per-process working sets and the overall Standby/Modified/Free breakdown.
You can also query compression stats directly in PowerShell:
# Check compressed memory statistics
Get-Process | Where-Object {$_.Name -eq "System"} | Select-Object WorkingSet, PrivateMemorySizeFor detailed kernel memory stats:
# View memory compression info via WMI
Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object TotalVisibleMemorySize, FreePhysicalMemory, TotalVirtualMemorySizeWhen Memory Compression Helps
Memory compression is largely beneficial in these scenarios:
You have 8 GB of RAM or less. With limited physical RAM, compression extends how much data can stay resident without hitting the pagefile. Compressing 2:1 effectively gives you 25% more usable memory headroom.
You’re running many background apps. Browser tabs, Electron apps, and open documents that sit idle are good compression candidates — they compress well and are rarely accessed at speed.
Your storage device is an HDD or a slow SATA SSD. Decompressing in RAM (microseconds) beats paging to spinning rust (milliseconds) by orders of magnitude.
When Memory Compression Hurts
Compression becomes a problem in specific high-performance scenarios:
Gaming with Heavy VRAM Pressure
When a game and Windows are both competing for physical RAM, compression kicks in aggressively. If the game then needs to access compressed assets, the CPU must decompress them — adding latency and consuming CPU cycles that could go to game logic. On a system with 16 GB running a game that uses 12–14 GB, this can manifest as micro-stutters.
CPU-Bound Workloads
Compression and decompression are not free. The Memory Compression store uses CPU resources. On older quad-core CPUs already running hot, you may see 3–5% CPU overhead attributed to the System process during heavy memory pressure.
Low-Latency Audio Production
DAW applications and real-time audio processing are especially sensitive to unpredictable latency. Decompression delays, even at microsecond scale, can cause buffer underruns and audio glitches. Audio producers typically disable compression as part of their latency optimization pass.
How to Disable Memory Compression
Disabling memory compression forces Windows to page directly to disk instead of compressing. This is only recommended on systems with 16 GB+ of RAM where paging is already rare, or in professional audio/low-latency environments.
Open PowerShell as Administrator and run:
# Disable memory compression
Disable-MMAgent -MemoryCompressionTo re-enable it:
# Re-enable memory compression
Enable-MMAgent -MemoryCompressionTo check the current state:
Get-MMAgentLook for MemoryCompression : True or False in the output. A reboot is required for the change to take effect.
Practical Decision Guide
| Your Setup | Recommendation |
|---|---|
| 8 GB RAM, any storage | Keep compression enabled |
| 16 GB RAM, gaming only | Keep compression enabled — paging is rare anyway |
| 16 GB RAM, heavy multitasking | Keep compression enabled |
| 32 GB+ RAM, DAW/audio production | Consider disabling compression |
| 32 GB+ RAM, gaming + streaming + dev work | Enabled is fine; you have headroom |
| 8 GB RAM, frequent stutters in games | Don’t disable — add more RAM instead |
The Real Fix: More RAM
If you’re seeing heavy memory compression during normal use, the underlying problem isn’t compression — it’s that you don’t have enough RAM for your workload. Adding RAM from 8 GB to 16 GB (or 16 GB to 32 GB) will eliminate the conditions that trigger heavy compression in the first place, and it’s the most impactful fix.
Memory compression is a symptom management feature, not a root cause solution. Before disabling it, ask whether adding physical RAM would solve the problem more effectively.
Monitoring Compression Over Time
To track whether compression is impacting your system during normal use, enable Performance Monitor (perfmon) and add these counters:
Memory\Pages/sec— High values (>100 sustained) indicate paging pressureMemory\Cache Bytes— Available disk cache in RAMProcess(System)\Working Set— Includes the memory compression store
A healthy system with adequate RAM will show near-zero Pages/sec under normal workloads. If it’s consistently elevated, compression is working overtime to compensate for insufficient RAM.
Windows 11’s memory compression is well-engineered and helpful for the majority of use cases. Understanding it lets you make an informed decision rather than applying a blanket disable and wondering why nothing changed.