Updated November 2026 · 7 min read

How to Check RAM Usage on Windows 11: 3 Methods

"How much memory am I using?" sounds like a simple question, but Windows 11 reports memory in at least four different numbers, and third-party tools often count them differently. This guide shows three reliable ways to check RAM usage on Windows 11 and — more importantly — how to read the result without panicking about a figure that is actually healthy.

Method 1: Task Manager (fastest)

Press Ctrl + Shift + Esc, then open the Performance tab and click Memory. The graph at the top shows the last 60 seconds, and the numbers below it tell most of the story:

In use — memory currently allocated by running processes and the kernel.
Available — free memory plus standby (cached) memory that Windows can hand out instantly.
Committed — memory promised to processes, including the page file. It can legitimately exceed physical RAM.
Cached — recently read files kept in RAM. This is a performance feature, not waste.
Paged pool / Non-paged pool — kernel memory. Non-paged pool growing into the gigabytes over days is a driver leak.
Speed, Slots used, Form factor — hardware facts. "2 of 4" means you have two free slots.

The percentage shown under the graph is "in use" divided by total RAM. It does not include standby memory, so a 70% reading may still leave several gigabytes immediately available.

Which tab names the real culprit?

The Processes tab is convenient but groups apps: Chrome's thirty renderer processes appear as one line. For accurate numbers switch to the Details tab, right-click any column header, choose Select columns, and add Commit size and Working set (memory). Then click the Memory (active private working set) header to sort descending. The top few entries are usually a browser, a chat client, or an updater running in the background since login.

Tip: right-click a process → Properties → Details to see the publisher, which is the quickest way to tell a system component from a leftover installer.

Method 2: Resource Monitor (per-process detail)

Press Win + R, type resmon and press Enter, then open the Memory tab. The physical memory bar breaks usage into hardware reserved, in use, modified, standby and free — the breakdown Task Manager hides. Below it, the process table lists Working Set, Commit, Shareable and Private memory plus Hard Faults/sec.

Hard faults are the number that matters most. A hard fault means Windows had to read a page from disk because it was no longer in RAM. A few per second are normal; hundreds per second sustained while you are not opening anything new means the system is paging and will feel slow. That is the point where memory pressure is real, regardless of what the percentage says.

Method 3: PowerShell or Command Prompt (numbers you can log)

If you want figures you can copy into a note, or check history over time, use the built-in tools:

Get-CimInstance Win32_OperatingSystem |
  Select-Object TotalVisibleMemorySize, FreePhysicalMemory

Get-Counter '\Memory\Available MBytes','\Memory\Committed Bytes'

The first command returns values in kilobytes; divide by 1,048,576 to get gigabytes. The second returns megabytes for "Available" and bytes for "Committed" — and unlike Task Manager it refreshes on demand, so you can run it before and after closing an app.

An older one-liner still works in cmd:

systeminfo | findstr /C:"Total Physical Memory" /C:"Available Physical Memory"

How to read the numbers without panicking

High "used" is not a fault. Windows fills spare RAM with cached file data and drops it the moment an app asks for memory. An idle PC showing 60–75% is usually doing exactly what it should.
Third-party tools disagree because they count standby as used. A widget showing 92% may be reporting "used + cached"; Task Manager would call most of that available.
Memory Compression appears as a process using a few hundred megabytes. It stores compressed pages instead of writing them to disk — leave it alone.
Committed above physical RAM is normal as long as the page file is on a healthy SSD and hard faults stay low.
Hardware reserved of a few hundred megabytes is normal; on laptops with integrated graphics, shared GPU memory also consumes part of the total.

What counts as normal on Windows 11?

After a clean boot, expect roughly 3–5 GB in use on an 8 GB machine and 4–7 GB on a 16 GB machine, depending on startup apps, antivirus and whether a browser restored its tabs. Steady usage near 60–80% with low hard-fault activity is fine. Warning signs are different: available memory under about 500 MB, sustained hard faults, or the "Committed" figure pushing against the commit limit while the disk light stays on.

When to dig deeper

If usage climbs hour after hour with the same apps open, suspect a leak. Sort the Details tab by memory, note the top three processes, and check again in an hour. A process whose private working set keeps growing without new work is the leak. For kernel memory, watch Non-paged pool in the Performance tab over a day — steady growth of hundreds of megabytes usually points to a driver.

Get-Process | Sort-Object WS -Descending |
  Select-Object -First 10 Name, Id, WS

This lists the ten largest processes by working set, in bytes. It is the fastest way to compare two points in time without keeping Task Manager open.

Want per-app numbers in one window? MemoryCleaner shows memory per app, lets you search by name, and releases idle pages without closing anything. free during the launch promotion.

Download MemoryCleaner

FAQ

Is 80% RAM usage bad?

No, if "available" memory is still measured in gigabytes and hard faults are low. Windows deliberately uses RAM for cache; forcing usage down usually just slows the next app launch.

Why do Task Manager and a third-party tool show different numbers?

They count different things. Task Manager separates standby from used; many widgets add standby to used. Both can be technically correct and still describe very different situations.

Does Chrome inflate RAM usage?

Each tab and extension can be its own process, so yes — but that isolation is also why one bad page does not crash the browser. Check it with the Details tab or Chrome's own task manager (Shift + Esc).