If your Mac feels sluggish, Activity Monitor shows memory pressure creeping into the yellow or red, and you've started Googling "free up RAM on Mac" — you're in good company. The frustrating part is that most advice online either misunderstands how macOS manages memory or recommends steps that do nothing useful. This article explains what cached and inactive RAM actually means, whether flushing the memory cache is ever worth doing, and what genuinely reduces memory pressure on modern macOS.
How macOS Manages RAM (and Why "Used" Memory Isn't the Problem)
macOS uses a memory model designed to keep RAM as full as possible — because idle RAM is wasted RAM. When you quit an app, macOS doesn't immediately zero out those memory pages. Instead, it marks them as inactive: still holding the previous app's data, but available to be overwritten the instant any other process needs the space. If you relaunch that app quickly, macOS can restore it from inactive memory without reading from disk — which is dramatically faster.
This means a Mac with 16 GB of RAM showing "15.2 GB used" in Activity Monitor is almost certainly healthy. The number that actually matters is memory pressure, shown as a color-coded graph in Activity Monitor (Window > Memory tab). Green means the system is fine. Yellow means macOS is starting to compress memory. Red means it is actively swapping to disk — and that is when you notice real slowdowns.
The Four Memory Categories
- Wired: Locked in RAM by the kernel or certain apps. Cannot be freed.
- Active: In use right now by running processes.
- Inactive: Held from recently closed apps — available immediately to new processes.
- Compressed: macOS has compressed older pages to make room, without writing to disk yet.
The system automatically reclaims inactive memory the moment something needs it. You do not need to do this manually.
The purge Command: What It Does (and Why You Probably Shouldn't Use It)
The Terminal command most guides recommend is purge:
sudo purge
Running this forces macOS to flush the disk buffer cache and mark inactive memory pages as free. Your Activity Monitor will briefly show a dramatic drop in "used" memory. Then, within 30–60 seconds, macOS refills that memory as apps reload their data from disk — and your Mac feels slower during that refill window, not faster.
purge is a developer diagnostic tool, not a performance optimization. Apple ships it for testing how apps behave under low-memory conditions — not for everyday use. Using it on a working Mac is roughly equivalent to emptying your desk to prove you have a clean desk, then spending the next hour finding all your papers again.
When purge Is Legitimately Useful
- Reproducing a bug that only appears when memory is genuinely scarce.
- Benchmarking an app's cold-start performance.
- Developer testing on macOS Monterey (12) through macOS Sequoia 15 and beyond.
For anything else, skip it.
What Actually Reduces Memory Pressure on macOS
If your memory pressure graph is consistently yellow or red, here are the steps that genuinely help — in order of impact.
- Find and quit the memory hog. Open Activity Monitor (Applications > Utilities > Activity Monitor), click the Memory tab, and sort by "Memory" descending. The top process is your culprit. Common offenders: browsers with dozens of open tabs, Electron apps (Slack, VS Code, Figma), and virtual machines. Quit or restart the offending app.
- Reduce browser tab count. Each Chrome or Firefox tab runs its own process. 40 open tabs can consume 4–6 GB on their own. Use a tab suspension extension or close tabs you are not actively using. Safari is generally much more memory-efficient on Apple Silicon.
- Disable login items and background agents you don't use. Go to System Settings > General > Login Items & Extensions. Every background agent that loads at startup contributes to baseline memory usage. Remove anything you don't recognize or need.
- Restart the Mac. This genuinely clears all inactive and compressed memory, resets kernel caches, and gives you a clean baseline. If you rarely restart (leaving the Mac in sleep for weeks), a restart is the single most effective "RAM cleaner" available.
- Check for memory leaks. If one process's memory usage climbs continuously over hours without being released, that is a leak — usually a bug in a specific app. The fix is to quit and relaunch that app, or update it. Activity Monitor's memory column will show a process growing past what makes sense (e.g., a music app consuming 4 GB).
- Upgrade RAM if you consistently hit pressure. On Intel Macs, this may be straightforward. On Apple Silicon (M-series), RAM is unified memory and not user-upgradeable, so the long-term fix is buying a model with more memory.
RAM vs. Disk Cache: An Important Distinction
A lot of confusion in this space comes from conflating two different things:
| Term | Lives in | What it is | Safe to clear? |
|---|---|---|---|
| Inactive / cached RAM | Physical RAM | Recently used data held in memory, reclaimed automatically | macOS handles this — no action needed |
| Disk cache (app caches) | Your SSD / HDD | Files written to ~/Library/Caches and /Library/Caches by apps and the system |
Generally yes, but selectively |
| System Data / purgeable | Your SSD / HDD | Optimized Storage files, local Time Machine snapshots, temp files | Yes — macOS purges automatically or you can trigger it |
Clearing disk caches does not free RAM. It frees storage space. If your goal is more free disk space — especially when the Finder shows a large "System Data" category — that is a separate problem with separate solutions.
Clearing Disk Caches Manually
You can manually remove user-level caches from Terminal. Quit all apps first, then:
rm -rf ~/Library/Caches/*
Be aware: this is permanent. Some apps will rebuild their caches on next launch (which can make them feel slow temporarily), and a handful of apps store important data — not just caches — inside their ~/Library/Caches subfolder. If you are unsure what a specific folder contains, do not delete it blindly.
System-level caches at /Library/Caches require administrator privileges and are generally best left alone unless you have a specific reason to clear them. macOS manages these aggressively on its own.
If you want a safer, one-click approach to disk cache cleanup without manually navigating Library folders, Crumb handles system caches, user caches, logs, and temp files in a single pass — and its "Is this safe to delete?" feature lets you ask about any specific folder before committing. It also surfaces the largest space consumers on your disk so you know where to focus. Note that Crumb cleans disk space, not RAM — the distinction matters.
What to Check in Activity Monitor Right Now
- Open Activity Monitor from Spotlight (Cmd + Space, type "Activity Monitor").
- Click the Memory tab at the top.
- Look at the Memory Pressure graph at the bottom. Green = healthy. Yellow = watch it. Red = act now.
- If pressure is high, sort the process list by "Memory" column (click it) and identify the top consumer.
- Check Swap Used at the bottom. Any swap usage means macOS is writing memory pages to disk. On an SSD this is tolerable in bursts, but chronic swap use means you genuinely need more RAM for your workload.
Common Myths, Debunked
- "RAM cleaner apps free up memory." Most RAM cleaner utilities call
purgeor allocate a large block of memory to force macOS to flush caches — the same result as above: a brief drop followed by macOS refilling the memory. The cleaned memory returns within seconds. - "High RAM usage means something is wrong." Not on macOS. Full RAM that stays green on the pressure graph is the system working correctly.
- "Clearing disk cache = clearing RAM." These are entirely separate. Disk cache cleanup frees storage space, not memory.
- "More RAM always makes a Mac faster." Only if you are genuinely hitting memory pressure. If your pressure graph is consistently green, additional RAM won't change day-to-day performance.
Conclusion
To free up RAM on your Mac, skip the purge command and RAM cleaner apps — they don't do what they promise. Instead, watch the memory pressure graph in Activity Monitor, quit the apps consuming the most memory, and restart your Mac regularly. If you are also dealing with a full disk, that is a separate problem: clearing caches at ~/Library/Caches, removing large unused files, and cleaning up system logs will recover storage space. For a straightforward way to do that disk-side cleanup, download Crumb and let it handle the tedious part safely. RAM and disk space are different resources — but keeping both healthy means a consistently fast Mac.