How to Free Up RAM on a Mac (What Actually Works)

There is a whole category of apps that promise to free up RAM on your Mac, and they all work the same way: they force macOS to throw away cached data so the “free memory” number goes up. It does go up. Your Mac then gets slower while it rebuilds the cache. Here's what actually reduces memory use, and why the number everyone watches is the wrong one.

First: the free-memory number is not the goal

macOS fills unused RAM with cached files because unused RAM is wasted RAM. That cache is discarded instantly when an app needs the space, so a Mac showing very little free memory is behaving correctly. The number worth watching is Memory Pressure, in Activity Monitor's Memory tab — green means you're fine regardless of what “free” says. Here's how to read it.

So the real goal isn't to free memory. It's to need less of it, so pressure stays green and macOS never has to swap to disk.

1. Find out what's actually holding it

1. Open Activity Monitor (/Applications/Utilities).
2. Click the Memory tab.
3. Click the Memory column header to sort highest-first.

Look at the top five. On most Macs it's a browser, then whatever creative or development tool is open, then a sync client. If one process holds an implausible amount — 20 GB for a text editor — that's a leak, not a capacity problem. Quit and relaunch it and the memory comes back. More on reading Activity Monitor properly.

2. Close browser tabs — the specific ones

The browser is nearly always the largest consumer, and it's rarely the tab count that matters. Ten text articles cost almost nothing; one document editor, one video call, and one dashboard with live charts can cost several gigabytes between them.

• Chrome and Edge: Window → Task Manager lists memory per tab and per extension. Sort by memory footprint and close the offenders.
• Safari: Activity Monitor lists individual Safari web-content processes; hover to see which page each belongs to. Safari also unloads background tabs on its own, so it usually costs less than Chrome for the same pages.
• Extensions count too. Each one runs in its own process. An ad blocker on a hundred open tabs is a hundred instances of it.

3. Quit apps instead of minimising them

Closing a window is not quitting an app — on macOS the app keeps running, and keeps its memory, until you press ⌘ + Q. Minimising to the Dock is the same. For lightweight apps this doesn't matter; for design, video, virtualisation and IDE tools it's the difference between green and yellow pressure. If you tend to leave everything running, quitting them all at once from the Dock is a fast reset.

4. Restart — genuinely, not as a joke

A restart clears the swap file, resets processes that have leaked slowly over days of uptime, and releases memory held by apps that crashed badly. If your Mac has been awake for three weeks, this is the highest-value thing on the page and takes ninety seconds.

One detail worth changing first: if macOS reopens every app and window you had open, you'll be back where you started before you've touched anything. Turn off reopening windows and restarts actually give you a clean slate.

5. Cut what loads without being asked

Background helpers hold memory all day for features most people never use.

1. Open System Settings → General → Login Items (Login Items & Extensions on macOS 15 Sequoia and later).
2. Remove anything under Open at Login you don't need immediately.
3. Go through Allow in the Background and switch off updaters and helpers for apps you rarely open. You can re-enable any of them.

See managing startup items for the older locations these can hide in.

What doesn't work

• Memory cleaner apps. They call the same mechanism as purge: drop the file cache, watch the free number rise, then pay for it as everything reloads from disk.
• sudo purge. Built into macOS, and it does exactly what it says — which is a testing tool, not a tune-up. Running it makes the next few minutes slower.
• Clearing disk caches. Different thing entirely. Deleting files in ~/Library/Caches has no effect on RAM. See when clearing caches is actually appropriate.
• Disabling swap. Sometimes suggested in forums; it removes macOS's safety valve and makes low-memory situations fail hard instead of slowly.

When the answer is more memory

If pressure sits yellow or red during ordinary work after all of the above, you're simply short of RAM. On Apple silicon it's part of the chip and can't be upgraded — the only fix is a different Mac, so it's worth knowing before you spend a weekend tuning. Many Intel Macs from 2012–2015 do have replaceable memory, which makes a 8 GB to 16 GB upgrade the cheapest real speed-up available; see speeding up an old MacBook.

The settings-level fixes above are one-click, reversible toggles in Mainspring — labelled in plain English, with an undo button for every one.

Common questions

Does closing apps free RAM on a Mac?

Yes, quitting an app with Command-Q releases its memory. Closing its window or minimising it does not: the app keeps running and keeps its allocation until you quit it.

Should I use a RAM cleaner app on my Mac?

No. They free cached memory macOS would have released automatically the moment it was needed, so the only lasting effect is a slower few minutes while the cache rebuilds.

Why does my Mac use so much memory when I have nothing open?

macOS caches files in otherwise-idle RAM, and background helpers from installed apps hold memory too. If memory pressure is green, this is normal. If it is not, sort Activity Monitor's Memory tab to find the process responsible.

Does restarting free up RAM?

Yes, and it also clears the swap file and resets processes that have leaked memory over long uptime. It is the most reliable single step if your Mac has been running for weeks.

Is 8 GB of RAM enough for a Mac?

For browsing, mail, and documents, yes, though you will see swap once several apps are open at once. For design, video, virtualisation or development work, 16 GB or more avoids constant swapping.