A Mac RAM usage monitor tells you which tab to close first

The fan is audible, scrolling has started to stutter, and the obvious move is to install something that puts a memory figure in the menu bar. A day later the figure is there, it says 26.4 GB of 32 GB, and nothing about that sentence says what to close. The number was never the missing piece. What was missing is a way to get from a number to a decision.

macOS already ships with everything needed to make that decision, and the tools that put a graph in the menu bar are useful for a narrower reason than most people install them for. Separating the two makes the next hour productive instead of superstitious.

Memory used is the wrong number to watch

The instinct behind watching memory is that unused memory is good memory. macOS is built on the opposite assumption. Apple's own documentation for Activity Monitor states the position directly.

When you have free or unused memory, your computer performance does not necessarily improve. macOS obtains the best performance by efficiently using and managing all of your computer's memory. Source: support.apple.com

A large part of what looks like consumed memory is Cached Files, which is the space the system has filled with recently used file data because that space would otherwise be idle. It is released the moment something needs it. A monitor that reports one aggregate percentage cannot distinguish that from memory genuinely held by a running application, which is why a menu bar reading of 80 per cent can appear on a machine that is running perfectly and on one that is about to stall.

The figure that separates those two cases is memory pressure, and it exists because a single usage percentage cannot answer the question. Apple documents it as being determined by the amount of free memory, the swap rate, wired memory and file cached memory. In other words it is a composite of how much is left and how hard the system is working to keep it that way.

The reading is deliberately coarse. Green means all of the installed RAM is being used efficiently. Yellow means the machine might eventually need more RAM. Red means it needs more RAM now. A machine sitting on green with 90 per cent of memory reported as used needs nothing done to it. A machine touching yellow every afternoon has a real problem, whatever the percentage says.

Where the actionable detail lives

Activity Monitor is in Applications, inside the Utilities folder, and its Memory tab holds more than the graph at the bottom. The fields under it are worth reading once rather than glanced at forever: Physical Memory is the RAM installed, Memory Used is what is currently allocated, App Memory is the part belonging to applications, Wired Memory is the part the system requires and cannot cache or move out, Compressed is memory that has been squeezed to free space for active work, Cached Files is the reclaimable part described above, and Swap Used is how much has been pushed onto the startup disk.

Two of those deserve attention when the machine feels slow. Rising Swap Used means the system has run out of room and is writing to storage, which is the point at which a stutter becomes noticeable. A large Compressed figure means macOS has already started squeezing inactive applications to keep the active one responsive, which it does automatically as the machine approaches its limit.

Wired Memory is the one figure that no amount of closing will move, since it is what the system needs to operate and cannot be cached or paged out. On a machine with virtualisation software, a container runtime or heavy peripheral drivers installed, this value is meaningfully larger, and it is subtracted from what everything else has to share. That makes it the first thing to look at when a machine with plenty of installed RAM still reaches yellow pressure with only a handful of applications open, because the answer is background software rather than the visible workload.

The column that turns this into a decision is per process. Sorting the process list by memory shows which application holds the most, and adding the Compressed Memory column shows, in the VM Compressed value for each row, how much of that application has already been compressed. An application at the top of the list whose contents are heavily compressed is the one whose windows have not been touched in hours, and it is the one to quit first.

Three readings that need nothing installed

For anyone comfortable in a shell, three built-in commands answer the same questions faster than any interface, and none of them require a download. They are also the readings worth capturing when a problem needs to be described to somebody else.

memory_pressure prints the system total, the free and purgeable page counts, and a pressure figure. vm_stat prints the raw page counters, including the page size, which is 16384 bytes on Apple silicon, so a count of pages has to be multiplied by 16 KB rather than 4 KB to reach a figure in gigabytes. top -o mem lists processes ordered by memory, refreshing live, which is the quickest way to catch a process that grows steadily over minutes rather than one that is simply large.

Keeping a terminal open for readings like these is the reason some browsers include one, so that a check does not mean leaving the window currently being used. That pattern is what a built-in terminal is for.

What a menu bar monitor is actually good for

Given that Activity Monitor is free and more detailed, the honest case for a menu bar tool is narrow: it is a tripwire, not an analysis tool. Its value is noticing that pressure went yellow while attention was elsewhere, so that the investigation happens at the moment of the problem instead of an hour later when the evidence has gone.

Tool	Cost	What it gives	Requirement
Activity Monitor	Included with macOS	Memory pressure, per process memory, VM Compressed	None
memory_pressure, vm_stat, top	Included with macOS	Raw page counts and live process ordering	Terminal
Stats	Free, MIT licence	Menu bar graphs for memory, CPU, disk, network	macOS 12 or later
iStat Menus	Paid, also on Setapp at USD 9.99 per month	Menu bar items plus detailed drop down menus	macOS 11 or later
Browser task manager	Included with the browser	Memory per tab and per extension	Chromium based browser

One current detail matters when a menu bar tool appears to be broken rather than merely quiet. macOS 26 added a privacy control under System Settings, in the Menu Bar section, and applications now have to be allowed there before they can display menu bar items. A monitor that is running, with a module active and a widget enabled, yet shows nothing at all, is almost always sitting behind that permission rather than misconfigured.

Telling a memory problem from the things that feel like one

Memory gets blamed for slowness that has another cause, and a monitor makes that easier rather than harder, because it supplies a number that always looks high enough to be guilty. Three other causes produce almost the same symptoms and are worth ruling out before anything is bought or closed.

A nearly full startup disk looks exactly like a memory problem, because swap is written to that disk. When there is no room to write, the system has nowhere to put the pages it wanted to move, and everything waits. The check is the Storage section of General settings rather than any memory reading, and the relief is deleting files rather than quitting applications.

Sustained heat is the second. When a machine has been rendering, compiling or sitting in a long video call, the processor slows itself to stay within its thermal limit, and the memory graph looks unchanged throughout because memory was never the constraint. The tell is that the slowdown arrives after twenty minutes of heavy work rather than at the moment a new application opens.

A single misbehaving process is the third, and it is the one a monitor genuinely catches. A process with a slow leak grows steadily rather than jumping, which is invisible in a snapshot and obvious in top -o mem watched for a minute. The fix is quitting and reopening that one application, not a reboot of the machine.

What all three share is that the correct diagnosis comes from watching change over time rather than reading a level once. That is the case for keeping a pressure indicator visible during work and the case against reacting to any single figure. A reading taken at the moment the machine stutters is worth more than a dozen taken while it is fine.

The browser is usually the answer, and it has its own monitor

On a machine used for web based work, the honest answer to which process holds the memory is the browser, every time. That is not a defect. Each tab runs in its own process so that one page cannot take down the rest, and the cost of that safety is measured in processes.

Which means Activity Monitor gives an incomplete answer on its own. It reports a dozen renderer processes with identical names, and matching those to pages is guesswork. A Chromium based browser has a task manager of its own, reached under More tools, and its rows are named after the page or extension they belong to. Sorting it by memory footprint names the tab to close, and ending a process there closes that tab without touching the rest of the session, at the cost of any unsaved work in it.

Two settings change the shape of the problem rather than reacting to it. Memory Saver deactivates tabs that are not being used and reloads them on return, and performance issue alerts, which are on by default, prompt when browsing performance drops. Both trade a reload delay for memory, which is the right trade for reference pages and the wrong one for a page holding a half written form.

There is a structural version of the same trade. When every service lives as a tab in one window, the browser is a single opaque block in any monitor, and Memory Saver decides for you which of them goes cold. When each service has its own window, the accounting becomes legible: the window that is costing memory is visible, and the decision to put a service to sleep or keep it live becomes a deliberate one, organised by the task in hand rather than by tab order. That is the idea behind Workspaces, and the list of supported apps is the practical check of whether the daily set is covered.

What to change first

Open Activity Monitor, add the Compressed Memory column, and watch the memory pressure graph rather than the percentage for one working day. If pressure stays green, nothing needs buying or closing. If it reaches yellow, the browser task manager will name the tab responsible, and the longer term fix is giving the heaviest services their own windows so the accounting stays readable, which is what SpaceDeck is built for.