Mac Running Hot and MacBook Fan Loud: How to Find the Process Behind the Heat
Mac running hot or fans staying loud? Check CPU, GPU, energy use, ventilation, and hardware symptoms to narrow down the cause.
5 guides
Trace high resource use, heat, and loud fans to the right workload. Start with what you can observe, then follow the relevant process guide.
Check CPU and energy use first. If the load is low, the guide also covers ventilation, surroundings, and hardware symptoms.
Read the guide →Investigate WindowServer and graphics-heavy apps. Compare the load as you close windows or change the display setup.
Read the guide →Read what its CPU figure represents before taking action. Follow the thermal troubleshooting path instead of trying to terminate the kernel.
Read the guide →Work through the guides that match your situation, in the order below.
Mac running hot or fans staying loud? Check CPU, GPU, energy use, ventilation, and hardware symptoms to narrow down the cause.
WindowServer at 100%+ CPU? It is the macOS process that draws every pixel on your screen. Learn why it spikes, when to worry, and how to find the app actually causing the load.
Seeing kernel_task in Activity Monitor? Learn what PID 0 means, why high CPU protects an overheating Mac, and how to find the real process causing it.
mds_stores eating CPU and disk? It is Spotlight's per-volume indexer. Most spikes are real work that resolves on its own — learn how to tell legitimate indexing from a stuck process, and what actually fixes it.
Step-by-step guide to diagnosing a slow Mac — find processes causing high CPU, memory pressure, and disk I/O, then kill or manage them with the right tool.
Use Apple’s built-in tool for an initial check. Its official guide explains the available views and measurements.
Read the guide ↗Inspect the process tree, resource history, and process details together. Start with the product overview or follow the setup guide.
A large memory number is only the beginning. Use memory pressure, app behavior, and changes over time to decide what deserves investigation.
5 guidesFind what is running, identify its parent app, and inspect unfamiliar processes before deciding what to close. Compare built-in tools with deeper inspection workflows.
12 guides