RAMKeeper
What does "swap used" mean on a Mac?
It is the single most useful number in the Memory tab, and the only one that tells you plainly that your Mac has run out of the real thing.
Swap is space on your disk that macOS uses as if it were memory. When the demand for RAM is higher than the RAM you have, the system writes the least-needed pages out to disk to make room, and reads them back when something wants them again.
Activity Monitor shows it as Swap Used at the bottom of the Memory tab. On the command line:
sysctl -n vm.swapusagewhich prints the total, the used and the free portion of the swap file, and is the reading worth taking because it is one line and needs no window open.
Why a number above zero is not automatically bad
macOS does not swap as a last resort only. It will move pages it is fairly sure nobody wants out to disk as ordinary housekeeping, and a few hundred megabytes of swap on a machine that has been awake for a week is not a symptom of anything.
Before it swaps, it compresses. That is the step people miss: on the machine these guides are measured on, the compressor was holding 21.3 GB of data in 10.9 GB of physical memory, a ratio of about 1.9 to 1, with swap at zero bytes and free memory at 0.71 GB of 64 GB. Compression absorbs a great deal before the disk is involved at all.
The pattern that is bad
Not the value, the shape. Take the reading once a day for a week, at the end of a working day rather than after a restart, and look at how it moves:
| Shape | What it means |
|---|---|
| Stays at zero, or a small figure that does not grow | Your memory is keeping up. Nothing to do. |
| Climbs through the day, resets when you restart | You are at the edge of what the machine has. It works, and you will feel it whenever you add one more app. |
| Gigabytes every day, and climbing across days | Demand is above what the machine has. This is the reading that settles the question. |
| Jumps sharply at a particular time every day | One process is doing something heavy on a schedule. Find it before concluding anything about the machine. |
Why swapping feels so much worse than it sounds
A page fetched from RAM and a page fetched from an SSD differ by orders of magnitude in latency, and the fetch happens while your app is waiting to do the thing you just asked it to do. That is why a Mac deep in swap does not feel uniformly slower, it feels like everything pauses. The pauses are page faults being serviced.
It also writes. Sustained heavy swapping means sustained writes to the internal drive, which on an Apple silicon Mac is soldered in place, so this is worth avoiding for reasons beyond speed.
What to do about it
Nothing, directly. Swap is not a setting, there is no safe way to disable it, and no utility reduces it except by reducing what your Mac is being asked to hold. The two useful actions are upstream of it:
- Find what is demanding the memory.
top -l 1 -o mem -n 10 -stats pid,command,mem, then check whether the app is leaking or just large with the one-hour leak test. - Decide whether it is the workload or the machine. A week of swap readings is exactly the evidence that answers it: how much RAM do I need, or for the two common versions of the decision, is 8 GB enough and 16 GB against 24 GB.
Disclosure: published by RAMKeeper, which sells a Mac memory tool. RAMKeeper does not reduce
swap and nothing does except reducing demand. Figures measured with vm_stat and
sysctl on 11 September 2026.