Mac temperature monitor: how to check CPU temperature and fan speed, and what the numbers mean
On Apple silicon Macs there is no built-in temperature readout, so you need a menu bar app: Stats (free, open source), iStat Menus, TG Pro or Macs Fan Control all show chip temperature and fan speed. The numbers matter less than people expect. A chip in the 90s Celsius while exporting video is working as designed, and macOS slows it before it can harm itself. The real signal is heat while idle: a warm Mac with a loud fan when nothing is open means a process is busy, not that the sensor is high. Find that process in Activity Monitor; the temperature follows.
- Built-in readout
- None on Apple silicon. Terminal's powermetrics can print it but needs admin rights
- Free option
- Stats (open source, GitHub). Sensors module off by default; turn it on
- Paid options
- iStat Menus (most polished), TG Pro (temps plus fan control), Macs Fan Control (free to monitor)
- Normal under load
- High 80s to around 100 C on the chip. By design; macOS throttles before harm
- The real signal
- Warm case and spinning fan while idle for more than a few minutes
- Apple's ambient range
- Use a Mac notebook where the room is 10 to 35 C (50 to 95 F)
How to check your Mac's temperature
macOS does not show temperature anywhere in its interface. Activity Monitor has CPU, Memory, Energy, Disk and Network tabs and no Thermal tab. System Information lists sensors but not readings. On Intel Macs, long-time users could read the SMC through small utilities; on Apple silicon the sensors are reached through a different interface and the first-generation M1 exposed them only through the HID system, which is why some older tools show nothing.
There is a command-line route. Terminal's powermetrics tool prints thermal pressure and, on some models, die temperatures, but it needs administrator rights and prints several screens of text every sample.
So in practice, checking temperature on a Mac means installing a menu bar app. Four are worth considering, and they split by what you want from them.
Just see the number: Stats, free and open source, or Macs Fan Control, free for monitoring. See it beautifully with history, alerts and everything else: iStat Menus. See it and take control of the fans: TG Pro, or Macs Fan Control's paid tier.
Whatever you install, note what one Apple Community regular pointed out about the Stats sensors module on M1 Macs: "It's disabled by default because it consumes a lot of CPU and energy." Polling sensors has a cost, and a monitor set to update every second can itself be a measurable load on the chip it is watching. Set the refresh to every few seconds.
The apps compared: Stats, iStat Menus, TG Pro, Macs Fan Control
Stats (free, open source, GitHub). Modular menu bar monitor: CPU, GPU, memory, disk, network, battery, Bluetooth and a Sensors module that shows chip temperatures and fan speed. The project's own README says Sensors and Bluetooth are its most resource-hungry modules and that its map of Apple silicon sensors is incomplete, so some readings are labeled generically. Fan control exists but is marked legacy. Bugs come and go, and the issue tracker in 2026 included reports of high CPU use from the Sensors module, so keep it updated and keep the refresh interval relaxed.
iStat Menus (paid, one-time per major version, also on Setapp). The long-standing benchmark: sensors, fan control with temperature curves, history graphs, rules and notifications (for example, alert when CPU stays above 80 percent), weather and clocks. A MacRumors member comparing it with Stats said "it has a level of polish that's pretty hard to beat". In the same thread a user noted that Activity Monitor used more resources than iStat Menus did.
TG Pro (paid, one-time). Narrower and focused: every temperature sensor the Mac exposes, fan speeds, and fan control with Auto Boost rules that spin fans up when a sensor crosses a threshold. It reports temperatures and spins fans; it does not tell you which app is causing the heat.
Macs Fan Control (free to monitor, paid Pro for custom curves). Simple window listing fans and sensors, with the option to set a constant speed or a sensor-based curve. A useful detail from its documentation: when you quit the app, fans return to automatic control, so you cannot leave a Mac stuck on a manual setting by accident.
All four read the same sensors. The differences are polish, price model, and whether you want fan control. None of them names the process making the Mac hot; that is a separate job covered below.
What is a normal Mac temperature?
These are typical chip readings reported by monitoring apps on Apple silicon MacBooks. Exact numbers vary by model, sensor and room; the ranges are what to expect.
A fanless MacBook Air behaves differently from a MacBook Pro: with no fan it reaches its limit sooner under sustained load and simply slows down, which is why an Air exporting a long video feels warm and takes longer. That is the design working, not a fault. Apple's own guidance on operating temperature is about the room, not the chip: use a Mac notebook where the ambient temperature is between 10 and 35 C (50 to 95 F).
What the numbers actually mean
A temperature readout answers one question, how hot is the chip, and people usually want it to answer a different one: is something wrong, and what? The numbers alone cannot say.
High under load is expected. Modern chips are designed to run up to their thermal limit and then hold it. When the sensor reads 95 C during a render, the chip is doing exactly what it was built to do, and macOS will throttle it rather than let it go further. An Apple Community regular answering a "what is a safe temperature" thread put it simply: "The computer will normally Throttle when and if the computer is operating in an elevated temperature state".
Throttling shows up as kernel_task. When the chip needs to slow down, macOS has kernel_task take CPU time away from other processes, so Activity Monitor shows it at 80 or 90 percent. That confuses people into thinking kernel_task is the cause. Howard Oakley's explanation has been quoted for years: "kernel_task isn't causing the thermal problem, it's part of your Mac's response to it."
The reading you want is the trend, not the peak. A chip that spikes to 100 C and drops to 60 C when the export finishes is healthy. A chip that sits at 80 C with nothing visibly running, or that stays hot after you quit everything, is the one to investigate. Heat is the symptom; some process is the cause.
Fan speed is the same story. A fan at 6,000 rpm during a compile is doing its job. A fan at 6,000 rpm while you read email is telling you a process is working hard in the background: indexing after an update (mds_stores), a photo library scan (photoanalysisd), a stuck sync client, or a browser tab. The Mac overheating and fan loud guide lists the usual suspects in order.
See how load turns into heat and fan noise
Drag the slider to see what happens to the chip, the fan and kernel_task as the load on your Mac rises. The chain is the same on every model: work makes heat, heat makes the fan spin, and if that is not enough, macOS slows the chip.
Every link in that chain starts with work. A temperature monitor shows you the middle of the chain. The useful question is always the first link: what is doing the work?
Why temperature is less useful than knowing which app causes it
Here is the pattern from Apple Community threads about hot Macs. Someone installs a monitor, confirms the chip is at 90 C with the fan loud, and then writes: "CPU is around 80%, and the fan is making a loud noise, when I'm doing nothing." They open Activity Monitor and add: "I've looked at the CPU usage, and there's nothing showing that's taking a high percentage of CPU." The temperature app has confirmed the symptom and the thread stalls.
What is usually happening: the busy process is a system one with an unfamiliar name, it is sorted off the bottom of the list because Activity Monitor is showing only My Processes, or it is bursty and drops out between refreshes. The fix is to show All Processes, sort by % CPU, and watch for a minute rather than a glance.
A temperature monitor cannot do that part. iStat Menus will show you a graph of the chip climbing; TG Pro will spin the fans harder; Stats will put a red number in the menu bar. None of them connect the heat to the app. That connection is what resolves the problem, because once you know it is mediaanalysisd scanning a new photo library, you know it will finish by itself, and once you know it is a browser tab, you know to close it.
That is the gap Safe to Quit is built for: it watches every process over hours, names the one that is making the Mac hot, loud or slow in plain words, and says whether it is safe to quit or better left to finish. Temperature is the thermometer; this is the diagnosis. Use both if you like numbers, but if you only want the Mac to cool down, the second is the one that gets you there.
Should you control the fans yourself?
TG Pro, iStat Menus and Macs Fan Control all let you override the fan curve: spin up earlier, hold a minimum speed, or run flat out. It is tempting, and it has real trade-offs.
Spinning fans earlier keeps the chip cooler under sustained load, which can delay throttling and keep a long export slightly faster. The cost is noise, a little more battery drain, and more dust pulled through the vents over time.
Spinning fans slower for quiet is the risky direction. macOS's own curve already favours quiet; forcing the fan below it lets the chip run hotter and throttle sooner. Nothing will be damaged, because the chip protects itself, but the Mac will be slower and you will have paid for a utility to make it so.
The safety net is that these tools hand control back to macOS the moment they quit (Macs Fan Control documents this explicitly) and macOS still enforces its own limits above any curve you set. You cannot cook a Mac with a fan app. You can only make it louder or slower than it needs to be.
The honest recommendation: leave fan control automatic unless you have a specific, repeatable workload that measurably benefits, and even then, find the process first. A fan curve is a way to cope with heat. Quitting the thing causing it removes the heat.
What to do when your Mac runs hot
- Check whether it is doing work
Open Activity Monitor, choose View, All Processes, click the % CPU column, and watch for a full minute. A process steadily above 50 percent explains the heat. If it is a system process you do not recognise, look it up in the Activity Monitor guide or the process pages on this site.
- Let indexing and scans finish
If the busy process is mds_stores, mediaanalysisd, photoanalysisd or similar, it is indexing after an update or a big import. Leave the Mac awake and plugged in; it finishes within hours and the heat goes with it.
- Quit the app or tab
If it is a browser, close the heavy tab or window (⌘W). If it is an app, save and quit it (⌘Q). Watch the temperature fall over the next two or three minutes; that confirms the cause.
- Clear the vents and the surface
Lift a laptop off soft surfaces (bed, sofa, lap blanket) that block the intake. Check the room is within Apple's 10 to 35 C range. Direct sunlight on a dark lid adds a surprising amount of heat.
- Unplug accessories one at a time
An external display drives WindowServer harder, and some USB hubs and chargers add heat near the chip. If the fan calms when a device is unplugged, you have found it.
- Restart
A restart ends any process that has been stuck for days and resets the power and thermal management daemons. If the Mac is hot at idle immediately after a restart with nothing open, move on to the next step.
- Consider dust or a service check
A Mac that is several years old and runs hot and loud at idle even after a restart may have dust in the fan and vents. Oakley's long-running kernel_task article notes that "By far the most common cause of more persistent problems, though, is dust and debris in the air ducts." Apple Diagnostics (hold the power button at startup on Apple silicon) checks the sensors and fan; a service visit can clean the inside.
When to worry
Most of the time, a high reading is not a worry. These are the patterns that are.
Hot at idle, repeatedly, after a restart. Nothing open, fan audible, chip in the 80s. Either a background process is stuck in a loop (find it in All Processes) or the cooling path is blocked. Dust, a failed fan or a sensor fault are hardware problems and Apple Diagnostics will usually flag them.
The fan never runs on a Mac that has one. Silence under heavy load on a MacBook Pro or iMac is not good news. If the monitor shows 0 rpm while the chip climbs past 100 C, the fan may have failed. Book a service check.
Shutdowns under load. A Mac that switches itself off during exports is past throttling and into protection. Same answer: hardware check.
Everything else, a chip at 95 C during a render, a fan at full speed during a compile, a warm Air during a video call, is the machine working as designed. powerd and thermalmonitord manage the limits in the background and need no help. Install a monitor if you enjoy the numbers; install nothing at all if you just want the Mac to be quiet, and find the process instead.
What people hit, in their words
“The computer will normally Throttle when and if the computer is operating in an elevated temperature state”
“It's disabled by default because it consumes a lot of CPU and energy.”
“kernel_task isn't causing the thermal problem, it's part of your Mac's response to it.”
“it has a level of polish that's pretty hard to beat”
Installing Stats and turning on the sensors module
Install FREE Stats Temperature/Fan monitoring app on macOS Sonoma by Andrew Tsai's Tips. The free route. Set the refresh interval to a few seconds once it is running.
Questions people ask
Can you see the temperature of your MacBook?
Not in macOS itself; there is no temperature readout in Activity Monitor or System Settings on Apple silicon. You need a menu bar app such as Stats (free, open source), iStat Menus, TG Pro or Macs Fan Control, all of which read the same built-in sensors and show chip temperature and fan speed. Terminal's powermetrics can print thermal data but needs administrator rights.
Is there a free way to monitor CPU temperatures on a Mac?
Yes. Stats is free and open source and shows CPU, GPU and sensor temperatures plus fan speed in the menu bar; enable its Sensors module, which is off by default. Macs Fan Control is free for monitoring and only charges for custom fan curves. Both read the same sensors as the paid apps; the paid ones add polish, history graphs and alerts.
How do MacBooks stay cool without a fan?
The fanless MacBook Air spreads heat through an internal heat spreader and the aluminium case, then relies on macOS to slow the chip when it reaches its limit. Under short bursts it performs like a MacBook Pro; under sustained load (a long export, a game) it throttles sooner and finishes slower. That is by design and causes no harm. If an Air is warm at idle, a background process is the cause.
What temperature is too hot for a MacBook?
For the chip, nothing you can reach in normal use: macOS throttles around 100 C before any damage can occur, so a reading in the 90s under load is normal. For the room, Apple says to use a Mac notebook between 10 and 35 C (50 to 95 F). The number to act on is not a peak but a pattern: a chip in the 80s with nothing running, repeatedly, after a restart.
Is iStat Menus worth it, or is Stats enough?
For seeing temperatures and fan speed, Stats is enough and free. iStat Menus is worth paying for if you want polish, long history graphs, rules and alerts, and fan curves in one well-maintained app, and it is light on resources. Neither tells you which app is causing the heat, so pair either with Activity Monitor or a process monitor for the diagnosis.
Should you shut down a Mac every night?
No need. Sleep uses almost no power and macOS runs maintenance while asleep and plugged in. A restart once a week or so is worth it: it ends any process that has been quietly busy for days, resets the thermal and power daemons, and clears swap. If a Mac that runs hot at idle cools down after a restart, that confirms a stuck process rather than a hardware problem.
Sources and further reading
- Apple Support: Keep your Mac notebook within acceptable operating temperatures 10 to 35 C ambient range
- Apple Community: How can I check cpu temp on my desktop mac May 2024, M1 iMac
- Stats on GitHub (exelban/stats) README on sensors module cost and Apple silicon coverage
- Eclectic Light: Why is kernel_task eating my CPU?
- TG Pro by Tunabelly Software
- Macs Fan Control by CrystalIDEA Fans return to automatic when the app quits