Mac memory pressure explained: what green, yellow and red mean, and when to act

Why memory pressure matters and Memory Used does not

Every few days someone opens Activity Monitor, sees Memory Used at 7.8 GB of 8, or 15 GB of 16, and decides their Mac is out of memory. It usually is not. macOS deliberately fills RAM: anything it has read recently from disk stays in memory as Cached Files, so it is there instantly if you need it again. Empty RAM is wasted RAM. The moment an app needs that space, the cache is dropped without any cost. So Memory Used being high is the system working as designed, and it tells you nothing about whether the Mac is struggling.

Memory pressure is Apple's answer to this confusion. Instead of counting bytes, it measures how hard the kernel is working to find memory: how much it is compressing, how much it is swapping, how often it has to wait. Apple's own guide says to use the graph, not the numbers, to decide whether your Mac needs more RAM. The graph is color-coded so you do not have to interpret it: green, yellow, red.

This is also why "free memory" apps cannot help. They force macOS to drop its caches so the Memory Used number goes down, which makes the next file you open slower and leaves memory pressure exactly where it was. The memory cleaner apps page goes through this in detail. The short version is that the only ways to lower memory pressure are to need less memory (quit things) or to have more of it (a different Mac).

What green, yellow and red memory pressure mean

Here is what each color means in practice, what the Mac feels like, and what, if anything, to do about it.

A detail people miss: the graph scrolls, so you can see the last few minutes. A single yellow spike while an app launches or a big file opens is nothing. A graph that has been solid yellow since you sat down is the thing to act on. And yellow can appear without any swap at all. A MacRumors poster was puzzled that their "memory pressure turned yellow but the swap was zero", which is simply macOS compressing memory before it bothers writing to disk. Compression comes first; swap comes when compression is not enough.

Is swap used bad on a Mac?

Not by itself. Swap is the space on the SSD where macOS puts memory pages that nothing has touched in a while. On a Mac that has been running for days, there are always such pages: the preferences window you opened on Monday, the helper for an app you quit yesterday, the back half of a document you scrolled past. Writing those to disk costs nothing you can feel, and reading them back takes a fraction of a second on an Apple SSD. So a Mac can show 2, 5 or even 10 GB of swap with memory pressure firmly green and be completely healthy.

The misconception runs deep. One MacRumors poster stated "My simple rule is that if swap used is not zero I need more RAM." By that rule every Mac that has been up for more than a day needs more RAM. The rule that actually works is: swap that is growing while you watch, with pressure yellow, means something is consuming memory faster than macOS can make room. That is a leak or a workload too big for the machine, and the Memory column will show which. Another poster with an 8 GB Air described what red looks like from the chair: "when its RAM is full and starts using SSD swap, it stutters." That stutter is the signature of swap being read back constantly, which only happens under real pressure.

There is a second worry about swap, which is SSD wear. A Hacker News commenter warned that heavy swapping "will lead to early SSD death". The concern is real in principle: SSDs have a finite write life. In practice Apple's SSDs are rated for hundreds of terabytes of writes, and the swap traffic on even a hard-working 8 GB Mac runs to a few gigabytes a day. That is years of headroom. It is a reason to prefer 16 GB if you are buying, not a reason to panic about the swap number on the Mac you have.

What compressed memory is and why it is good news

Before macOS swaps anything to disk, it compresses. It takes the memory of apps you are not actively using and squashes it in RAM, typically to about half its size, which is far faster than writing to disk and reading back. The Compressed figure in the Memory tab summary is how much RAM is currently holding squashed pages; the Compressed Memory column (add it from View, Columns) shows it per process.

A large Compressed figure is macOS stretching your RAM successfully. On a 16 GB Mac doing real work it is common to see 3 to 5 GB compressed with pressure still green. The cost is a little CPU to compress and decompress, which is why a Mac deep in the yellow feels like it is thinking before every app switch: it is decompressing the app you just clicked. If that pause bothers you, the fix is the same as for everything else on this page, which is to quit what you are not using so there is less to compress.

The hierarchy, then, is: RAM, then compression inside RAM, then swap on disk, then the dialog. Green covers the first stage and a bit of the second. Yellow is the second and third. Red is the end of the third. The run out of application memory page is about what happens after red.

Check your own numbers

Copy the five figures from the bottom of Activity Monitor's Memory tab into this and it tells you which stage you are at and whether the problem is load (too much open) or a leak (one thing growing).

If you want the same answer continuously rather than when you remember to look, Safe to Quit watches memory pressure and each process's size over hours and tells you which one is the grower, which is the question Activity Monitor's snapshot cannot answer on its own.

When to act, and on what, in order

Act on yellow that has lasted more than an hour or so, and on any red. Before you start, decide which of two situations you are in, because the fix differs. Load is when many ordinary processes add up: the browser at 4 GB, a design app at 3 GB, a call at 1 GB, each at its normal size. The fix for load is to close and quit things until the graph goes green, and to accept that this workload is near the Mac's limit. A leak is when one process is several times its normal size and still growing: a 12 GB browser, a 9 GB WindowServer, an 8 GB chat app. The fix for a leak is to quit and reopen that one process; nothing else needs to change, and no amount of RAM would have saved you from it for long. Sort by the Memory column and the top entry usually tells you which it is. Then follow this order, safest first.

1. Sort the Memory tab by the Memory column

   The top entries are your browser, WindowServer and your biggest app. Look for one that is several times its usual size. That is the one to deal with; the rest are load.

2. Close the tabs and windows you are not using

   Each browser tab keeps a renderer process alive, and Eclectic Light measured Safari at "an average of more than 120 MB per tab" before the page does anything heavy. The which tab uses memory guide shows how to find the big ones. Press ⌘W generously.

3. Quit apps you are not using, with ⌘Q

   An app in the Dock with a dot under it still holds its memory, even if its window is closed. Quit it properly. Reopening later costs a couple of seconds.

4. Quit and reopen the grower

   If one app is far larger than normal, quit it and launch it again. It starts at its normal size. If it climbs back within an hour, it has a leak and needs an update or a replacement.

5. If WindowServer is the grower, log out and back in

   WindowServer normally sits at 1 to 2 GB. If it is at 5 GB or more and closing windows does not reduce it, Apple menu, Log Out restarts it without a full reboot.

6. Restart if it has been more than a week

   Swap goes to zero, compressed memory is freed, every slow leak is reset. If pressure is green afterward with your usual apps open, the problem was accumulation, not the hardware.

7. Then decide about RAM

   If pressure is yellow within 30 minutes of a restart with only your everyday apps open, and that is every day, your workload is bigger than your RAM. That is the one case where the honest answer is a Mac with more memory, and no app or setting changes it.

Is 8 GB enough? What memory pressure looks like on 8 GB and 16 GB Macs

Memory pressure is where the 8 GB versus 16 GB question becomes concrete. macOS, WindowServer and the always-on daemons take a couple of gigabytes before you open anything. A browser with a dozen tabs takes 3 to 4 GB. A video call takes 1 GB. So an 8 GB Mac with a browser, a chat app and a call open is already compressing, and a Hacker News commenter put it plainly: "Again it comes down to the fact that 8GB means you are almost guaranteed to be on swap." That does not make 8 GB unusable; macOS is very good at compression and Apple's SSDs are fast enough that light swapping is invisible. It means an 8 GB Mac lives closer to yellow and gets there with fewer things open.

A 16 GB Mac with the same workload sits in the green with room to spare, and only reaches yellow with a genuinely heavy job or a leak. The difference shows up less as speed and more as how often you have to think about it. Another Hacker News commenter described the 8 GB experience as a system that is "palpably less responsive with a couple of documentation / bad web interface Safari tabs too many", which is the yellow zone exactly: not broken, just a step behind.

So if you are deciding whether your Mac has enough: restart it, open your normal day's apps, work for half an hour, and look at the graph. Green means yes. Yellow means you are at the limit and will feel it on heavy days. Red within half an hour of a restart, with no leak in the Memory column, means no.

What does not lower memory pressure

Memory cleaner and RAM booster apps. They drop Cached Files so Memory Used looks smaller. Pressure is unchanged, and the next thing you open is slower because its cache is gone. Some of them also run a background agent that uses memory itself.

Purging with Terminal commands. Same effect as the apps, same lack of benefit. macOS reclaims caches the instant an app needs the space, so doing it by hand only makes things slower for a minute.

Closing windows without quitting. Helps a little with WindowServer, does nothing for the app's own memory. Use ⌘Q.

Turning off visual effects or Spotlight. Neither holds meaningful memory. Spotlight's indexer, mds_stores, can use memory while indexing, but it finishes and releases it.

Reinstalling macOS. The workload comes back with your apps and your habits, so the pressure does too. Reinstalling is for a broken system, not a busy one.