What kernel_task is on a Mac, and why it is using your CPU
kernel_task is not a virus or an app you installed. It is the kernel's own process, and a high number in Activity Monitor is a heat report, not a fault.
By Chethan Kumar S N · Updated
The fans come first. Then Activity Monitor, sorted by CPU, and something you have never heard of sitting near the top. WindowServer is the usual suspect, and if that is the one you found, there is a page for it. The other one is stranger, because the name says kernel and the number beside it is zero.
kernel_task is not an app, not a driver and not something anyone installed on your Mac. It is the kernel, the thing macOS runs as, and Apple has a support article about this exact question that answers it in a paragraph. This page is that paragraph, plus what the numbers actually mean and the short list of things worth doing about them.
What it actually is
Apple’s article is called “If kernel_task is using a large percentage of your Mac CPU”, and it opens by telling you what the process is for. One of the functions of the kernel task process, it says, is to help manage the temperature of your CPU.
That is the answer in one line, and the rest of the page follows from it. The same article goes on: kernel_task responds to conditions that cause your CPU to become too hot, even if your Mac doesn’t feel hot to you. It does not itself cause those conditions. When the CPU temperature decreases, kernel_task automatically reduces its activity.
Read the second sentence twice, because it is where almost every forum thread about this goes wrong. A high kernel_task figure is a report, not a cause. Apple is explicit that the process does not create the heat, that it answers it, and that it stands down by itself once the temperature falls. So the useful question is never how to stop kernel_task. It is what is making this Mac hot, and that question has its own page covering Apple’s two articles on fans, temperature and the surfaces a laptop should not sit on.
Why the number beside it is zero
The thing that makes kernel_task look wrong is the number next to it. It is 0, which is where the searches for kernel_task (0) come from, and the honest explanation is that the kernel is not a process in the way everything else in that list is.
Ask the ordinary tools and they come back empty:
$ ps -Ao pid,comm | grep -c kernel_task
0
$ ps -p 0
PID TTY TIME CMD
ps lists nothing for it, which is correct rather than broken. kernel_task is the kernel itself, not a program the kernel started, so it has no entry in the process table. The tools that read the kernel directly do show it, with that zero as its identifier:
$ top -l 1 -stats pid,command,cpu,time,threads | grep kernel_task
0 kernel_task 0.0 78:43:39 1096/10
There is a lot in that one line. The last column is threads, 1,096 of them with ten running, which sounds alarming until you remember that the kernel’s own threads live here, so a thread count in the thousands is normal on a machine that has been up for a while. The middle column is processor time since boot, 78 hours and 43 minutes of it, and the Mac it was read on had been up 24 days, which works out at roughly 13 per cent of one core averaged across the whole life of the machine. On ten cores that is about 1.3 per cent of the Mac.
And the CPU column says 0.0.
On Apple silicon it usually looks quiet
That 0.0 is worth stating plainly, because the internet’s version of this process is the loud one. The famous screenshots are Intel Macs with kernel_task pinned near the top of the list and the laptop sounding like a hairdryer. Apple’s article describes exactly that case, and it is real. It is also not the resting state, and it is not what most people will see.
The reading above came from an M1 Pro running macOS 27.0.1, with a load average around eight and a day and a half of accumulated kernel time, and kernel_task still reported 0.0 per cent at the moment it was read. If you are on an Apple silicon Mac and the number is low, that is not a fault, a hiding process or a broken Activity Monitor. It is the kernel doing its ordinary work with nothing to brake.
Why it climbs when it does
The mechanism is one sentence in Apple’s article: kernel_task helps manage CPU temperature by making the CPU less available to processes that are using it intensely. That is a brake, applied on purpose. macOS is slowing the machine down so that it does not cook.
Which means the number rises when something else is working hard and the machine cannot shed the heat fast enough. The causes people find are mostly boring:
- A process that will not stop. A runaway app, a stuck render, a background job in a loop. This is the one Apple’s article points at, and it is the one worth checking first.
- Charging while you work. Power going into the battery is heat, and a warm chassis has less headroom to absorb the rest.
- Something resting on the vents. A bed, a sofa, a cushion, a closed case. Apple’s own description of what the system controller manages is a list of power and thermal hardware, and it includes the fans, which need somewhere to push air.
- An external display. This is the folk theory of the moment. It is testable in about two minutes, so test it rather than believing it.
- The day or two after a system update. Spotlight, Photos and the rest are rebuilding indexes, and indexing is real work. If the timing fits, what Spotlight indexing actually does is the page to read before you start hunting processes, and the Photos half of that rebuild is photoanalysisd.
- A genuinely hot room. All of the above is harder to do at 35 degrees than at 20.
Reading the CPU number properly
One thing to get right before you decide anything is what the figure measures. Activity Monitor’s percentages are against a single core, not against your whole Mac, which is why a busy process can read well above 100 per cent. The WindowServer page has the measurement that makes this obvious, on the same ten core Mac: a four thread test program reported itself at 396 per cent while it ran, because four cores of ten is 40 per cent of the machine.
So 100 per cent for kernel_task is one core out of ten, not the whole computer. And the CPU tab tells you something else useful while you are there: of the three totals at the bottom of the window, System is the share going to processes that belong to macOS, which is where a busy kernel task lands, and User is the share going to apps you opened. If System is high, look for a system process rather than a browser tab.
What actually helps
In order, cheapest first.
Find the process that is really working. Open Activity Monitor, click CPU, click the % CPU column heading to sort, and watch for a few updates. Apple’s own note is that its figures refresh every five seconds, so a single glance will not tell you whether something is climbing. The process feeding the heat is the one worth acting on.
Use the Energy tab, which is the tab people forget. It shows Energy Impact, which Apple describes as a relative measure of the current energy consumption of the app, and 12 hr Power, the average energy impact over the last 12 hours, which only appears on a laptop. It also has columns for whether App Nap is active, whether the app is preventing your Mac from going to sleep, and whether it wants the high performance graphics card. Heat follows work, and this is the tab that finds the work over a whole day rather than over the last five seconds.
Check the Memory tab before you blame the CPU. Apple’s test for a memory problem is the Memory Pressure graph, which it defines as how efficiently memory is serving your processing needs, determined by the amount of free memory, swap rate, wired memory and file cached memory. Green pressure with a busy kernel task points somewhere else entirely, and why a Mac is running slow works through the order to read those tabs in.
Take the weight off the machine. Get it onto a hard surface, out of a case, and out from under anything soft. If it is charging and hot, let it finish before you decide anything.
Settle the display question with a test rather than an opinion. Unplug the monitor, watch the number for a minute, plug it back in and watch it again.
Restart, and give it an hour. If the machine has just taken a system update, the first day includes work that goes away on its own. Updates also leave files behind for a while, which is why System Data on a Mac often climbs around the same time it takes an update and falls back later once macOS clears the staged files.
And one piece of advice to ignore. The classic forum answer is to reset the SMC. Apple’s own page on that opens with “You most likely do not need to reset the SMC”, says it may help with certain issues on Intel based Mac computers, and lists fans running fast and a laptop getting too warm among them. For Apple silicon there is no procedure to follow at all: plug in, restart, and Apple’s words are that the SMC resets automatically on Mac with Apple silicon. On an M series Mac there is nothing to reset.
What does not help
Force quitting it. Apple’s article does not offer it, and there is no process underneath to quit. The remedies it does point at are finding the processes using your CPU intensely and quitting those.
Any app that promises to fix or disable kernel_task. The process is the kernel. There is nothing to clean, patch or remove.
Quitting the other system processes you do not recognise. Most of the unfamiliar names in this list are Apple’s own and are doing ordinary work, which is worth knowing before you start closing them. mDNSResponder answers every name lookup the machine makes, and its log will tell you which app asked rather than leaving you to guess.
Deleting things in system folders. The kernel itself is a single file whose size and age you can look at, and it is not the problem:
$ sysctl -n kern.version
Darwin Kernel Version 27.0.0: Tue Aug 11 21:22:49 PDT 2026;
root:xnu-13432.1.9~1/RELEASE_ARM64_T6000
$ ls -la /System/Library/Kernels/kernel.release.t6000
-rwxr-xr-x 1 root wheel 17158864 /System/Library/Kernels/kernel.release.t6000
Two things are worth noticing there. The version string names the exact kernel this Mac is running, and RELEASE_ARM64_T6000 is the build for this machine’s chip family, which is why /System/Library/Kernels holds a separate 17 MB kernel for every Apple silicon generation rather than one file for all of them. And when a hardware fault is real, this is the layer it shows up in, which is a conversation with Apple rather than something to fix by hand.
Where window managers fit
A window manager is not going to make a hot Mac cool, and it is fair to ask whether it makes things worse. The measurement on the WindowServer page answers most of that: moving a window 54 times in ten seconds cost about a fifteenth of a second of processor time, against a ten second baseline that had already spent two and a third. Arranging windows is not what heats a Mac. A runaway render, a sync job or a full time video call is.
What a manager changes is how much arranging you do by hand. Tiling built into macOS covers halves, quarters and a centre, and if you have two screens, moving windows between monitors is its own problem with its own page.
Ribbon keeps the windows you use as a scrolling strip instead of placing one each time you name a spot, so opening a sixth window makes the strip one column longer rather than making everything narrower. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs.
The short version
kernel_task is the kernel, which is why its process ID is 0 and why ps cannot see it and everything else can. Apple says one of its jobs is managing CPU temperature by making the CPU less available to intense processes, so the number on your screen is a response to heat rather than a cause of it, and it comes down on its own. On the Mac this was checked on, an M1 Pro under a real load, it sat at 0.0 per cent. If yours does not, find the process doing the work, look at the Energy tab rather than only at CPU, and get the machine onto a hard surface before you conclude anything. And skip the SMC advice if your Mac is Apple silicon, because Apple’s own page says there is nothing there to reset.
Questions
What is kernel_task on a Mac?
It is the kernel's own process, the thing macOS runs as, rather than an app, a driver or a background service you could uninstall. Apple's support article on it says one of its functions is to help manage the temperature of your CPU. It appears in Activity Monitor with the process ID 0, and ordinary tools such as ps do not list it at all, because the kernel is not a program the kernel started.
Is kernel_task a virus or malware?
No, and it is one of the few processes on the list that could not be. It is the kernel, the part of the system that everything else runs on top of. Malware does not get to be the kernel, and a process that showed up in Activity Monitor with the ID 0 and 1,000 or more threads is not an intruder trying to pass as one. If you are hunting something unwanted, look at what is using your CPU and your Energy Impact, not at kernel_task.
Can I force quit kernel_task?
There is nothing useful to quit, and Apple's article does not offer it as an option. The process is the kernel, so it does not belong to your account, and the two things Apple's page points you towards are working out which processes are using your CPU intensely and quitting those instead. A restart is the only reset that means anything here, and it is the same kernel coming back up.
Why is kernel_task using so much CPU?
Apple's own explanation is that one of its functions is to help manage CPU temperature by making the CPU less available to processes that are using it intensely. It responds to conditions that make your CPU too hot, even if the Mac does not feel hot to you, and it does not itself cause those conditions. So the number is a report rather than a fault. Find the process that is actually working the machine hard and the kernel task calms down on its own.
What does the zero next to kernel_task mean?
That is the process ID, and there is no ordinary process with ID 0. It is the kernel itself rather than something the kernel launched, which is why the process tools disagree about it: ps finds nothing named kernel_task, and the kernel level view that top and Activity Monitor use shows it with that 0 as its identifier. It is not an error and it is not a sign that the process is damaged.
Ready? Buy Ribbon for $15, or read all the guides.