# How to Check Mac Temperature and Fan Speed > Check Mac temperature and fan speed with Activity Monitor and powermetrics, and learn why the SMC sampler fails on current Apple silicon Macs. Published: 2026-07-19 | Updated: 2026-08-17 macOS does not provide a built-in dashboard of CPU temperature and fan RPM. It does provide the more actionable thermal state: whether the system is under pressure and limiting work. Third-party tools can expose sensor readings, but the label, location, and normal range of a sensor vary by Mac. Apple also cautions that these readings are not the external case temperature and should not be used alone to diagnose hardware. A single degree value without workload and trend is easy to misread. ## Four routes, and what each one can actually tell you | Route | Gives you | Does not give you | Cost | |---|---|---|---| | Activity Monitor | Which process is driving load, energy impact | Any temperature, any fan RPM | None, ships with macOS | | `pmset -g therm` | Whether macOS has recorded thermal or performance pressure | Degrees, sensor names | None, no admin needed | | `sudo powermetrics` | Power and thermal-pressure detail for one bounded sample | A stable CPU or GPU temperature on Apple silicon | Admin password | | A sensor monitor | Named sensor readings and fan RPM where the model exposes them | A threshold that transfers to another Mac | A third-party app, model-specific | | Apple Diagnostics | A hardware verdict from Apple's own test | Live monitoring | A restart | The order matters more than the tools. Load explains most heat, pressure tells you whether macOS is already reacting, and a degree reading is only interpretable once you know both. ## What Activity Monitor shows, and what it does not Activity Monitor, in Applications > Utilities, shows per-app CPU percentage, memory pressure, and energy impact. It is the right first stop for "what is making my Mac hot": open the CPU tab and sort by %CPU, and the process driving the load is named at the top. What it never shows is a temperature or a fan RPM. It tells you the cause of heat, not the heat itself. If the busy process is unfamiliar, [what your Mac's background processes do](https://mole.fit/blog/mac-processes-explained) is a good companion. ## Start with workload and thermal state macOS will tell you whether it is throttling, just not the number. With no admin rights: ``` pmset -g therm ``` On a cool machine every line is a negative, which is itself the answer: ``` Note: No thermal warning level has been recorded Note: No performance warning level has been recorded Note: No CPU power status has been recorded ``` When macOS does record pressure, it is reporting its own control decision, which is more useful than comparing one sensor against a generic internet threshold. For one finite sample with more power and thermal context: ``` sudo powermetrics --samplers thermal,cpu_power -n 1 ``` Run it only when you need the diagnostic. Compare idle and a repeatable workload rather than leaving a privileged sampler running indefinitely. `powermetrics` labels its power figures as estimates, so do not compare their absolute values across different Macs. ## Why the Terminal route stops there on Apple Silicon On some older Intel macOS releases, `sudo powermetrics --samplers smc` exposed sensor readings. On current Apple silicon systems that sampler is unavailable, and the refusal is immediate rather than empty output: ``` powermetrics --samplers smc # powermetrics: unrecognized sampler: smc ``` `powermetrics` can still report thermal pressure, but it does not present one stable CPU or GPU temperature in degrees. There is no public, unprivileged interface that provides a universal sensor mapping across Apple silicon Macs, which is why third-party tools require model-specific handling. ## Under the hood: where the numbers live Mac thermal management combines sensors near compute blocks, storage, battery, and other components with power and fan control. Intel and Apple silicon designs expose different sensor keys, and some MacBook Air models are fanless. Third-party monitors use model-specific or non-public interfaces, so two tools may choose different sensors for a label such as "CPU temperature." RPM is meaningful only on a model that has a fan and exposes its tachometer.
A model-specific monitor combines CPU and GPU load, available sensor keys, and fan RPM where present, then compares temperature trend, thermal pressure, fan state, and performance under the same workload.
Compare the same Mac, sensor, and workload. Temperature trend, thermal pressure, fan state, and performance matter more than one universal number.
## Reading fan speed, and what a fan cannot tell you Fan RPM is the most misread number on this list, because its meaning is inverted from what people expect. A fan spinning up is the cooling system working, not the machine failing; a silent fan under sustained load is the reading worth investigating. Three cases account for almost everything: - **No fan at all.** Every MacBook Air since the M1 is fanless and sheds heat through the chassis, so there is no RPM to read and a warm case under load is the design. - **Fan ramps under load, settles after.** The expected shape. The useful question is how long the cooldown takes with the workload gone, not the peak number. - **Fan at maximum with the machine idle.** This is the one to act on. Check for a runaway process first, then a blocked intake, then a sensor fault, in that order. The firmware owns the fan curve, and keeping that default is the right call. Manual control can trade noise for headroom during one known sustained workload, but it cannot repair blocked airflow, a failed sensor, or an idle heat source. ## How to interpret a sensor reading There is no universal "safe CPU temperature" that applies to every Mac and every sensor. Instead, record four things together: the sensor label, workload, thermal pressure, and whether performance or fan behavior changed. A brief high reading during a compile can be ordinary; a rising idle trend with no owner is more useful evidence. Activity Monitor plus `powermetrics` can provide workload and pressure. A monitor such as [Mole](https://mole.fit/)'s Status view adds temperature and fan trends where supported. Keep one local baseline if temperature matters to your work. Record the same named sensor, ambient conditions, power mode, fan state, thermal pressure, and task at idle and under one repeatable workload. Compare later readings only with that baseline. A value from another Mac model, another sensor label, or a room with a different temperature is not a limit for this machine. The one number Apple does publish is the room, not the chip: its [operating-temperature guidance](https://support.apple.com/102336) puts normal ambient between 10 and 35 degrees Celsius, and recommends checking CPU activity when a Mac is warm at light load and using it on a stable ventilated surface. ## When it runs hot, in order 1. **Name the owner.** Activity Monitor, CPU tab, sorted by %CPU. Most heat has one process behind it, and quitting the right one ends the question. 2. **Check pressure, not degrees.** `pmset -g therm` says whether macOS is already limiting work. If nothing is recorded, the machine is warm rather than throttled. 3. **Remove the physical causes.** A soft surface, a blocked vent, direct sun, a room above 35 degrees, and a charging session all raise the floor before any software explanation applies. 4. **Compare against your own baseline.** Same sensor, same workload, same room. A number from a different Mac model is not evidence about this one. 5. **Ask the hardware.** Repeated shutdowns, thermal warnings at light load, a fan that grinds or never responds, or a machine that stays hot with nothing running are service symptoms. Run Apple Diagnostics before assuming that cache cleanup or a custom fan curve can fix them. ## A repeatable temperature check Record idle load and thermal state, run a fixed workload, take a bounded pressure sample, and compare the cooldown. If you use a sensor monitor, compare the same named sensor on the same Mac rather than importing a threshold from another model. Trends, throttling, noise, and workload attribution tell you more than one temperature number. ## FAQ ### What temperature is too high for a Mac? There is no published per-sensor limit, and any single figure you find online belongs to some other Mac model and sensor label. The answer macOS will give you is thermal pressure: if `pmset -g therm` records no warning, the machine is warm rather than throttled. Apple's own published range is for the room, 10 to 35 degrees Celsius. ### Why does my MacBook Air have no fan speed to read? Every MacBook Air since the M1 is fanless by design and cools through the chassis. There is no tachometer to report, so a monitor showing no RPM on those models is correct rather than broken. ### Do I need an admin password to check temperature? Not for the two most useful checks. Activity Monitor and `pmset -g therm` need nothing. Only `powermetrics` requires `sudo`, which is why it is worth running as one bounded sample instead of leaving it open. ### Why do two monitoring apps show different CPU temperatures? Because they are reading different sensors. Apple silicon exposes many sensor keys and no public mapping, so each tool picks its own and labels it "CPU". Compare a tool with itself over time on one Mac; do not compare one tool's number against another's. ### Is a loud fan a sign of damage? On its own, no. A fan ramping under load is the cooling system doing its job. What deserves attention is a fan at maximum while the machine is idle, a fan that grinds, or a fan that never spins up on a model that has one. --- Canonical HTML page: https://mole.fit/blog/how-to-check-mac-temperature Blog index for agents: https://mole.fit/blog/llms.txt Site index for agents: https://mole.fit/llms.txt