Fan control on a Mac: what you can set, and what you cannot

Searching for fan control on a Mac usually follows a specific moment: a machine that has been silent for months starts sounding like a hairdryer while doing something unremarkable, and the obvious response is to look for a slider. macOS does not have one. There is no fan pane in System Settings, and the Mac User Guide has no page about setting fan speed, because setting fan speed is not something Apple exposes.

What does exist is worth separating into three layers, because conflating them is how people end up either installing something they did not need or forcing a fan to a speed that makes things worse. There is what macOS provides, there is what a third party tool can do, and there is the question of why the fan is spinning at all, which is usually the only layer that matters.

What macOS actually gives you

The nearest thing to a fan control in System Settings is an energy setting, and Apple describes its effect on noise directly.

Low Power Mode: Reduce energy usage for computers that are always on (such as those used as servers) and fan noise for environments and tasks that require minimal noise. Source: support.apple.com, read September 27, 2026

That is an indirect lever and an effective one. It reduces the work the machine does, which reduces the heat, which reduces the fan speed. It does not address the fan itself.

On a laptop the same idea appears with more granularity, as a three way choice that can differ between battery and mains power.

Energy Mode: Choose which energy mode you want your Mac to use while on battery power or plugged into a power adapter. Low Power: Reduce energy usage to increase battery life. Automatic: Have your Mac automatically use the best performance level. High Power: Increase energy usage to improve performance during sustained workloads. Source: support.apple.com, read September 27, 2026

The pair is the real control surface. High Power exists precisely so that a sustained workload can run faster and louder, and Low Power exists so that the same machine can run slower and quieter. Setting Low Power on battery and Automatic on mains power is a reasonable default for anyone who works in quiet rooms and occasionally renders something.

There is nothing else. No minimum speed, no curve, no target temperature.

What a third party tool adds

Tools exist that read the sensors and write fan speeds directly. The most established one on the Mac states its scope on its own site.

Real-time monitoring of fan speeds and temperatures. Solve overheating problems like those found on a MacBook Pro. Works on all Macs, both Intel and Apple Silicon. Source: crystalidea.com, read September 27, 2026

Two modes are offered per fan, and understanding the difference is the whole safety question.

Auto: a fan is controlled by the system automatically (Apple's default scenario). When all fans are controlled automatically by the system the app works in monitoring-only mode. Custom: a fan is controlled by the app. Can be either some constant RPM value (e.g. 1500 RPM) or sensor-based control (e.g. in relation to CPU PECI sensor). Source: crystalidea.com, read September 27, 2026

A constant speed and a sensor based rule are not the same kind of setting. A constant value takes the fan out of the feedback loop entirely, which is fine for raising a floor and dangerous for setting a ceiling. Sensor based control keeps the loop but moves the curve, so the fan still responds to heat and simply responds sooner or later than Apple intended.

The same page states what happens when the tool is not running, which is the detail worth checking about any tool of this kind.

When Macs Fan Control quits, it always restores all fans back to Auto (Automatic preset). Source: crystalidea.com, read September 27, 2026

That behaviour is the difference between an experiment and a commitment. A tool that leaves a forced speed in place after quitting has effectively changed the machine, while one that restores the automatic mode has only borrowed it.

Raising a floor is safe, lowering a ceiling is not

The two things people want from fan control pull in opposite directions, and only one of them is low risk.

Goal	How it is done	Risk
Fans spin up earlier during long workloads	Sensor based rule, or a constant speed above the idle default	Low. More noise, cooler components
Fans stay quiet during light work	Constant speed below what the system would choose	High. Heat has nowhere to go if the workload changes
Fan noise reduced overall	Low Power Mode, closing the process causing the heat	None
Noise from a replaced drive or a failing bearing	Sensor based rule tied to the relevant sensor	Low, but treats a symptom

The asymmetry is physical rather than a matter of opinion. A fan asked to run faster than necessary wastes some power and some quiet. A fan pinned below what the thermal system wants leaves the machine with one response left, which is to reduce its own speed until the heat fits the cooling available. That is not a failure mode that announces itself. It looks like a Mac that has become slow.

Anyone tempted to pin a low speed for quiet is usually better served by the setting Apple ships for that purpose, because reducing the work produces silence without removing the safety margin.

Find the process before touching the fan

A fan running hard is a report, not a fault. In most cases something is asking for continuous work, and the fan is the only visible sign of it.

Activity Monitor answers this in about a minute. The CPU tab sorted by processor share names whatever is busy, and the Energy tab names whatever has been busy over a longer window, which catches a process that spikes rather than pegs. The usual suspects are repetitive: a browser tab running a video call or an animation, a sync client indexing a large folder, a photo library rebuilding thumbnails, a backup running for the first time, or a build tool that finished its work but left a process behind.

Some of those resolve themselves given time. A first backup, a first photo library index and a first full sync are all finite, and forcing fans faster to sit through them is reasonable while forcing them slower is not. Others never finish on their own and simply need the app closed.

Two physical checks are worth the time before concluding that software is to blame. A Mac on a soft surface has its intake or exhaust blocked, which raises temperatures without any change in workload, and a machine several years old accumulates dust in the exhaust vents that has the same effect. Both produce the pattern of a Mac that got louder gradually with no change in how it is used.

Presets, and why switching beats one permanent rule

One setting that suits every activity does not exist, which is why the established tools offer named sets rather than a single configuration.

For convenience the app features fan presets that let you quickly put your fan(s) to either Auto or some Custom mode depending on your activity. Source: crystalidea.com, read September 27, 2026

This is the shape a sensible setup takes. One preset leaves everything automatic and is the one in use almost all of the time. A second raises the fans early and is switched on deliberately before a long export, a long build or a long call. Switching back is a click, and because the automatic preset is the resting state, forgetting to switch back costs nothing.

The alternative, a single custom rule left in place permanently, is what produces the two complaints people report about these tools. A Mac that is now always slightly audible, or a Mac that is quiet and slower than it used to be. Both are the result of treating a situational adjustment as a permanent setting.

Sensor choice matters in the same way. A rule tied to a processor sensor reacts to computing work, which is what most people want. A rule tied to a drive sensor reacts to disk activity, which is the right choice for the specific case the tool's own site mentions, an internal drive replaced by hand whose temperature the original thermal profile does not read. Picking the sensor that matches the actual complaint is the difference between a rule that helps and a rule that simply makes the machine louder.

One more reason to prefer presets over permanence: the workload that prompted the search is often temporary. A first backup, a library rebuild or a one off render all end, and a rule set during one of them outlives the reason for it.

Keeping the numbers visible

Anyone who cares about fan speed ends up wanting the temperature and the speed on screen permanently, because a number that has to be looked up is a number that gets looked up too late. That means the menu bar, and the tool mentioned above offers it.

Configurable menu bar display: Options to display fan speed and sensor temperature. Source: crystalidea.com, read September 27, 2026

A live readout in the menu bar is genuinely useful, and it is also the point at which the strip starts to run out. A numeric readout is wider than an icon, and two of them, a speed and a temperature, take up as much room as several ordinary status icons. Apple's own controls trim the built in items only.

Toward the right end of the menu bar are items (sometimes called status menus), typically represented by icons, that let you check the status of your Mac (such as the battery charge) or customize features (such as keyboard brightness). To rearrange status menus, press and hold the Command key while you drag an icon. Source: support.apple.com, read September 27, 2026

The Menu Bar pane in System Settings switches Wi-Fi, Bluetooth, Battery, Focus and the rest on or off, and Control Center holds items that do not need a permanent place. Neither can keep a third party readout reachable while taking it out of the visible row, which is where a tool that hides menu bar icons on a Mac comes in. The distinction worth checking is whether a hidden item can still be clicked in place, because a temperature readout that has to be unfolded before it can be read defeats its own purpose. The comparison page sets out which tools behave that way, and the pricing page covers what the paid tiers actually add.

What to change first

Open Activity Monitor and sort by CPU before installing anything, because a named process explains most cases and closing it is faster than any fan rule. If the workload is genuinely constant and the noise is the problem, set the energy mode rather than the fan, and reserve a third party tool for raising a fan curve rather than capping it. If a temperature readout ends up in the menu bar and the strip runs out of room, Koffret keeps it reachable.