Generic "close some apps" advice doesn't tell you which apps, or whether it'll actually help. Here's what really tends to eat memory, and exactly how to check each one for yourself.
Before closing anything, spend thirty seconds seeing what's really going on — it's usually not what you'd guess.
Most people assume it's "probably Chrome" or "probably that one app" — sometimes right, often not. Look at what's actually using memory before deciding what to close.
Browsers are almost always the single biggest category on any Mac. Every tab is its own process; video calls, embedded video, and single-page apps left open for days are the worst offenders. Closing tabs you're not using is usually the single highest-impact thing you can do.
Apps set to open automatically add up in the background without you ever deciding to open them today. Some are worth it; a lot accumulate over months of "just in case" installs.
Slack, Discord, ChatGPT's desktop app, VS Code, and similar apps are often full embedded browsers under the hood — a small window can still mean a genuinely large memory footprint.
Docker, local databases, node processes, simulators — these can balloon silently over a long coding session, with no window open to remind you they exist.
An app that jumps once isn't the same problem as an app that's a little heavier every single day. The second one is worth actually fixing — restarting it, updating it, or replacing it.
Closing an app on a hunch, only to find it wasn't the problem, wastes time. Measure instead of guessing.
Curious whether opening that huge spreadsheet, starting a video call, or exporting a project is really what's costing you memory — separate from everything else that happens to be running?
"Lots of memory used" and "your Mac is struggling" aren't the same thing — macOS caches aggressively on purpose. What matters is memory pressure, not the raw number.
Not specific to any tool — just genuinely useful, in order of how much they usually matter.
Not sure what's actually running on your Mac right now?
Download Memory Story