How to free up RAM on a Mac: what works, what doesn't, and when to leave it

On a Mac, free RAM is not the goal. macOS deliberately fills spare memory with cached files and compresses memory that apps are not using, so the Memory Used figure stays high on a healthy Mac. What you want is low memory pressure. This guide shows how to check whether memory is really short, how to get it back when it is, and which popular tricks do nothing useful. To read every figure in Activity Monitor first, see how to check CPU and memory usage.

First, check whether you need to free RAM at all

Open Activity Monitor (⌘Space, then type its name), click Memory and look at the graph at the bottom.

Memory pressure is the reading that matters. Apple’s guide says it “is determined by the amount of free memory, swap rate, wired memory, and file cached memory” (Apple: memory usage, macOS 26). The colors have plain meanings: green means the Mac is using all of its RAM efficiently, yellow that it might eventually need more, red that it needs more RAM (Apple: does your Mac need more RAM).

If the graph is green, stop here: there is nothing to free, and quitting apps only makes them slower to come back. If the Mac still feels slow, the cause is elsewhere, and why your Mac is so slow goes through the other suspects. Some swap in use is not a problem either.

For example, on a 16 GB Apple M4 Mac, 1.3 GB of swap was in use while memory_pressure reported 42% of memory free (measured October 1, 2026). Swap that keeps growing while the graph turns yellow is a different story. Swap is space on the startup disk that the system moves memory pages out to and reads them back from, and that disk is slower than RAM (Operating Systems: Three Easy Pieces). A Mac that keeps reading pages back from swap spends that time waiting. The glossary covers memory pressure and swap used in more detail.

How to free up RAM on a Mac

1. Sort the Memory tab. In Activity Monitor’s Memory tab, click the Memory column heading so the largest process is first. A browser or an Electron app such as Slack may appear as many rows; add them up.
2. Quit apps you are not using. Quit them normally with ⌘Q, or select the process, click the Stop button and choose Quit. Keep Force Quit for apps that do not respond; Apple warns that a force-quit process with files open may lose data (Apple: quit a process).
3. Relaunch the app that keeps growing. If one app’s Memory figure climbs for hours while you do nothing new in it, quit and reopen it. That returns everything it was holding, including memory it leaked.
4. Close browser tabs. Each tab costs memory. In Chrome, More > More tools > Task Manager sorted by Memory shows which tab or extension is heavy (Chrome Help: speed up Chrome), and Settings > Performance > Memory Saver deactivates tabs you are not using (Chrome Help: Memory Saver).
5. Trim login and background items. In System Settings > General > Login Items & Extensions, remove apps you do not need at login and review App Background Activity (Apple: Login Items & Extensions, macOS 26). Fewer apps start, so less memory is taken before you open anything.
6. Restart if pressure stays high. A restart ends every process, clears swap and starts clean. If pressure is back to yellow a day later, the cause is an app you reopen, and steps 1 to 3 will find it.

How to tell a memory leak from normal use

A memory leak is an app that keeps claiming memory and never gives it back. The pattern is steady growth: the app’s Memory figure rises over hours, even while it sits in the background, and only a relaunch brings it down.

Normal use looks different. Memory rises when you open a large file or many tabs and falls, or at least stops rising, when you close them. A photo editor holding 6 GB with a large project open is doing its job; a chat app holding 6 GB after three idle days is not.

Activity Monitor only shows the current figure, so to catch a leak you have to check the same app several times over a day and compare. This is where a monitor with history helps; see Where Orcylo fits, below.

Why RAM cleaners and sudo purge don’t help

Both target memory that is already working for you.

• sudo purge is a Terminal command whose manual page describes it as forcing the disk cache “to be purged (flushed and emptied)”. The same page says it “does not affect anonymous memory that has been allocated through malloc, vm_allocate, etc.”, which is the memory your apps hold (purge(8)). Cached Files drops, Memory Used looks lower for a moment, and the next files you open have to be read from disk again.
• RAM cleaner apps mostly do the same thing, emptying cached files or forcing compressed memory out. Apple defines Cached Files as files cached “into unused memory to improve performance” (Apple’s memory guide), so emptying it gives up that speed for a number that looks better.

Some cleaners also quit background apps. That part does free memory, because it is step 2 above done for you.

When full memory is fine, and when to worry

When your Mac needs more memory

If pressure is yellow or red most days with only the apps you always keep open, the Mac is short of memory for your work. Apple’s Check if your Mac needs more RAM guide, linked above, also shows whether memory can be added. Hold the Option key, choose Apple menu > System Information, click Memory under Hardware and look at Upgradeable Memory. On Apple silicon Macs, memory is integrated into the chip package; Apple’s Mac mini page says it “can’t be upgraded” (Apple: Mac mini memory). The practical options are fewer heavy apps at once, or more memory in your next Mac.

Where Orcylo fits

The hard part of freeing memory is knowing which app is to blame and whether it is growing. We make Orcylo, a menu bar system monitor for macOS 15 and later that counts each app’s helper processes into one row and keeps 30 days of per-minute history for every metric and the busiest apps. It notifies you when an app’s memory keeps growing or memory pressure turns critical. Its Smart Cleanup quits background apps holding a lot of memory, after one confirmation, which is step 2 done in one go rather than a cache purge. See the features and the pricing, or compare the best Activity Monitor alternatives and how it stacks up against Activity Monitor.

How we checked

Menu paths and Activity Monitor labels were checked against Apple’s macOS 26 Tahoe guides on October 1, 2026. We measured the swap and memory figures above the same day on a 16 GB Apple M4 Mac, with sysctl vm.swapusage and memory_pressure. Quotes from Apple, Google and the purge manual page went through a fact check against the pages they link to.