Task Manager on a Mac: where it is and how to open it

The quickest way to open Activity Monitor is Spotlight: press Cmd+Space, type "Activity Monitor", and press Return. That works from anywhere and is the route I use every time. If you would rather click, open your Applications folder, go into the Utilities folder inside it, and double-click Activity Monitor. From Finder you can also choose Go in the menu bar, then Utilities, and find it there.

If you check it often, keep it one click away. Once Activity Monitor is open, its icon sits in the Dock. Right-click that icon, go to Options, and choose Keep in Dock, and it stays there after you quit so you can launch it instantly next time. That is the closest you get to a permanent Task Manager button on a Mac.

There is no single default keyboard shortcut that opens Activity Monitor, so the honest answer to "task manager shortcut on Mac" is that one doesn't ship with macOS. Windows has Ctrl+Shift+Esc for Task Manager; macOS has no equivalent baked in for Activity Monitor. The closest built-in shortcut is Cmd+Option+Esc, but that opens the Force Quit window, not Activity Monitor, which is a different tool covered in the next section.

You can make your own shortcut if you want one. Open System Settings, go to Keyboard, then Keyboard Shortcuts, choose App Shortcuts, and add a shortcut for the menu command you want. For day-to-day use, though, Spotlight is fast enough that most people never bother: Cmd+Space then a few letters of "Activity Monitor" gets you there in under a second.

The Mac answer to Ctrl+Alt+Del is Cmd+Option+Esc, which opens the Force Quit window. On Windows, Ctrl+Alt+Del is what you press when an app has frozen and you need to kill it; Cmd+Option+Esc does that job on a Mac. The window lists your running apps, with anything stuck marked "not responding". Select the frozen app and click Force Quit, and macOS closes it immediately so you can reopen it clean.

There are two other ways to force quit a single app. Hold Option, then click and hold the app's icon in the Dock, and Force Quit appears in the menu. Or open Activity Monitor, select the process, click the X button in the toolbar, and choose Force Quit. All three skip the normal save-and-close, so they are for frozen apps rather than everyday quitting. The one thing Cmd+Option+Esc doesn't do is show you what is using your CPU or memory, which is the other half of what Windows users reach for, and that is what Activity Monitor is for.

Most people search for Task Manager on a Mac because the machine has gotten hot, the fan is loud, or it feels slow, and they want to see what is responsible. Activity Monitor is exactly the right tool for that. Open it, click the CPU column header to sort by CPU use, and read the top of the list. A browser tab gone wrong, a sync client stuck retrying, a video call doing too much, or an app caught in a loop can sit at a high percentage indefinitely with nothing obvious on screen, and while it does, it pins the chip and heats it up.

Quit your own apps and tabs first, not unfamiliar system processes. If you see something called kernel_task high in the list, leave it alone: that is macOS deliberately taking cycles to hold heat down, a symptom of the heat rather than the cause, and it can't be force quit. Reading the CPU column is its own small skill, so I have written a separate guide on how to check CPU usage on a Mac that goes through what each number means and which processes are safe to quit. Once you find the culprit and quit it, the chip usually cools within a minute or two and the fan settles.

Sometimes the busy process is meant to be busy. After a macOS update it is normal for Spotlight to reindex your drive or Photos to analyze your library, which loads the chip hard for a stretch and then stops on its own, often within an hour or so. A Time Machine backup does the same. If the process at the top of the list is one of those, let it finish rather than forcing it to quit.

And sometimes the Mac runs hot even though the process list is clean. Heat traps under a soft surface, in blocked vents, or in a warm room raise the temperature the chip starts from, so the fan ramps and the machine warms with no single app to blame. For the full set of heat causes, why your Mac gets so hot goes through each one, and how to fix an overheating Mac walks the cooling steps in order. If the Mac feels slow at the same time, the heat and the lag are usually the same event, which I cover in why a MacBook runs slow and hot.

Activity Monitor shows you what is using the chip, but it doesn't show the chip's temperature and it can't touch the fans. macOS has no built-in temperature readout and no built-in fan control, so even once you have found the heavy process, the machine gives you no number to watch and no way to make the fans react sooner. To see the actual temperature you need a separate tool, which I cover in the guide on checking your Mac's temperature, with checking CPU usage as the companion for the load side.

If the fan keeps roaring even after the CPU list looks calm, that is a different question, and why your Mac fan keeps running covers it. When the chip is hot enough for long enough, macOS also down-clocks it on purpose to shed heat, which is thermal throttling on a Mac, and it is the link between a hot chip and a slow one.

Activity Monitor is the right first move: find the runaway process, quit it, and the heat usually goes with it. But if the process list stays clean and the Mac still runs hot under normal work, the issue is often that macOS lets heat build before it ramps the fans, so the chip warms up while the fans are still spinning up slowly. There is no slider in System Settings and no supported Terminal command to make them react earlier, so on stock macOS you are at the mercy of the curve.

That gap is what I built ChillBlades for. With Auto Boost, every Auto fan spins up when the hottest sensor reaches a band you pick, then eases off once it falls back below it, so the fans get ahead of the heat instead of trailing it. You can also set a fan to a fixed speed with a slider that runs only across that fan's real hardware range, clamped so you can't push it past its rated maximum or stop it dead. It can't cool a chip below what the fans can physically move, and your Mac protects itself regardless, but for heat that builds because the fans react late, getting them moving earlier is the lever. The moment you quit ChillBlades, every fan goes straight back to macOS automatic control. A raised fan is also louder, so before you reach for software it is worth knowing whether a hardware aid helps, which is why I tested whether cooling pads work for a MacBook.

I make ChillBlades, a Mac fan control app, and I write these guides, so I spend a lot of time helping people who came to a Mac from Windows and went looking for Task Manager. I have kept this honest rather than promotional: Activity Monitor and the Force Quit window are free, built into macOS, and solve the actual question, which is finding and killing whatever is heating or slowing your Mac. A fan app only matters in the narrower case where the heat builds because macOS reacts to it late. Apple does not publish its fan curves or show a temperature anywhere in the system, so treat this as practical guidance from working with the hardware, not a spec sheet. The ChillBlades behavior described here runs on M1 through M5 and Intel Macs with fans, on macOS 13 and later; the base fanless MacBook Air has no fan to control, so it can only throttle to cool down.