kernel_task, WindowServer and other processes explained
What the macOS processes at the top of Activity Monitor do, why they sometimes use a lot of CPU, and what you can and can't do about it.
Sort Activity Monitor by CPU and you’ll often find processes you never installed: kernel_task, WindowServer, mds_stores. They are part of macOS. Quitting them isn’t an option, and mostly isn’t what you want.
The honest answer
Each of these has a job. When one is busy, there is usually a reason outside the process itself, and the reason is what you can change.
kernel_task
kernel_task is the macOS kernel and the system work around it: drivers, memory management and more. High usage by itself isn’t a fault.
One case catches people out. When your Mac gets hot, macOS can protect the hardware by reducing how much processor time other apps get, and kernel_task appears busy as part of that. If your Mac is warm, the fans are loud (or it has none, as on a MacBook Air) and everything is slow, then kernel_task high in the list is a symptom of heat, not its cause.
What to try: find which app is working hard (the CPU and Energy tabs), and close it. Make sure vents aren’t blocked and the Mac isn’t on a soft surface or in direct sun. Disconnect accessories one at a time if it started after plugging something in.
WindowServer
WindowServer draws everything you see: windows, menu bar, animations. Its cost grows with how much there is to draw, so it works harder with more or larger displays, high resolutions, many open windows, transparency and animation.
What to try: in System Settings, Accessibility, Display, turning on Reduce transparency and Reduce motion gives it less to do. Fewer open windows or lower display scaling can help as well. If WindowServer is busy only with a particular external display connected, try a different cable or resolution.
mds_stores and mdworker
These are Spotlight’s indexers. After a macOS update, a big file move or an external drive being connected, they can work hard for a while. This is temporary. Leave your Mac plugged in and it usually settles on its own. If it never does, the Spotlight index may need rebuilding, which is a job for the Spotlight settings in System Settings.
Other names you’ll meet
- launchd: starts and supervises other processes. Rarely busy.
- coreaudiod: handles sound. It’s busy while audio plays.
- Photos and photoanalysisd: analyze your library after imports. They pause when you use the Mac.
If you don’t recognize a process, search for its name before assuming the worst. Most are part of macOS, and the ones that aren’t usually belong to an app you installed.
How to check yourself
- In Activity Monitor, pick View, All Processes.
- Sort by % CPU and see which are consistently high.
- Look at what you were doing when it started: a new display, an update, a hot room, a new app?
Find the app that’s slowing your Mac has the full sequence.
How Hedroom does it
Hedroom explains processes like these in plain language, with a short note on what each does and what usually makes it busy. It never touches macOS’s own processes: anything Apple signs is explain-only. For these entries it points to the real cause where it can, such as a hot Mac, a display setup or an app working in the background, and offers fixes only for apps that are safe to touch.
Want Hedroom to do the checking? It reads memory pressure and swap for you, names the app that matters, and gives every fix a receipt. See how the free trial works or join the waitlist.