Kitsmith / Guides / Task Manager on Mac
Mac Task Manager: it’s called Activity Monitor
Checked against Apple’s own Activity Monitor and Force Quit documentation, August 2026.
macOS doesn’t have an app named “Task Manager” — that’s Windows. The direct equivalent is Activity Monitor, and it’s already on your Mac: open Finder, go to Applications → Utilities → Activity Monitor, or press ⌘Space and type its name.
If all you actually need is to close something that’s frozen, you don’t need to open Activity Monitor at all. Press ⌥⌘Esc (Option-Command-Escape) for the short version: a Force Quit window with nothing else in it.
What Activity Monitor actually shows you
Five tabs across the top, each one a different way of asking “what is my Mac busy doing?”
- CPU — which processes are using the processor right now, and how much of it.
- Memory — how much RAM is in use, and by what.
- Energy — which apps have used the most power recently, useful for chasing down what’s draining a laptop battery.
- Disk — how much each process is reading from and writing to storage.
- Network — data sent and received, per process.
Click any column heading to sort by it — sorting the CPU tab by “% CPU” is the fastest way to see what’s actually busy.
How to force-quit something properly
Two ways to get there, same result:
- Press ⌥⌘Esc, or choose Force Quit… from the Apple menu. A Force Quit window opens listing what’s running — select the stuck app and click Force Quit. If the Finder itself is the problem, select it here and click Relaunch instead.
- From inside Activity Monitor: select the process in the list (an unresponsive one is marked “(Not Responding)” and shown in red), click the stop icon at the top-left of the window, then choose Quit to ask it to close normally, or Force Quit to close it immediately.
Quit gives the process a chance to save what it’s doing first, and can refuse if that would lose data. Force Quit doesn’t ask — use it when Quit hasn’t worked, not as the first move.
Reading %CPU and memory without panicking
A process pegged at high CPU isn’t automatically a problem — exporting a video, compressing a big folder, or Spotlight re-indexing after a large file move all run hot on purpose, then settle back down. What’s worth investigating is something sitting at high usage with no reason it should be busy, or something you don’t recognize at all. The Energy tab is the faster read if the actual question is “what’s draining my battery,” rather than CPU’s raw processor-time view.
Actually looking for a to-do app?
If you searched “task manager” hoping for somewhere to track a list of things to do, that’s a different job — a task manager in the to-do-list sense, not the process-monitoring sense Activity Monitor covers. We don’t have a dedicated to-do app roundup live on Kitsmith yet — we haven’t hand-verified enough of them to publish one, and an empty-feeling page isn’t the honest version of this site. macOS already includes a free Reminders app (Applications → Reminders) that covers the basics in the meantime. Otherwise, browse everything we’ve verified so far — or check back once a to-do section clears our publishing bar.
Task Manager on Mac — questions people ask
Is there a Mac equivalent of Ctrl+Alt+Delete?
The closest is ⌥⌘Esc (Option-Command-Escape), which jumps straight to the Force Quit Applications window — a short list of what’s running and a button to close the one that’s stuck. It skips past Activity Monitor’s full detail on purpose.
What does "Not Responding" mean in Activity Monitor?
Apple marks an unresponsive process with “(Not Responding)” next to its name and shows it in red — that’s the one to force-quit, not just whichever app you clicked by mistake.
Does closing Activity Monitor quit the apps it’s showing?
No. It’s only a window onto what’s already running — closing it has no effect on any process it was displaying.
What’s the difference between Quit and Force Quit inside Activity Monitor?
Quit asks the process to close itself, same as choosing Quit from its own menu — it can save your work first, and it can refuse if closing would lose data. Force Quit closes it immediately regardless, which is where unsaved changes go.