Mac fan won't ramp up, even near 100°C — here's why

You're rendering, compiling, or running a benchmark. Activity Monitor or a tool like istats shows the CPU climbing past 90°C, pushing toward 100°C, and the fan barely reacts — maybe it picks up a little, nowhere near what the temperature would suggest. It feels like the fan is broken. It almost certainly isn't.

Why 100°C isn't the emergency it sounds like

Apple Silicon chips are rated to run safely at sustained junction temperatures near 100°C — that's inside their designed operating range, not a fault condition. macOS's automatic fan curve is tuned around that: it's built to keep the machine quiet through normal and even heavy loads, and it treats high SoC temperature as expected behavior under sustained work, not something to react to aggressively. On an older Intel Mac, a fan hitting 100°C would usually mean something was wrong. On Apple Silicon, it mostly means the chip is doing exactly what it's designed to do, and Apple has decided that's not worth the noise of spinning the fan harder.

What actually suffers isn't the hardware — it's your performance

The real cost of that conservative curve is thermal throttling: when the SoC sits at the top of its temperature range for long enough, macOS quietly lowers the CPU clock to bring it back down, and your render, compile, or export slows down without any warning on screen. That's usually the actual complaint behind "the fan won't ramp up" — not a safety concern, but a performance one. More airflow, sooner, keeps the clock higher for longer.

Making the fan react before macOS decides to

Apple's own curve isn't configurable — there's no setting anywhere in macOS that changes how eagerly it spins up. The only way to get ahead of it is a temperature-based rule that isn't Apple's: set a target of your own (say, 70°C instead of whatever macOS is quietly waiting for) and the fan ramps as soon as that's crossed, before throttling kicks in. FanFan Control's automatic rules do this by sensor temperature or by which app is running in the foreground — a render app can trigger a more aggressive curve automatically, and switching back to something light lets it settle down again.

The one thing you're not overriding here is Apple's own safety margin: above 95 °C, every fan snaps back to fully automatic within three seconds, no matter what mode or rule was active, and that failsafe can't be turned off, license or not. Your own rule is meant to act well before that point — the point is to never need the emergency behavior in the first place.

Not the same problem?

If instead your fan sits at a fixed low RPM even under light load and won't come down no matter what, that's a different, simpler issue — see Mac mini M4 fan stuck at 1000 RPM.

Any questions?

Write to soporte@fanfancontrol.com and I'll answer myself.