How to monitor CPU temperature on a Mac
macOS has no built-in CPU temperature readout. Here's how to check it on Apple silicon with powermetrics, what's a normal range, and why the process running hot matters more than the number.
macOS doesn't show CPU temperature anywhere in its standard interface: not in Activity Monitor, not in the menu bar. To see the actual sensor values you need Terminal or a third-party app. Here's how to read them on Apple silicon, what the numbers mean, and why the temperature is rarely the thing worth chasing.
macOS hides the temperature on purpose
Activity Monitor shows CPU load and energy impact, but no degrees. Apple's view is that thermals are the system's job, not yours: macOS manages heat automatically by throttling the CPU and spinning up fans, so it never surfaces a number that would only make people anxious. That's reasonable, but it also means when your Mac is hot and loud, you can't see what's actually happening without extra tools.
Check it in Terminal (no install)
On Apple silicon, powermetrics reads the same on-board SMC sensors a monitoring app would. It needs sudo because it touches low-level hardware counters:
sudo powermetrics --samplers smc -i1 -n1
--samplers smc: read the System Management Controller (temperature and fans)-i1samples once;-n1takes a single reading, then exits
You'll see a CPU die temperature and, on Macs with fans, the current fan RPM. For a live view that refreshes, drop the -n1 so it keeps sampling, and add the CPU power sampler to see load and heat together:
sudo powermetrics --samplers smc,cpu_power -i1000
Press Ctrl-C to stop. (Intel Macs expose more discrete sensors; Apple silicon reports a smaller, cleaner set.)
What counts as "normal"
There is no single safe number, and chasing one leads people astray. As a rough guide for Apple silicon:
| State | Typical CPU die temp | What it means |
|---|---|---|
| Idle / light use | ~30–50 °C | Normal. Fanless Macs sit here silently. |
| Sustained load (compile, export, game) | ~70–95 °C | Normal under work. The chip is designed for this. |
| Pinned near max for a long time | mid-90s °C+ | The CPU throttles itself to protect the hardware: safe, but something is working it hard. |
Apple silicon is built to run warm and throttle rather than overheat. A high reading during a build or a video export isn't a fault. What's worth investigating is heat with no obvious cause: a fan spinning hard while you're doing nothing.
The temperature is a symptom, not the cause
This is the part most temperature guides skip. Knowing your Mac is at 92 °C tells you nothing you can act on. Knowing which process put it there does. Heat almost always traces back to one busy process: a runaway app, a stuck background daemon, or normal-but-heavy work like indexing.
So the useful move is to pair the temperature with the workload:
- Open Activity Monitor → CPU and sort by % CPU to find the top consumer.
- If it's a system process, it often has a known explanation; see kernel_task high CPU, WindowServer high CPU, or mds_stores / Spotlight indexing.
- If the fans are the main complaint, MacBook fans loud and running hot walks through finding the culprit.
Apps that show it in the menu bar
If you want the temperature at a glance instead of in Terminal, a menu-bar monitor keeps it visible:
- Stats: free and open-source; shows CPU temp, load, fans, and more in the menu bar.
- iStat Menus: the long-standing paid option, with detailed sensor breakdowns. (See our iStat Menus alternative if you want the monitoring without a separate purchase.)
- TG Pro / Macs Fan Control: focused on temperatures and manual fan curves.
Any of these read the same SMC sensors powermetrics does; the difference is convenience and how much they surround the number with context.
See the heat and the fix, in one place
A temperature readout is only half the story; the other half is the process that caused it, and doing something about it. Plumby puts live CPU, memory, and fan readings in your menu bar in plain language, and sits the fix right next to each one: the app that's working the CPU, named and rankable, so you can stop guessing at a number and deal with the thing behind it. Every reading is measured from the machine's real state, never estimated.
