How to check your Mac’s CPU temperature

macOS ships no temperature readout. There is no panel in System Settings, nothing in Activity Monitor, and nothing in System Information. Apple’s position is that thermal management is the machine’s job and not yours, which is defensible right up until you want to know whether the thing you just bought is throttling.

The sensors are there. You just have to ask for them.

The built-in way: powermetrics

Every Mac has powermetrics, a command-line tool that reads the same sensors everything else does. It needs root because it talks to the hardware directly. In Terminal:

sudo powermetrics --samplers smc -i1000 -n1

That takes one sample and prints it. On Apple Silicon the interesting lines are the CPU and GPU die temperatures and the fan RPM. For a live view, drop the -n1 so it keeps sampling:

sudo powermetrics --samplers smc -i2000

Two caveats worth knowing. It requires your password every time, which makes it awkward for anything sustained. And powermetrics is itself a running process, so leaving it sampling at a fast interval adds a small amount of the load you are trying to measure. Two seconds is a reasonable floor.

Which sensor is the one to watch

An Apple Silicon Mac exposes dozens of thermal sensors, and most of them are not what you want. There are sensors on the battery, the charger, the enclosure, individual memory packages, and several points across the die. People often quote whichever number is highest, which is how you end up with alarming screenshots that mean nothing.

The three that carry information:

• CPU performance core temperature. The P-cores do the heavy lifting and run hottest under load. This is the number that correlates with throttling.
• GPU temperature. Relevant for gaming, video encoding, and anything driving a large external display.
• SoC or package temperature. A wider average across the chip. Smoother than the core readings, which makes it better for spotting a trend and worse for spotting a spike.

Enclosure and battery sensors are useful for a different question, which is whether the machine is uncomfortable to touch, not whether it is fast.

Reading the numbers without panicking

Apple Silicon runs hot by design. A P-core touching 100 °C during a burst is normal behaviour, not a warning, and the chip has hardware protection long before anything is at risk. What matters is not the peak but how long it is held and what happens to clock speeds while it is. Normal temperature ranges for Apple Silicon goes through this in more detail.

A single number is also close to useless on its own. Temperature only means something alongside what the machine was doing when it was measured. A 95 °C reading during an export and a 95 °C reading at idle are completely different findings, and only the second one is a problem.

Menu bar apps

The practical reason people install something is that powermetrics does not give you history. You get the instant, not the shape. Watching a number climb over ten minutes of sustained work tells you far more than any single sample, and that is the case for having a readout on screen while you work.

Breeze does this part for free, permanently: every temperature sensor, a per-sensor heatmap, fan RPM, and a rolling five-minute graph in the menu bar. There is no account, no telemetry, and no time limit on the monitoring. It samples every two seconds, which is frequent enough to catch a spike and slow enough not to become part of the problem.

The paid half of the app is manual fan control, which is a separate question and one you can only answer sensibly after you have watched the numbers for a while. If your machine never approaches its limits under your actual workload, you do not need it, and the monitoring will tell you that for nothing.

A note on Intel Macs

Everything above about powermetrics applies to Intel Macs too, though the sensor names differ and the temperatures mean something slightly different: Intel machines throttle at lower die temperatures and are generally louder about it. Breeze is Apple Silicon only, so if you are on Intel hardware, the built-in command is your starting point.