Mac fan keeps running? Check CPU, memory, and fan speed first
A loud or persistent fan does not automatically mean something is broken. Check whether the Mac is under real load, whether memory pressure is high, and whether the fan trend matches the work you are doing.
If your Mac fan keeps running, start with three signals: CPU load, memory pressure, and fan speed trend. A short fan burst during a build, export, game, browser tab, video call, or external display session can be normal. A fan that stays high after the work stops deserves a closer look.
The fast path is not to quit random apps. First decide whether the machine is actually busy. Then open Activity Monitor when you need the exact process name.
Disclosure: I build teenystat. It is useful for this first pass because it keeps CPU, memory, and fan speed in the menu bar. It does not replace Activity Monitor, Apple Diagnostics, repair guidance, or common-sense checks such as airflow and ambient temperature.
Quick answer
| What you see | First check | What to do next |
|---|---|---|
| Fan rises during a known heavy task | Watch whether CPU and fan trend fall after the task ends. | If they settle, leave it alone. |
| Fan stays high while Mac feels idle | Check CPU and per-core load. | Open Activity Monitor and sort by CPU. |
| Fan rises with many apps open | Check memory pressure, not just memory used. | Quit the app causing pressure, then retest. |
| Fan is high but CPU and memory look normal | Check airflow, surface, room heat, external displays, and Apple's fan guidance. | If it continues, use Apple's diagnostics or support path. |
| No fan value appears | Confirm whether your Mac is fanless. | Watch CPU and memory instead. |
01Confirm the fan is actually sustained
A fan spike is not the same as a fan problem. macOS may spin fans harder while exporting video, indexing files, building code, running a browser benchmark, joining a video call, driving an external display, or charging under load.
What matters is the trend. Did the fan rise with the task and fall afterward? Did it stay high after the obvious work ended? Did it climb while the Mac was closed, idle, or sitting on a soft surface?
TeenyStat reads fan data through the AppleSMC path, shows current RPM for available fans, and tracks session highs and lows. On fanless Macs, it avoids stranding the menu bar on a fan value that cannot exist and switches back to memory if needed.
02Check CPU before quitting apps
CPU load is the most common reason a fan becomes noticeable. The mistake is guessing which app is responsible. A loud fan may be caused by the foreground app, a browser helper, Spotlight indexing, a sync tool, a stuck build process, a background renderer, or one tab doing far more than the window suggests.
TeenyStat reads CPU load through host_processor_info, computes usage from tick deltas, shows aggregate CPU, and includes a per-core mini chart. That does not name the process. It tells you whether the Mac is busy enough to justify opening Activity Monitor.
If CPU is high and stays high, open Activity Monitor, use the CPU view, and sort by CPU. Apple's Activity Monitor guide covers CPU activity, CPU Usage, and CPU History. The TeenyStat deep dive is checking Mac CPU usage per core from the menu bar.
03Read memory pressure, not just memory used
Many people see a high memory-used number and assume that explains the fan. Sometimes it does. Often it does not. macOS intentionally uses available memory for caching, and memory used is not the same signal as memory pressure.
Activity Monitor's Memory pane is better for diagnosis because it includes memory pressure, memory used, cached files, swap used, and compressed memory. If memory pressure is green and the fan is loud, RAM may not be the main cause.
TeenyStat shows used versus total RAM as a fast menu bar glance and breaks memory into active, wired, compressed, used, and free values in the popover. Use that for first-pass context, then use Activity Monitor when pressure or swap is the real question. The deeper explainer is Mac memory pressure vs memory used.
04Use fan speed as a correlation signal
Fan speed is useful when you compare it to CPU and memory over the same moment. Fan high, CPU high, and a known export running is one story. Fan high, CPU low, memory pressure low, and no obvious workload is another.
TeenyStat lets one metric live in the menu bar while the full dashboard stays one click away. If fan speed is your current problem, put fan RPM in the menu bar for a few minutes and watch whether it follows the workload.
Do not compare fan RPM across different Mac models as if there is one universal normal. Use it as a local trend on the same machine: lower, rising, sustained, falling, or unexpectedly high.
05Check airflow and Apple's fan guidance
Software is not the only explanation. Apple says fans may turn on when the processor is working on intensive tasks and notes that Mac notebooks should be used on a stable work surface with good ventilation. Blocked vents, soft bedding, room heat, dust, clamshell setups, and external displays can all change the thermal picture.
If CPU and memory do not explain the fan, stop guessing. Move the Mac to a hard surface, give vents room, unplug unnecessary devices, let the current task finish, and check whether the trend changes.
If the fan keeps running at high speed with no matching load or if the Mac reports thermal warnings, follow Apple's support path rather than treating it as a menu bar puzzle.
06When to open Activity Monitor
Open Activity Monitor when the first-pass signals point to real load. That means sustained CPU, a single hot core pattern that repeats, memory pressure that rises into yellow or red, swap that grows during the same task, or a fan trend that stays high after the app should be idle.
Sort by CPU first when the fan is loud. Then check Memory if the Mac feels sluggish, tabs reload, apps pause, or swap grows. If a browser is involved, use the browser's own task manager or performance tools after Activity Monitor shows the broad process family.
The rule is boring but effective: menu bar for the first signal, Activity Monitor for the process name, deeper profiling only after you can reproduce the problem.
A practical fan troubleshooting pass
- Write down what was happening when the fan rose.
- Watch CPU, memory, and fan speed for one or two minutes without changing anything.
- If CPU stays high, open Activity Monitor and sort by CPU.
- If memory pressure is high, inspect memory pressure, compressed memory, and swap.
- If one core is repeatedly high, check whether the same interaction triggers it.
- If CPU and memory look normal, check airflow, surface, room heat, external displays, and attached devices.
- Change one thing, then retest the same workload.
Sources checked
- TeenyStat feature claims were checked against the TeenyStat homepage and local Swift source for fan availability, AppleSMC fan reading, CPU reading through
host_processor_info, memory reading throughhost_statistics64, per-core charts, sparklines, menu bar metric selection, and fanless-Mac behavior. - Apple Support: View CPU activity in Activity Monitor on Mac.
- Apple Support: View memory usage in Activity Monitor on Mac.
- Apple Support: About fans and fan noise in your Apple product.
FAQ
Why does my Mac fan keep running?
A Mac fan often keeps running because the machine is under sustained CPU load, memory pressure, heat, blocked airflow, an external display or workload, or a stuck background process. Start by checking CPU, memory, and fan trend, then open Activity Monitor for the process name.
Can TeenyStat tell me which app is causing fan noise?
No. TeenyStat shows CPU usage, memory usage, fan speed, per-core load, and trends. Use it for triage, then open Activity Monitor when you need the exact process.
Why does TeenyStat show no fan speed on some Macs?
Some Macs, such as fanless MacBook Air models, do not have a fan to report. TeenyStat hides fan speed on fanless Macs and can show CPU or memory instead.
Keep system vitals close.
TeenyStat shows CPU, memory, and fan speed from the Mac menu bar, with per-core CPU, sparklines, thresholds, and a one-click dashboard.