Does closing apps free RAM on Mac?

Yes, but less than you'd hope, and only if you actually quit. Clicking the red X just hides the window. The app stays loaded in memory, ready and waiting. Quitting really does free RAM, but macOS keeps some of it compressed for a quick relaunch, so the numbers don't always drop the way you'd expect. Here's the full picture.

This question comes up constantly. You have a dozen apps open, your Mac feels sluggish, you close a few windows, and nothing changes. It feels like it should help. The frustrating truth is that on macOS, closing a window and quitting an app are two very different things.

Shiny is a small menu-bar tool for managing memory pressure, which means a lot of attention has gone into how macOS actually handles RAM (the temporary workspace your Mac uses to hold what's running). The conventional wisdom is half right; understanding the other half makes a noticeable difference.

What's the actual difference between closing and quitting?

On macOS, clicking the red circle in the top-left corner of a window closes that window. The window disappears. But the app itself remains running in the background, loaded in memory, waiting for you to open a new window or bring it back.

This catches people who switch from Windows, where closing the last window usually exits the program. On Mac, you'll often notice a small dot under the app's Dock icon even after the window is gone. That dot means the app is still running.

To actually quit an app and free its memory, you have two options: press Command-Q while the app is in the foreground, or right-click the app's Dock icon and choose Quit. Either way, the app exits and its memory is released back to the system.

If you've been clicking the red X and wondering why your Mac never feels faster, this is likely why.

Why doesn't quitting an app free all its memory?

Here's where things get a little counterintuitive. You quit an app, open Activity Monitor (press Command-Space and type "Activity Monitor"), click the Memory tab, and notice that "Memory Used" hasn't dropped much. What's going on?

macOS has a philosophy: unused RAM is wasted RAM. Rather than immediately wiping the memory an app was using, macOS often compresses it and keeps it around for a while. The idea is that if you relaunch the same app in the next few minutes, it can restart much faster from that compressed state than if it had to load everything from scratch.

This is a sensible design. It makes your Mac feel snappier day-to-day. But it means "Memory Used" in Activity Monitor can stay deceptively high even after you've quit several apps.

The number to watch instead is the Memory Pressure graph at the bottom of the Memory tab. Pressure is the honest signal. It tells you whether your system is actively struggling to find enough RAM, not just how much happens to be allocated at any given moment. What memory pressure actually means is covered in detail in a separate post if you want to go deeper.

"Unused RAM is wasted RAM. That's macOS's philosophy, and it's why quitting apps doesn't always produce the dramatic drop in Memory Used you might expect."

When does quitting apps actually help?

Quitting apps makes a real, meaningful difference in two situations.

When an app has a memory leak. Some apps gradually consume more and more memory the longer they run, a problem developers call a memory leak. The app keeps asking for more RAM and never gives it back. Common offenders include Chrome with many tabs open, Slack after a full day of use, Microsoft Teams, and occasionally Photoshop or Lightroom during a long session. Quitting one of these and relaunching it can free a significant chunk of RAM and noticeably reduce memory pressure. If your Mac slows down over the course of a day but feels fine after a restart, a leaky app is the likely culprit. See the guide on how to free up RAM on Mac for a step-by-step approach.

When you've opened more apps than your Mac has RAM to comfortably hold. If you're running a video editor, a browser with 20 tabs, and a design tool all at once on a Mac with 8 GB of RAM, you will hit genuine memory pressure. Quitting one of those apps frees its active memory and eases the pressure. In this case, the Memory Pressure graph will shift from yellow or red toward green, which is a real improvement you'll feel.

For everything else, moderate RAM use with green pressure, quitting apps is optional. macOS manages the situation fine without your help.

What works better than closing apps?

If your goal is a faster Mac, here are the things that make a more reliable difference than closing windows:

Restart occasionally. A weekly restart clears compressed memory, resets leaky apps, and gives macOS a clean slate. It's the most effective single thing most people can do.

Watch Memory Pressure, not Memory Used. Open Activity Monitor and look at the Memory tab. If the pressure graph is consistently green, your Mac's memory situation is fine, even if "Memory Used" looks high. How to use Activity Monitor on Mac walks through what each reading actually means.

Identify the leaky app. If pressure goes yellow or red during the day, sort the app list in Activity Monitor by "Memory" to find which app is using the most. Quitting that specific app is more effective than closing a dozen unrelated windows.

Reduce browser tabs. Browsers are the single biggest consumers of RAM on most people's Macs. Each tab is essentially a small running program. Keeping 5 tabs open instead of 50 makes a bigger difference than quitting most other apps.

Apple's own documentation on checking whether your Mac needs more RAM is a useful reference if you want to go further with Activity Monitor.

Should I quit apps every day?

It depends on which apps and how your Mac is coping.

If your memory pressure graph stays green throughout the day, there's no need to make a ritual of quitting apps. macOS is handling things. Let it.

If pressure goes yellow or red by mid-afternoon, it's worth identifying which app is responsible (Activity Monitor, sorted by memory, will tell you) and quitting it. That's a more targeted approach than blanket-quitting everything and is less disruptive to your workflow.

The one habit that is genuinely worth building: quit Chrome, Slack, Teams, or any other known memory-leaker at the end of the day, or at least restart them in the morning. These apps don't get better with time. The longer they run, the more memory they tend to hold.

If you find yourself doing this check repeatedly throughout the day and wish something could handle it more quietly, that's the gap a tool like Shiny fills. It sits in your menu bar, shows you pressure at a glance, and frees memory in one click when things get tight. You can read more about how that compares to the broader category of Mac cleaners if you're trying to decide what's worth paying for.

Bottom line

Closing a window with the red X does not free RAM on Mac. The app keeps running.

Quitting an app (Command-Q, or right-click the Dock icon and choose Quit) does free its active memory. The drop in "Memory Used" might be smaller than expected because macOS compresses recently-used memory for faster relaunches, but the improvement is real.

The most useful thing to watch is the Memory Pressure graph in Activity Monitor, not "Memory Used". Green pressure means your Mac is fine. Yellow or red means something is genuinely competing for RAM, and that's when quitting the right app will make a noticeable difference.

For most people, the bigger wins come from restarting weekly, reducing browser tabs, and quitting known memory-leakers like Chrome and Slack at the end of the day. If you want a broader explanation of what makes Macs slow, that post covers the other common causes beyond memory.

Common follow-up questions

Does quitting an app really free up RAM?
Yes, quitting an app frees the RAM (the temporary workspace your Mac uses to hold what's running) it was actively using. The caveat is that macOS sometimes keeps a compressed version of recently-used apps in memory so they relaunch faster, so the drop in "Memory Used" inside Activity Monitor may be smaller than you'd expect. What matters more is the Memory Pressure graph: if it shifts from yellow or red toward green after quitting an app, you've genuinely helped your Mac.
Why is my Mac still slow after closing apps?
Closing a window with the red X button does not quit the app on Mac. The app stays loaded in memory. To actually free that memory, you need to quit the app: press Command-Q while the app is active, or right-click its Dock icon and choose Quit. If you've already done that and your Mac is still slow, check the Memory Pressure graph in Activity Monitor. If pressure is green, the slowness probably has another cause. If it's yellow or red, you may need to quit more apps or add more RAM.
Is it bad to leave many apps open on Mac?
Not by itself. macOS is designed to handle multiple open apps and manages memory automatically. The problem arises with apps that gradually consume more and more memory the longer they run (sometimes called memory leaks). Chrome with many tabs, Slack after hours of use, and Microsoft Teams are common examples. If you notice your Mac slowing down over the course of a day, one of your long-running apps may be the culprit.
Should I quit Safari every night?
You don't have to, but it can help if Safari has accumulated dozens of tabs. Safari is generally well-behaved about memory, but any browser with a large number of tabs will use significant RAM. Quitting and relaunching Safari clears out inactive tab memory and often feels like a reset. If your Mac's memory pressure is consistently green, there's no need to bother. If you're often hitting yellow or red pressure, closing unused tabs or quitting Safari overnight is a reasonable habit.
How do I tell if quitting an app actually freed memory?
Open Activity Monitor (press Command-Space and type Activity Monitor), then click the Memory tab. Look at the Memory Pressure graph at the bottom. Quit the app you want to test and watch the graph over the next 30 to 60 seconds. If pressure eases from yellow or red toward green, the quit made a meaningful difference. "Memory Used" at the top of the window is less reliable for this check because macOS keeps compressed memory around; pressure is the honest signal.