Your MacBook Fan Says 0 RPM. Is It Dead—or Resting?

Zero RPM is normal on many modern MacBook Pros and inevitable on a fanless MacBook Air. The useful test is whether fan speed responds when temperature rises.

By CoreGuard · Jul 11, 2026 · 12 min read

What does 0 RPM mean on a MacBook?

A MacBook fan reading of 0 RPM means either the Mac has stopped an installed fan, the Mac has no fan, or the fan-speed signal is unavailable. By itself, 0 RPM does not prove that a fan has failed.

That last distinction matters. RPM is a live measurement, not a hardware verdict. It tells you what the monitoring path reports now. It does not tell you, without context, whether a motor exists, whether macOS intentionally stopped it, or whether the tachometer signal has gone missing.

The useful question is not “Why is this number zero?” It is:

When the Mac gets warmer under sustained work, does fan speed respond appropriately?

Before testing that, establish whether your Mac actually contains a fan.

MacBook Air with Apple silicon → fanless; stop investigating RPM
MacBook Pro or an older Intel Air → fan hardware exists; continue
Unknown model → identify it before interpreting the reading

Use Apple menu → About This Mac, or run:

system_profiler SPHardwareDataType |
  egrep 'Model Name|Model Identifier|Chip|Processor Name'

Apple explicitly called the M4 MacBook Air a “fanless design” in its March 5, 2025 launch material. Apple-silicon MacBook Air models beginning with M1 use passive cooling rather than an internal fan. A utility may therefore show no fan, N/A, a blank field, or 0 RPM depending on how it represents absent hardware.

A fanless Air cannot have a dead fan. It can still get warm and reduce performance under sustained work, but that is a different thermal question.

Why a MacBook Pro fan can sit at 0 RPM

Modern MacBook Pro cooling is demand-driven. When the machine is cool enough, the hardware can stop its fan or fans completely instead of maintaining an arbitrary minimum speed.

Tunabelly Software’s TG Pro support FAQ, checked July 11, 2026, reports that on M4, M4 Pro, and M4 Max Macs the hardware may turn the fans off entirely. Its older 0-RPM FAQ documents hardware-off behavior on specific Intel MacBook Pro and Intel MacBook Air models and ties that behavior to low temperatures.

Apple describes the broader mechanism in its May 27, 2026 support article: internal sensors respond to temperature changes, and fans run faster during processor-intensive work. Apple also says ambient temperature affects when fans respond.

That gives us the healthy-idle pattern:

• fan-capable Mac;
• light workload;
• low or stable temperatures;
• 0 RPM;
• no grinding, clicking, thermal warning, or unexpected shutdown;
• fan speed rises later if sustained work raises temperatures enough.

Nothing in that pattern needs intervention. Silence is part of the design, not evidence that Apple forgot the fan.

There is also no universal temperature at which every MacBook Pro must start its fan. The curve varies by model, workload, ambient conditions, power mode, and which internal component is producing heat. Anyone handing you one magic temperature is compressing a control system into a meme.

Run a temperature-correlated ramp test

A proper fan test needs two live signals: temperature and RPM. One without the other is mostly gossip.

First, restart the Mac. Apple’s May 27, 2026 fix list for unexpectedly fast fans on Apple silicon includes a restart, and it is sensible test hygiene here too. Put the laptop on a hard, flat surface with unobstructed vents; Apple recommends the same placement for normal airflow.

Open a monitor that shows live internal temperatures and fan RPM together. Record the idle state:

• Is the temperature stable, rising, or already high?
• Does the fan field say 0 RPM, N/A, missing, or sensor unavailable?
• Can you hear airflow or mechanical noise?
• Is the Mac doing background work such as Spotlight indexing?

Then apply a sustained, ordinary workload: a code build, video export, game, or other task you already trust. If you need a reproducible CPU-only load, open a fresh Terminal window and use this supervised test:

pids=""
for i in $(seq 1 "$(sysctl -n hw.logicalcpu)"); do
  yes > /dev/null &
  pids="$pids $!"
done

# Watch temperature and fan RPM in your monitor.
# Stop the load with:
kill $pids

This command creates CPU work and discards its output into /dev/null; it does not modify your files. Keep the Mac in sight. Stop immediately if you see a temperature warning, smell anything unusual, hear grinding or repeated clicking, or the Mac becomes unstable.

Do not force a fan speed during the test. That replaces the behavior you are trying to observe. The diagnostic signal is macOS and the hardware deciding to ramp the fan as temperature rises.

Watch the relationship, not a single sample:

temperature stable + fan 0 RPM
    → consistent with healthy idle

temperature rises + fan later rises above 0 RPM
    → cooling response exists

temperature rises, then stabilizes while fan stays at 0 RPM
    → may still be normal on an efficient or lightly loaded Mac;
      repeat with a genuinely sustained workload

temperature keeps climbing + fan never responds
    → stop the load and investigate

audible fan airflow + displayed 0 RPM
    → fan motor is moving; the reading path is wrong

The test does not need to turn your Mac into cookware. You only need enough sustained work to see whether temperature and fan speed behave as a system.

The healthy result is a curve, not a number

I trust a sequence more than a screenshot.

A healthy fan-capable Mac may begin at 0 RPM, stay there while temperature rises modestly, then ramp smoothly once the hardware decides airflow is useful. When the work ends, temperature should fall and fan speed should eventually fall with it. The response can lag; metal, heat pipes, and internal sensors have thermal inertia.

A suspicious result is not merely “still zero.” It is a broken relationship between load, temperature, and cooling response.

For example:

• At idle, temperature is stable and the fan is stopped: reassuring.
• Under sustained load, temperature rises and the fan begins moving: reassuring.
• Under sustained load, temperature keeps rising, performance collapses, and the fan remains stopped: suspicious.
• The fan grinds, clicks, pulses, or repeatedly tries to start: mechanical evidence worth servicing.
• The chassis is cool but one app shows an impossible or frozen sensor value: suspect the reading before the hardware.

Run the test once after a restart and, if possible, cross-check the fan reading with a second monitoring tool. A stale helper, unsupported sensor map, or recently released Mac model can produce a convincing-looking zero that is really “I do not know.”

When 0 RPM is a tachometer problem

A fan has at least two relevant paths: power makes the motor turn, while a tachometer signal reports its speed. Those paths can disagree.

If you can clearly hear or feel steady airflow but the monitor reports 0 RPM, the motor is not stopped. Possible explanations include a failed or disconnected tachometer path, a monitoring app that does not understand the model, stale sensor data, or the wrong fan being displayed on a multi-fan Mac.

Treat this as a telemetry problem until you have more evidence:

1. Restart the Mac.
2. Check whether another monitoring tool reports the same fan.
3. Watch whether the displayed value ever changes during a supervised load.
4. Run Apple Diagnostics.
5. If the mismatch persists, give the exact observation to a technician: “The fan audibly spins, but RPM remains zero across two monitors.”

That sentence is much more useful than “my fan is broken.” It separates the motor from the feedback signal.

The opposite case is more urgent: no airflow, no RPM, rising temperature, and no fan response under sustained load. Stop repeating the test. You already collected the useful evidence.

When it is actually a service problem

I would arrange hardware service when one or more of these signals survive a restart:

• A fan-capable Mac never ramps during sustained work while reported temperatures continue rising.
• The fan grinds, clicks, scrapes, pulses, or repeatedly attempts to start.
• The fan audibly spins but multiple monitors continue to report 0 RPM.
• The Mac shows temperature warnings, thermal shutdowns, or severe repeatable instability alongside the missing fan response.
• Apple Diagnostics returns a fan-related reference code.

Apple’s current Diagnostics reference, published December 15, 2025, assigns PPF001, PPF003, and PPF004 to “There may be an issue with the fan” and directs the user toward Apple or an authorised service provider.

Those codes do not identify the exact failed part. They also do not justify ordering a random fan before inspection. A cable, sensor path, obstruction, motor, connector, or board-level fault can present as “fan issue.” The code narrows the subsystem; it is not a parts invoice.

Back up important data before service. Do not keep cooking the machine to collect a more dramatic graph. Hardware evidence does not become more scientific when accompanied by smoke.

Run Apple Diagnostics, then respect its limits

Apple’s December 19, 2025 instructions say to disconnect external devices except those needed for the test, shut down the Mac, and start Apple Diagnostics using the model-appropriate method.

On Apple silicon, hold the power button until startup options appear, then press Command-D. On an Intel Mac, turn it on and immediately hold D; Apple lists Option-D as a fallback. Follow the onscreen instructions, which Apple says vary by Mac model and macOS version.

Write down every reference code before leaving the results screen.

A PPF001, PPF003, or PPF004 result is direct service evidence. An ADP000 “No issues found” result is useful but not omniscient. Apple describes Diagnostics as helping determine which hardware component might be at fault—a hardware-scope check—and an intermittent fan or tachometer fault may behave normally during a short test.

That is why I keep the correlation test in the workflow. Diagnostics is one observation. Temperature, load, RPM, sound, and repeatability are the rest of the case.

What software cannot tell you

No monitor can inspect a bearing through software. RPM data can show motion, absence of motion, or a missing signal. Temperature data can show whether heat is rising. Neither can identify dust, physical damage, or a loose connector with certainty.

Sensor access also varies between Mac models. A missing field may mean unsupported telemetry rather than missing hardware. Newly released Macs sometimes arrive before third-party tools have reliable sensor mappings.

Do not diagnose from one number, and do not compare your MacBook Pro’s idle RPM with a screenshot from another model. The honest unit of evidence is the pattern on your machine:

known model + known workload + temperature trend + fan trend + sound + Diagnostics result.

That bundle is usually enough to distinguish “quiet by design” from “book a service appointment.”

How CoreGuard handles the observation

This is the exact problem I want CoreGuard to make boring.

CoreGuard shows live fan RPM beside live temperatures on Apple-silicon and Intel Macs. The separating observation—does the fan ramp when temperature climbs?—is available in Free, along with basic reading history, threshold alerts, the menu-bar readout, and every danger warning. You do not have to pay to learn that something may be wrong.

Pro adds CSV/JSON sensor-log export, useful when you want to preserve the sequence for a technician. The live danger signal remains free. This diagnosis does not require changing fan behavior, and I would not change it while testing.

CoreGuard is local-only and makes zero network connections. It observes and explains; it never cleans, optimizes, speeds up, or repairs the Mac. Its current requirements are macOS 13 or later, with support for Apple silicon and Intel, and builds are Developer-ID signed and notarized by Apple.

The app is pre-launch. You can get notified when it is available or inspect the pricing page; the useful test in this article works without it.

The answer in one line

If your MacBook Air has no fan, stop looking for one. If your MacBook Pro reports 0 RPM, watch temperature and RPM together under supervised load: a correlated ramp is healthy evidence; rising heat with no response, mechanical noise, a dead tachometer signal, or a PPF fan code is service evidence.

Frequently asked questions