Mac fan not spinning? How to tell if it is actually broken

A fan reading zero RPM looks like a failure and usually is not. Modern Macs stop their fans completely when the machine is cool enough, which is a feature. The problem is that a healthy stopped fan and a dead fan look identical from the outside, and the way to tell them apart is to give the machine a reason to spin up.

First, confirm there is a fan

Every Apple Silicon MacBook Air is passively cooled and has no fan at all. So is the base model 24-inch iMac in some configurations, and the Mac Studio and Mac Pro have fans that idle so low they are inaudible in a normal room. If a monitoring app reports zero fans rather than one fan at zero RPM, there is nothing wrong. The model-by-model list is the quickest way to check.

The test: give it something to do

Load the machine and watch whether the fan responds. Anything sustained works: export a video, run a long compile, or open Terminal and run a few instances of yes > /dev/null to saturate cores, then close them with Control-C. Give it three to five minutes. The firmware controller is deliberately slow to react, so a fan that is still at zero after thirty seconds tells you nothing.

Then read the outcome:

• Temperature rises, fan RPM rises. Everything is working. The fan was idle because the machine was cool.
• Temperature rises past 95 °C, fan stays at zero. This is the case that suggests a real fault, either the fan itself or its connector.
• Fan RPM reports a number but you hear nothing. Likely fine. A fan at 1200 RPM in a MacBook Pro is genuinely close to silent.
• RPM reading is erratic, jumping between zero and a value. Consistent with a failing bearing or a tachometer that has stopped reporting reliably.

Zero RPM versus no reading at all

These are different findings and worth distinguishing. A fan reporting 0 RPM is a fan the system can see and is choosing not to spin. A fan that reports no value, or that disappears from the sensor list entirely, is one the system cannot talk to. The second is much more likely to be a hardware or connector problem, and it is the one worth taking to a technician.

Any monitoring tool will show you this distinction, including the built-in powermetrics command, which needs nothing installed.

Driving the fan directly

There is a more direct test, which is to command the fan to a speed yourself and see whether it obeys. If you set a fan to a mid-range RPM and the reported speed moves to match, the fan and its controller are both fine and any earlier stillness was the firmware’s choice. If you command it and nothing changes, that is a much stronger signal than any amount of waiting.

This is what manual fan controldoes, and it is the one diagnostic that distinguishes “not spinning” from “not working” without opening the machine. Breeze clamps any speed you ask for into the minimum and maximum the fan itself reports, and hands the fan back to firmware control when you quit, so the test is reversible by design. Reading the sensors, including live RPM, is free; commanding a speed is the paid half.

If it spins but sounds wrong

A grinding, rattling, or cyclical ticking noise usually means the bearing is failing or something has found its way into the blades. This gets worse, never better, and a fan that seizes in a machine under load is a genuinely bad outcome. Worth booking a repair rather than monitoring.

A fan that is simply louder than it used to be at the same workload is more often dust in the heatsink fins than a fan problem. The fan compensates for reduced airflow by working harder, so the noise is a symptom of the blockage rather than of the fan.

What a healthy machine looks like

Fans at zero when idle, rising smoothly under sustained load, falling again afterward, and each fan reporting a plausible RPM within the range its own hardware advertises. If that is what you see, the stillness you noticed was the machine being quiet on purpose, which is most of what its thermal design is trying to achieve.