How to free up RAM on a Mac

There is exactly one reliable way to make an app give memory back, and it is not a button in a utility.

Last updated October 9, 2026 · by the RAMKeeper team

Taking the question literally: you want an application to release memory it is holding. Here is what does that, ranked by how well it works, followed by the part most articles on this topic leave out.

What actually frees memory

Quit the app and open it again. This is the whole list of things that reliably work. Only the process that allocated memory can release it, and quitting is how you ask. Everything below is a variation on this or a way of avoiding it.
Close what you are not using, especially browser tabs. Each tab is its own process with its own footprint; twenty of them are grouped under one name, which is why a browser looks like a single enormous app. Our measured reading had Chromium at 22 processes and Vivaldi at 15.
Restart the Mac if swap has been climbing for days. Not as maintenance, and not because memory needs clearing, but because it resets processes that have grown past what they need.
Log out and back in as the smaller version of the same thing: it restarts everything running as you while leaving the system alone.

What does not free memory, despite appearances

sudo purge. It empties the file cache, which is not memory you were short of. You have converted memory nobody was waiting for into disk reads you now have to wait for. It exists so developers can measure against a cold cache. Why the cache is large on purpose.
Apps with a free-up-memory button. The usual mechanism is to allocate a large block, force macOS to compress or evict other things to satisfy it, and then release it. The free-memory figure moves, which is the point, and the machine is no better off. We measured what they actually change.
Suspending a process. It stops the app growing; it does not hand back what the app already holds. Useful for getting through an afternoon, not a fix, and worth saying because our own app does this and is explicit about it in its own interface.
Anything aimed at wired memory. It cannot be paged out or compressed by definition, and no process owns it. What wired memory actually is.

When you should not free up RAM at all

Most of the time, and this is the part worth reading twice. Unused memory is wasted memory, so macOS deliberately keeps very little of it free. A reading from the machine these guides are measured on, 11 September 2026:

Free memory: 0.71 GB of 64 GB installed.
Swap used: 0 bytes.
Cached file data: 13.87 GB, all of it instantly available to any app that asks.

Almost nothing free, nothing paging to disk, and 14 GB of cache doing useful work. If your Mac looks like that, there is nothing to free and no action to take. The figure that would tell you otherwise is memory pressure, not free memory: see what each figure in the Memory tab means.

If you are here because your Mac is slow

Then freeing memory is the wrong frame, and the right sequence is short:

Check whether memory is even the problem: sysctl -n vm.swapusage and memory_pressure -Q. Zero swap and green pressure means look elsewhere.
If it is memory, find out which app: top -l 1 -o mem -n 10 -stats pid,command,mem.
Check whether that app is misbehaving or simply large: the leak test takes about an hour.
If the answer is that you are genuinely short of memory, no software fixes that.

RAMKeeper automates step two and three permanently and can restart the repeat offender on a rule rather than on your attention. What it does not have is a button that frees RAM, because the honest version of that button is "quit the app", and you already have it.

Disclosure: published by RAMKeeper, which sells a Mac memory tool. The figures here were measured with vm_stat on 11 September 2026 on the machine described in the measured reading guide.