The first time my MacBook started sounding like a jet engine for no obvious reason, I had no idea Activity Monitor even existed — I just force-quit random apps until the fan calmed down. Turns out there’s a much less chaotic way to do this. Here’s how to use Activity Monitor on MacBook to actually diagnose what’s eating your CPU, memory, disk, or battery instead of guessing.
Quick Answer
- Open Activity Monitor via Spotlight (Cmd+Space, type “Activity Monitor”) or Applications > Utilities.
- Five tabs: CPU, Memory, Energy, Disk, Network — each shows a different resource.
- High CPU usage from one process is usually the cause of fan noise and lag.
- Memory Pressure (green/yellow/red) in the Memory tab tells you if you’re actually low on RAM.
- Double-click any process for more detail, or select it and click the X button to force quit.
What Each Tab Actually Shows You
CPU tab. Shows every running process and how much processor time it’s using, both per-process and as a system-wide percentage at the bottom. If your Mac is running hot or the fans are loud, this is almost always where you’ll find the culprit — sort by the “% CPU” column by clicking the header, and whatever’s at the top is your suspect.
Memory tab. This one confuses people because the numbers alone don’t tell the whole story. What actually matters is the Memory Pressure graph at the bottom — green means you’re fine, yellow means things are getting tight, red means you’re actively short on RAM and macOS is compensating with swap (writing memory to disk, which is slower).
Energy tab. Shows which apps are draining your battery the fastest, both currently and cumulatively over the last 8 hours or 7 days depending on the dropdown. Handy for figuring out why your battery life tanked out of nowhere.
Disk tab. Shows read/write activity per process. Useful for catching an app that’s hammering your SSD with constant writes, which can happen with some backup tools or misbehaving apps stuck in a loop.
Network tab. Shows data sent/received per process. Good for spotting an app quietly uploading or downloading way more than it should be.
Step-by-Step: Diagnosing a Slow or Hot MacBook
Step 1: Open Activity Monitor
Cmd+Space, type “Activity Monitor,” hit Enter. Or navigate to Applications > Utilities > Activity Monitor.
Step 2: Click the CPU tab
This is your starting point for almost any “why is my Mac slow/loud/hot” situation.
Step 3: Sort by % CPU
Click the “% CPU” column header once to sort highest-to-lowest. Whatever’s sitting at the top using an unusually high percentage — anything sustained above 80-100% for a single process when you’re not doing anything demanding — is worth investigating.
Step 4: Identify the process
Some names are obvious (Chrome, Photoshop). Others aren’t — things like “kernel_task,” “WindowServer,” or “mds_stores” are all legitimate system processes that occasionally spike for their own reasons, not necessarily something wrong.
Step 5: Decide whether to quit it
Select the process and click the X (Force Quit) button in the toolbar if it’s a regular app that’s misbehaving. Be more careful with system processes — quitting the wrong one can cause more disruption than the original problem.
Step 6: Check Memory Pressure if the issue feels more like general sluggishness than one specific spike
Switch to the Memory tab and look at the color-coded graph at the bottom. Yellow or red means you genuinely need to close things or you’re low on RAM for your workload — not just a perception issue.
Common Scenarios and What They Usually Mean
kernel_task using a lot of CPU: This one throws people off constantly because it looks alarming but it’s often not actually doing real work — kernel_task sometimes ramps up specifically to slow down other processes and help manage heat when your Mac is running warm. It’s more of a symptom than a cause in a lot of cases.
WindowServer eating CPU: This handles all the visual rendering of your screen. High usage here often points to too many overlapping windows, external display scaling issues, or GPU-intensive visual effects rather than any single app being the direct problem.
A browser using way more memory than expected: Chrome specifically is notorious for this — each tab and extension effectively runs as its own semi-independent process, so a dozen tabs can genuinely use gigabytes without anything being “broken.”
mds_stores or mdworker spiking after connecting external storage: This is Spotlight indexing a newly connected drive. It’s temporary and resolves on its own once indexing finishes, usually within a few minutes for smaller drives.
What Actually Worked For Me
That fan-noise situation I mentioned — I eventually opened Activity Monitor properly instead of guessing, and Photos was sitting at the top of the CPU tab using something like 150% (yes, it can go over 100% since it’s spread across cores). I hadn’t even opened Photos recently.
Turned out it was quietly reprocessing my entire library in the background after I’d imported a big batch of photos from my phone a few days earlier and just closed the app without thinking about it further. It wasn’t actually a problem exactly, just an unexpectedly long background task I didn’t know was still running.
My first move, before I understood what was happening, was to force-quit it assuming that would fix things. It did quiet the fans temporarily, but Photos just picked the exact same background processing back up the next time I opened it, so the “fix” wasn’t really a fix — more just a pause. What actually resolved it was leaving it alone and letting it finish overnight, which took a few hours longer than I expected given how big the import batch was.
Advanced Fixes and Edge Cases
Sampling a process for deeper diagnosis: Select a process in Activity Monitor, then go to the gear icon (or right-click) and choose “Sample Process.” This generates a more detailed technical snapshot of what that process is doing internally — mostly useful if you’re trying to report a bug to a developer or genuinely dig into something unusual, less useful for casual troubleshooting.
Checking swap usage specifically: In the Memory tab, look at “Swap Used” in the bottom summary. A small amount of swap use is completely normal and not a red flag by itself. Consistently high or rapidly growing swap alongside red Memory Pressure is the actual warning sign, not swap existing at all.
Distinguishing a runaway process from a stuck one: A process pegged at a high, stable CPU percentage for a long stretch with no change is usually stuck in a loop and safe to force quit. A process that spikes, drops, spikes again in a pattern is more likely doing legitimate periodic work.
Using Terminal alongside Activity Monitor: top -o cpu in Terminal gives a live, text-based version of the same CPU data, updating in real time — sometimes faster to glance at than switching windows if you’re already in Terminal for other reasons.
Prevention Tips
- Check Activity Monitor occasionally even when nothing seems wrong, just to get a baseline sense of what “normal” looks like on your specific Mac.
- Don’t force-quit system processes you don’t recognize without looking them up first — some are essential and quitting them can cause more issues than they solve.
- If Memory Pressure regularly sits in yellow during normal daily use, that’s a sign your RAM amount is genuinely tight for your workload, not just something to tune away.
- Restart occasionally rather than just sleeping the Mac for weeks straight — accumulated background processes and memory leaks in long-running apps tend to clear up with a fresh restart.
FAQ
Why does CPU usage show over 100% for one process? Because Activity Monitor’s percentage is per-core, not total. A process using multiple cores can show 200%, 300%, or more depending on how many cores your Mac has.
Is it safe to force quit anything in Activity Monitor? For regular apps, yes, generally safe. For processes with names you don’t recognize, look them up first — some are core system functions that shouldn’t be interrupted casually.
What’s a normal amount of memory pressure? Green is normal and healthy. Occasional brief yellow during heavy multitasking isn’t alarming. Frequent or sustained red means you’re consistently running short on RAM.
Does Activity Monitor slow down my Mac by running? Negligibly — it’s a lightweight system utility, not something that adds meaningful overhead just by being open.
Why do I see multiple processes with the same app name? Common with browsers and Electron-based apps (Slack, Discord, VS Code) — they split work across multiple background helper processes rather than running as one single process.
Editor’s Opinion
activity monitor is one of those tools people ignore until somethings already wrong, which is kinda backwards honestly. i wish id started checking it casually way earlier instead of treating force quit as my only troubleshooting move for years. kernel_task looking scary but usually being fine is probably the biggest “gotcha” in there for most people, worth knowing before you panic over it.