Mac Running Hot and Fans Loud With Nothing Open
Short answer
Open Activity Monitor (Applications → Utilities), click the CPU tab and sort by % CPU with All Processes selected in the View menu. Something is always responsible — most often Spotlight indexing, a Photos analysis pass, a browser tab, or iCloud syncing. Background system processes finish on their own; an app pinned at 100% for hours does not.
On this page
The fans spin up, the chassis gets warm under your left hand, and the Dock is empty. Nothing is open.
Something is running. macOS does not heat a processor for no reason, and Activity Monitor will name the process in about thirty seconds — provided you change one setting most people never touch.
Open Activity Monitor correctly
Applications → Utilities → Activity Monitor. Then, and this is the part that matters, open the View menu and choose All Processes.
The default view shows only your own processes. Every system daemon, indexer and sync agent — exactly the things that run when nothing is open — is hidden under the default. People check Activity Monitor, see nothing above 4%, and conclude the fans are faulty.
Click the % CPU column header to sort descending. The top row is your answer. Leave the window open for a minute, because some processes spike and settle.
What you are likely to find
| Process | What it is doing | Expected duration |
|---|---|---|
mds, mds_stores, mdworker |
Spotlight indexing the disk | Minutes to hours after a change |
photoanalysisd |
Scanning Photos for faces and scenes | Hours, once, then idle |
bird or cloudd |
iCloud syncing files | Until the sync completes |
backupd |
Time Machine running a backup | Minutes to hours |
kernel_task |
Managing heat, not causing it | Varies |
| A browser or Electron app | A tab or extension in a loop | Indefinitely |
The first four are normal and self-limiting. They are also the most common answer when the Mac has recently been restored from a backup, had a large photo library added, or finished a macOS update — all three trigger long indexing passes.
kernel_task is not the problem
kernel_task showing 200% or 400% looks alarming and gets misread constantly.
It is macOS deliberately occupying processor cores to reduce heat output, which
means it is a symptom of high temperature rather than a cause.
High kernel_task usually points at something physical: a blocked vent, a
failing fan, or on some Intel models a charger plugged into the wrong side of
the machine. Do not try to kill it. You cannot, and you would not want to.
When the top process is an app
A browser is the most frequent offender, and a browser with one busy tab looks identical to an idle browser from the outside.
Chrome has its own task manager — Shift+Esc, or the ⋮ menu → More tools → Task manager — which breaks usage down per tab and per extension rather than giving you one aggregate figure. Chrome using too much CPU walks through reading it and the settings that genuinely reduce load.
Safari does the same thing through Develop → Show Web Inspector on an individual tab, though the simpler test is closing tabs one at a time and watching Activity Monitor.
Electron apps — Slack, Discord, Teams, Notion — are browsers in a costume and behave the same way. A single one misbehaving after an update is common enough that quitting and relaunching should be your first move before any deeper investigation.
Check the Energy tab for the slower picture
The Energy tab shows Avg Energy Impact, which averages over the last several hours rather than the last second. A process that spikes periodically shows almost nothing under % CPU at the moment you look, and sits near the top of Energy.
This is how you catch things that wake up every few minutes: sync agents, updaters, badly written menu bar apps. The Memory tab matters too, because heavy swapping generates constant disk and processor activity that reads as heat. If the Memory Pressure graph is yellow or red, memory is your real problem, not CPU.
Rule out the physical causes
Software explains most cases. When it does not, check the dull things.
- Blocked airflow. Vents on a MacBook are at the rear hinge and underside. A bed, sofa or lap blocks them completely. A flat hard surface is not a nicety.
- Dust. Several years of it on a fan and heatsink raises idle temperature measurably. Compressed air through the vents helps a little; proper cleaning means opening the machine.
- Ambient heat. A Mac in a warm room or direct sunlight runs its fans harder for the same workload. This is not a fault.
- Charging. Fast charging generates heat. A Mac that is hot only while charging a nearly-empty battery is behaving correctly.
Apple silicon MacBook Air models have no fan at all. They get warm under load and quietly throttle instead. Silence on an Air is not evidence that nothing is running.
Login items and the restart test
A Mac that is hot within a minute of every startup has something launching with it. System Settings → General → Login Items & Extensions lists both the apps that open at login and the background items installed by apps you may have forgotten.
Turn off anything you do not recognise — a background item being off does not uninstall the app, so this is reversible. Then restart and watch Activity Monitor for five minutes.
Starting in safe mode gives you a cleaner comparison still: it loads a minimal set of system extensions and runs no login items. On Apple silicon, shut down, hold the power button until startup options appear, choose your disk and hold Shift while clicking Continue. On Intel, hold Shift during startup. A Mac that is cool and quiet in safe mode has a third-party cause.
Realistic expectations
Most cases end at the first screen: one process at the top of the list, either a system indexer that will finish or an app that needs quitting. Spotlight and Photos passes after a migration or a major update can genuinely run for several hours, and the correct response is to leave the Mac plugged in and let them finish rather than interrupting them nightly, which only makes them start again.
The honest limit is physical. If Activity Monitor is quiet, safe mode is quiet, and the machine still runs hot, you are looking at dust, a failing fan or dried thermal paste on an older machine. No setting fixes that, and no cleaner app will either. If the Mac also loses charge while apparently asleep, that is a separate mechanism covered in why a MacBook drains overnight with the lid closed.