Find out what's actually using it

Before closing anything, spend thirty seconds seeing what's really going on — it's usually not what you'd guess.

1

Start with the big picture, not a hunch

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.

Open Overview — memory grouped by category (Browsers, AI Tools, Developer Tools, and more), heaviest first.
2

Too many browser tabs, especially media-heavy ones

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.

Install the browser extension (in Setup) to see memory by tab/site, not just "Chrome" as one big number.
3

Apps that quietly launch at login

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.

Check Who's heavy for anything you didn't realize was running, then remove it from System Settings → General → Login Items.
4

Chat, AI, and Electron-based apps run heavier than they look

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.

The AI Tools and Communication categories in Overview surface these directly, instead of them hiding among "everything else."
5

Background dev tools and services

Docker, local databases, node processes, simulators — these can balloon silently over a long coding session, with no window open to remind you they exist.

Check the Developer Tools category, or watch one specific process climb over time in Live Chart.
6

A slow leak looks nothing like a big spike

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.

Trends's "repeat offenders" list is built exactly for this — chronic weight over days and weeks, not a one-off.

Verify before you act

Closing an app on a hunch, only to find it wasn't the problem, wastes time. Measure instead of guessing.

7

Isolate one specific action

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?

Use Check one action: start, do the thing, stop. It reports the real delta for that specific window, nothing else.
8

Know when it's actually urgent

"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.

The floating widget turns red and forces itself open the moment your Mac has 5% or less free — see the pressure guide in Docs for what the levels mean.

General habits that help

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