How to Clean Mac Memory: Which Tabs and Apps to Close First
Searching for how to clean Mac memory usually follows a specific experience. The beachball appeared during something ordinary, Activity Monitor showed most of the RAM in use, and the obvious conclusion was that something needs emptying. That conclusion is half right. Something does need to change, but on macOS the amount of memory in use is a poor signal, and acting on it leads to work that makes the machine slower rather than faster.
What follows is how to read the numbers that do mean something, what to close and in what order, and how to keep the session from returning to the same state by Thursday.
Memory used is not the number to act on
macOS fills unused RAM on purpose. Apple's description of Cached Files states that the system caches files into unused memory to improve performance, and that until the memory is overwritten it remains cached, so it can help improve performance when an app is reopened. Empty RAM does no work. Full RAM with a healthy pressure reading is the design, not a symptom.
The figure that carries information is Memory Pressure, which Apple describes as a graphic representation of how efficiently memory is serving processing needs, determined by the amount of free memory, the swap rate, wired memory and file cached memory. Green means the demand is being met. Yellow and red mean it is not.
Two supporting figures explain why. Compressed is the amount of memory that has been compressed to make more RAM available, because when the machine approaches its maximum memory capacity, inactive apps in memory get compressed to leave room for active ones. Swap Used is the amount of space being used on the startup disk to swap unused files to and from RAM.
Compression is cheap and swap is expensive, so the pair to watch is Memory Pressure alongside Swap Used. A machine with 95 percent of its RAM in use, green pressure and almost no swap is working correctly. A machine with the same 95 percent, yellow pressure and swap climbing steadily has a real problem, and it is the same problem whether the RAM is 8GB or 64GB.
One more habit is worth dropping. Freeing memory so the number looks better guarantees the next few operations are slower, because whatever was purged has to be fetched again. The goal is not a lower number. It is a pressure reading that stays green during ordinary work.
Find what is holding the memory
Open Activity Monitor, click the Memory tab, and sort by the Memory column. Then read the list the way it is actually structured rather than row by row.
Browsers appear as many rows rather than one, because each site runs in its own process. The individual rows look modest and the group total is often the largest single item on the machine. Grouping by application, or simply adding up the rows that share a name, is the honest reading.
Three categories deserve attention, and they behave differently.
Long lived web applications are the common case. A chat workspace, a project board, a document, a design tool and a dashboard that stay open for days hold state continuously. Anything rendering on a timer, such as a call, a live spreadsheet or a map, never becomes inactive, which means macOS cannot compress it to make room. Compression only works on inactive pages.
Background helpers are the quiet case. Cloud drives, backup tools, VPN clients, printer software, updaters and menu bar utilities each hold a small amount of memory for the entire session and wake on their own timers. Individually none of them is worth attention. Fifteen of them together set the floor the session starts from.
A leaking process is the rare case and the easiest to identify. It grows steadily while nothing new is being asked of it, and the growth does not reverse when its window is closed. Leaving Activity Monitor open in a corner for an hour is enough to name one.
The order to close things in
Closing at random works eventually and teaches nothing. This order releases the most memory for the least disruption.
| Step | What to close | Why it is first |
|---|---|---|
| 1 | Web apps rendering continuously: calls, live boards, maps, streaming | Their memory cannot be compressed while they render |
| 2 | Duplicate sessions of the same service in different windows | Full cost per session, no benefit |
| 3 | Sites opened for a single lookup days ago | Highest ratio of memory to value |
| 4 | Applications not used today, including helper utilities | Steady floor, no immediate need |
| 5 | The single process identified as climbing while idle | Only a quit releases a leaked allocation |
Steps 1 through 3 usually account for most of the recovery, which is why they come before quitting anything a person actually uses.
Two actions do not belong on the list. Emptying browser caches frees very little RAM, since a cache on disk is not memory, and it slows the next hour of browsing. Running a utility that purges memory on demand produces a visibly lower figure and then a period of refetching, which is why the improvement so reliably feels temporary.
One action belongs on the list even though it is not about memory. Check free space on the startup disk, in System Settings under General, then Storage. macOS swaps to that disk, so a nearly full disk removes the room swap needs and turns a mild shortage into a stall. Apple's guidance for a slow Mac begins there: move files to another disk or an external storage device, delete what is no longer needed, and use the storage recommendations offered in Storage settings.
Memory and storage are two different problems
A large share of searches for how to clean Mac memory are actually about storage, and the two get treated as one thing because both are measured in gigabytes and both produce warnings.
Memory is RAM. It holds what is running right now, it is emptied every time the machine shuts down, and it is the resource Memory Pressure reports on. Storage is the startup disk. It holds files, applications and the system, it survives a restart, and it is the resource the message about the disk being almost full refers to. Deleting a folder of old video files frees storage and changes nothing about memory. Quitting an application frees memory and changes nothing about storage.
The two are connected at exactly one point, and it is the point that causes confusion. Swap lives on the startup disk. When RAM runs short, macOS writes inactive pages to the disk, so a disk with very little free space leaves swap nowhere to grow. That is why a machine can behave as though it is out of memory when the real shortage is disk space, and why freeing storage sometimes fixes what looked like a memory problem.
The practical consequence is a two part check rather than one. Read Memory Pressure for the memory side, and read free space in System Settings under General, then Storage for the disk side. If pressure is green and the disk is comfortable, nothing needs attention. If pressure is yellow and the disk is nearly full, fix the disk first, because doing so may resolve the memory symptom on its own and costs nothing.
Deciding whether the machine needs more memory
At some point the question stops being what to close and becomes whether the configuration fits the work. Apple silicon uses unified memory soldered at manufacture, so this cannot be revisited later on those machines, which makes the judgement worth making carefully rather than in a frustrated moment.
The measure is an ordinary day. Watch Memory Pressure across a normal afternoon, with the applications normally open and nothing exceptional running. Sustained yellow, with Swap Used climbing and adequate free disk space, means demand genuinely exceeds the installed memory. Pressure that only turns yellow when a video export, a virtual machine and a call happen at once means the machine is adequate and that afternoon was not typical.
Two conditions have to be ruled out before the reading can be trusted. A leaking process inflates demand artificially, so watch for a row that climbs while idle and quit it before judging anything. And a nearly full startup disk distorts the swap figure, so check storage first.
There is a middle answer that gets skipped between living with pressure and replacing hardware. It is worth asking how many live sessions the work genuinely requires simultaneously, as distinct from how many are open because closing them means signing back in later. A workload that truly needs eight web applications at once is a hardware question. A workload that has eight open because closing them felt expensive is a habit question, and it is the more common of the two.
Set the floor the session starts from
Everything above is recovery. The reason it has to be repeated is that the session rebuilds itself, and it rebuilds from a floor nobody chose.
That floor is in System Settings, under General, then Login Items and Extensions. Apple splits the panel in two. Open at Login holds apps, documents and server connections that open automatically at sign in. App Background Activity holds the entries allowed to perform tasks when the app is not open, such as checking for software updates or syncing data. The second group is where most accumulated helpers live, which is why they are rarely noticed.
Turn off anything belonging to an app not used weekly, and anything whose purpose is not identifiable from its name. Nothing is uninstalled by doing this and every entry can be turned back on, so being wrong costs one toggle. Then sign out and back in, and read the Memory tab before opening anything by hand. That reading is the machine's floor, and if it is already high, every session starts worse than the hardware requires.
Browser extensions deserve the same treatment for the same reason. They load per site rather than once, so a dozen extensions multiply the cost of every open page. Removing the four that are never used changes the arithmetic across the whole session.
The structural version of this is to stop treating tabs as free. When each web app lives in its own window, the cost of keeping it open is visible and the thing being closed is an app rather than an anonymous tab. That is the premise behind Features, and organising those windows by the work at hand rather than by service is what Workspaces sets out. Which services run correctly when isolated this way is listed on Supported apps.
What to change first
Read Memory Pressure and Swap Used during ordinary work, not during a bad moment, and check free space on the startup disk. If pressure is green, nothing needs cleaning regardless of how much RAM is in use.
If pressure stays yellow because a dozen web apps never close, the durable change is how those apps are kept open, which is what SpaceDeck addresses. The Pricing page settles whether that is worth the step.
Frequently asked questions
Is it bad if almost all of the RAM shows as used?
No, on its own. macOS caches files into unused memory deliberately, and Apple notes that the memory stays cached so it can improve performance when an app is reopened. High usage with green memory pressure and little swap is the system working as designed. The combination to worry about is yellow or red pressure with Swap Used climbing during ordinary work.
Do memory cleaner apps for Mac actually work?
They do what they say, which is release cached memory so the reported figure drops. Whether the machine is faster afterwards is a different question, because anything purged has to be fetched again over the following minutes. For a machine under real pressure, closing continuously rendering web apps, auditing login items and freeing disk space change the outcome more than any release does.
Is there a command to free up memory on a Mac?
Older guides mention a purge command, and it does force cached memory to be released. The result is the same as any other purge: a lower number for a short while, then slower operation as the caches refill. It does not address why pressure was high, so the effect is cosmetic in exactly the cases where the machine needed help.
Does restarting clear Mac memory?
Yes, and it is the right move in two situations: after a process has leaked, since a leaked allocation is only released when the process ends, and when the machine is too unresponsive to close things individually. As a routine it is weak, because the same session gets rebuilt within hours and the floor set by login items is unchanged.
Does closing tabs free more memory than closing apps?
Often, yes. A browser runs each site in its own process and extensions load per site, so the group total for one browser with forty open sites frequently exceeds any single native application. Pages that render continuously, such as calls and live documents, matter most, because their memory never becomes inactive and therefore cannot be compressed.