Why are my Mac fans running at full speed?

Short answer: fans pinned at maximum are usually a fault, not a workload. Mac fan control fails safe to full speed, meaning the system has to keep reading a temperature to justify staying quiet, so when it loses that reading it lets the fans run flat out. That means one question splits every cause: is the chip actually hot? Full speed on a cool Mac, or straight from boot, points at a sensor or a stuck controller, not at heat.

Start here: is the chip actually hot?

Before you touch anything, get one number: the hottest CPU or GPU temperature your Mac is currently reporting. Everything below hangs off that reading, and it takes under a minute. There are a few ways to read your Mac's temperature without opening anything up.

If the chip is hot, in the nineties or knocking on 100°C, the fans are doing their job and you should be looking for what is loading the machine or what is blocking the airflow. If the chip is cool, reading somewhere in the thirties or forties while the fans howl, then nothing about this is a heat problem. Your Mac is not fighting temperature. It has stopped trusting its own measurement of it, and maximum RPM is what that looks like from the outside. For a sense of which of those two camps your numbers fall into, the ranges are laid out in how hot is too hot for a Mac.

One more free clue: timing. Note whether the fans come up to maximum immediately at startup, before you have opened anything, or whether they climb there after a while. Full speed within seconds of the chime is almost never a workload, because there is no workload yet.

Every cause, the tell that identifies it, and what actually fixes it

Six things put Mac fans at maximum. The tell in the middle column is how you separate them without taking anything apart.

Why a Mac that cannot read its own temperature runs the fans flat out

This is the part almost nobody explains, and it turns the whole question around. Your Mac's fans are not off by default and switched on when needed. They are wired the other way up. Full speed is the resting state, and a control system has to actively hold them down. Temperature sensors feed the System Management Controller, macOS runs a thermal management daemon on top of that, and between them they decide how little airflow the machine can get away with. Quiet is the exception the system grants you when it can see that everything is cool.

Break any link in that chain and the permission to stay quiet disappears. A dead sensor, a cable that no longer carries the reading, a controller in a state it will not leave: none of those tell the firmware the Mac is hot. They tell it nothing at all, and nothing is the one answer it cannot work with. So it does the only safe thing available and releases the fans. That is why the symptom feels so disproportionate. A machine sitting cool on a desk with the fans screaming is not overheating. It is blind, and it is behaving exactly as designed for a Mac that has gone blind.

You can watch this in action without any fault at all. Boot many Macs into Safe Mode and the fans go straight to maximum, because the software layer that normally throttles them back is not loaded. Same mechanism, no broken hardware. It is the clearest demonstration there is that maximum RPM means absent control, not high temperature.

A failed or unplugged temperature sensor, including after a repair

If the chip is cool and the fans are at maximum, a sensor is the first suspect, and there is one rule that makes this much easier to reason about: the firmware cannot tell a missing sensor from a broken one. Both look like silence. That has two consequences. First, unplugging the part you suspect is not a valid test, because disconnecting a working sensor produces the identical symptom to a failed one. Second, and much more useful, any Mac that has recently been opened up is a prime suspect.

Sensors live in more places than people expect. On some MacBook Pros the trackpad carries one, and the cable that relays sensor data can be damaged during a battery replacement, which is why fans sometimes come up to maximum after a service that had nothing to do with cooling. Liquid damage does the same thing by corroding the path rather than the sensor. Desktops have their own version and it catches a lot of people: an iMac's display panel has a temperature sensor that gets unplugged from the logic board when you take the panel off to reach a drive or the memory. Leave it disconnected on reassembly and the fans run high afterwards, even though the drive you fitted is seated perfectly. Different sensors drive different fans, so a single missed connector can produce one loud fan and one behaving normally.

The evidence to look for is specific rather than vague. A sensor that reports a dash instead of a number is not reading. Several dashes at once usually means the shared bus or the cable rather than several simultaneously dead sensors, which is a useful thing to know before someone quotes you for parts. Apple Diagnostics is worth running and its reference codes are worth reading properly: PPF codes point at a fan, while PFM codes point at the System Management Controller. Do not treat a clean pass as proof of health, though. There are well-documented cases of Apple Diagnostics reporting no issues found on machines whose fans were still pinned at maximum, sensor fault and all.

A wedged thermal daemon, and the SMC state the firmware will not leave

Two software-adjacent causes are worth ruling out before you book a repair, because both are free and one of them is genuinely common. The first is the thermal management daemon getting wedged, classically across sleep and wake. The signature is clean: the fans were fine, the Mac slept, it woke up at full speed, and it has stayed there ever since on a chip that is stone cold. Nothing is broken. The layer that would normally hold the fans down has stopped doing so, and a restart puts it back. If a restart fixes it, that was your cause.

The second is a controller state that survives a restart. This is where most of the advice you will find online is a decade out of date, so be careful. On an Intel Mac there was a documented System Management Controller reset involving a key combination, and it was a reasonable thing to try. On Apple silicon that procedure does not exist. The controller is still there, still doing fan control and still exposing the sensors, but Apple removed the user-invocable reset, and the key combinations in older guides simply do nothing on an M-series Mac. What replaces it is unglamorous and it works: shut down fully from the Apple menu, leave it genuinely off rather than asleep for about thirty seconds, then power up normally. A restart is not the same thing, because a restart never takes the power down. If the fans come straight back to maximum on a cool machine after that, you have ruled out the state and you are looking at hardware.

kernel_task pinning your CPU while macOS fights the heat

If Activity Monitor shows kernel_task eating hundreds of percent of CPU while the fans are at maximum, you are seeing macOS actively intervening. kernel_task is not a runaway app. It is macOS occupying the processor on purpose so that nothing else can heat it up further, which is why the Mac feels sluggish and loud at the same time. The full mechanism, and why killing it is not the answer, is in what kernel_task is doing when it takes over your CPU.

The part that matters for this page is that kernel_task behaves the same way whether the heat is real or the reading is wrong. It responds to what the system believes about temperature. So kernel_task plus maximum fans plus a genuinely hot chip is thermal defence working, and it is the same story as thermal throttling. kernel_task plus maximum fans plus a cool chip is the sensor case wearing a different costume. Same tell, same fork, and it is worth resisting the popular advice to delete preference files to make kernel_task settle. That silences the symptom on a machine that may have a real hardware fault.

The mundane case: cooling that is genuinely saturated

Sometimes the fans are at maximum because they need to be, and it would be careless to skip that. Apple is straightforward about the by-design half: heavy processor work like compressing video, a graphics-heavy game, or Spotlight reindexing after you migrate to a new machine will run the fans faster, and high ambient temperature makes them turn on sooner and run faster too. Apple specifies an acceptable ambient range of 10°C to 35°C for Mac laptops, and a warm room eats into your cooling headroom before you have opened a single app. Blocked vents do the same. So does dust, which is quietly the most common real cause of all and the easiest to fix yourself once you know how to clean your Mac's fans.

The distinction to hold on to is between saturated and stuck. Saturated cooling tracks the work: it ramps, it holds while the load holds, and it comes back down afterwards. That pattern is a workload problem, and if the ramps are what is bothering you rather than the level, the causes behind Mac fans suddenly getting loud are the better read. A fan that runs constantly but never quite reaches maximum is a third thing again, covered in why a Mac fan keeps running and never returns to idle. Pinned at maximum, unchanging, on a cool machine, belongs to nothing on that list. It belongs to the fail-safe.

Why Safe Mode is the wrong test for this one symptom

Nearly every troubleshooting list tells you to boot into Safe Mode to see whether third-party software is to blame. For most Mac problems that is sound advice. For fans at full speed it is close to useless, and knowing why will save you an afternoon of confusion.

Safe Mode does not load the software layer that holds the fans down. On many Macs that means the fans go to maximum in Safe Mode regardless of whether anything is wrong, which is the same fail-safe behaviour described above rather than a fault. So the test has no readable outcome for this symptom. Loud fans in Safe Mode tell you nothing, because that is what Safe Mode does. Quiet fans in Safe Mode would be the surprise. Test with a full power-down instead, or with a second user account if you genuinely suspect something you installed, and keep Safe Mode for the problems it can actually answer.

Why a fan control app is the wrong fix for most of this

I make a Mac fan control app, so let me be direct about where it does not belong. If your fans are pinned at maximum because the firmware has lost a temperature reading, fan control software is not the answer and I would rather say so than sell you a workaround. It cannot repair a sensor. It cannot restore a reading the controller has lost. And no app can take a fan below its hardware minimum, so it has nothing to offer against a firmware fail-safe that is deliberately holding a fan at its ceiling. The machine is not misbehaving. It is protecting itself, and overriding that on a Mac which genuinely cannot read its own temperature would strip out the last safeguard it has. Several forum threads on exactly this symptom recommend reaching for a fan control app. That advice is how a sensor fault becomes a board fault.

There are two places where ChillBlades earns its keep on this page, and they are narrow. The first is answering the question at the top: it shows the hottest single CPU or GPU die reading, one number, polled every two seconds, which is exactly what you need to split fault from heat. Be aware of its limit, though, because it matters here. It shows one number and no sensor list, so it will tell you the chip is cool while the fans scream, which is the finding you want, but it cannot tell you which sensor failed. For that you need Apple Diagnostics and eventually a bench.

The second is the mundane case, once you have confirmed the chip really is hot. There ChillBlades does something useful: Custom mode gives each fan a slider across its real hardware range so you can hold a higher floor before a long export, and Auto Boost spins the fans up at a band you pick, Warm at 80°C, Hot at 90°C, or Very hot at 100°C, instead of waiting for the firmware's own late ramp. That is a genuine improvement on a machine whose cooling is saturated. It is not a repair, and it was never going to be.

About this guide

I am the maker of ChillBlades, a Mac fan control app, which means I spend more time than most people reading Mac fan and temperature behavior through the System Management Controller. Two things are worth separating. The product details here are first-hand: the single hottest CPU or GPU die reading, the two-second polling, the Custom sliders clamped to each fan's real hardware minimum and maximum, the three Auto Boost bands, and the fact that quitting the app cleanly hands every fan back to macOS. Those are how the app works, not a description of fan control in general.

The firmware side is different, and I would rather flag the boundary than blur it. Apple does not publish how its thermal management logic decides fan speed, so the fail-safe behavior described above is drawn from what Apple does document about fans and ambient temperature, from Apple Diagnostics reference codes, and from repair-bench accounts of machines with dead or disconnected sensors. It is a well-evidenced account of how these Macs behave, not a published specification, and I have tried to be clear about which is which. Your Mac protects itself regardless of what any app asks of it, and that is the right way round.

FAQ

Why is the iMac fan running at full speed?

On a desktop, the most common answer is a temperature sensor that is no longer being read, and the usual reason is a recent upgrade. An iMac has several sensors driving different fans, and the display panel carries one of its own. Take the panel off to reach the drive or the memory and that sensor gets unplugged from the logic board, so the fans can sit at high speed afterwards even though the part you actually replaced is seated perfectly. Third-party drives that do not provide the temperature reading the original one did cause the same thing. Check every connector you disturbed before you suspect anything else.

Why is my Apple Mac Pro fan running fast?

Split it the same way you would on a laptop: find out whether the chip is genuinely hot. A Mac Pro has a lot of cooling and a lot of things that can load it, so sustained fast fans during a render or a long compile are the machine working as intended. Fans at maximum on an idle, cool Mac Pro point instead at a reading the firmware cannot trust, and on a tower that usually means something disturbed during an upgrade: a card, a drive sled, or a fan whose speed feedback is no longer reaching the controller. A fan the controller cannot read is treated as a failed fan, and the response is to run the others flat out.

Why is my MacBook Air fan running all the time?

First check which MacBook Air you have, because several models have no fan at all and the noise you can hear is coming from somewhere else. On an Air that does have one, constant running at a moderate speed is usually a background workload, and Activity Monitor sorted by CPU will name it. Constant running at maximum is a different symptom and it is usually a fault, not a workload. If the machine is cool to the touch and the chip is reading in the thirties or forties while the fan is flat out, treat it as a sensor or controller problem rather than something you can close an app to fix.

Does resetting the SMC fix fans stuck at maximum on Apple silicon?

There is nothing to reset in the way there was on Intel. Apple silicon Macs still have a System Management Controller, and it still handles fan control and exposes the sensors, but Apple removed the user-invocable reset that Intel Macs had, so the key combinations you will find in older guides do nothing on an M-series machine. The equivalent is a full shutdown from the Apple menu, a pause of about thirty seconds with the machine genuinely off rather than asleep, then a normal power-up. That clears a stuck controller state if there is one. If the fans come straight back up to maximum on a cool machine, the state was not the problem and you are looking at hardware.

Can a fan control app fix fans that are stuck at full speed?

No, and I make one, so take that as it is meant. A fan control app cannot repair a sensor, cannot restore a reading the controller has lost, and cannot take a fan below its hardware minimum, so it has nothing to offer a fan the firmware is deliberately holding at maximum. Worse, if you did manage to quieten a Mac that has genuinely lost its temperature reading, you would be muting the only protection it has left. ChillBlades is useful here for one thing and one thing only: it shows you the hottest CPU or GPU reading, which tells you whether this is heat or a fault. Once you know it is a fault, the fix is a repair.