What happened

FanBar, a free and open-source fan control app for the Mac menu bar, released version 0.6.3 on October 19, 2026. FanBar is a small independent project, not a household name yet: its public GitHub repository shows 84 stars, 304 commits, and 22 releases since it appeared in August 2026. Version 0.6.3 is its latest release, published with full release notes on the project's own site.

The 0.6.3 release adds a redesigned menu panel that states which app or system currently controls the fans, a CSV log that records temperatures, fan speeds, and the active control mode over time, a configurable sound for high-temperature alerts, and French language support. It also fixes temperature accuracy on two fronts: Intel Macs now read per-core sensors instead of a proximity sensor that read low, and Apple Silicon Macs where no SMC temperature is readable, such as some M1 models on macOS 27, now read CPU and GPU temperatures from HID sensors instead.

FanBar covers the same ground as established tools like Macs Fan Control and TG Pro. It monitors CPU, GPU, SSD, and battery temperatures, shows live fan RPM, and offers six cooling modes: Automatic (macOS stays in control), a fixed target RPM, and Silent, Balanced, Performance, and Extreme preset curves. Each preset curve is editable. It runs on macOS 11 Big Sur and later, on both Apple Silicon and Intel Macs, and it is distributed as a notarized build through GitHub Releases and Homebrew. The full source code, including its privileged helper, is public under the GPL-3.0 license.

Sources: FanBar 0.6.3 release notes, FanBar official site, FanBar on GitHub.

What it means for your Mac's thermals

A new entrant does not change how your Mac cools itself. macOS still runs the fans by default, and it still protects the chip by slowing it down if temperatures keep climbing. What a release like this changes is the set of tools you can choose from when you want to see temperatures yourself or ask the fans to start earlier than macOS would on its own.

Two details in this release are worth understanding, because they apply to every fan app, not just FanBar.

First, temperature readings are only as good as the sensor an app can reach. On some M1 Macs running macOS 27, the usual SMC temperature readings are not available, so FanBar 0.6.3 falls back to HID sensors for CPU and GPU temperature. If a monitoring app ever shows blank, frozen, or implausible temperatures after a macOS update, the app has usually lost access to a sensor, not found a fault in your Mac. Check for an app update before you assume a hardware problem. Our guide to unavailable temperature readings walks through how to tell the difference.

Second, every fan control app needs a privileged helper to change fan speeds, and the safety question is what that helper is allowed to do. FanBar's design states the boundary plainly: the helper runs as root but can only read fan state and set a bounded target within each fan's reported hardware range, with no arbitrary SMC writes. Presets and fixed speeds can expire back to Automatic after 15 minutes, 30 minutes, or an hour, and the app restores macOS automatic control when it quits, loses its connection, or the control service fails. That pattern, bounded writes plus automatic handback to macOS, is the standard you should hold any fan app to. Our guides on whether Mac fan control is safe and why notarization matters for fan apps explain how to check both before you install.

There is also an honest trade-off to note. FanBar's own release notes say that keeping its animated menu bar icon spinning uses about 3 percent CPU on a Mac mini. A monitoring tool should never become a heat source itself, so if you try it, turn the icon animation off in Settings, Appearance, and confirm the app is quiet in Activity Monitor.

Practical takeaways

  • Treat FanBar as a new option to evaluate, not a reason to switch on day one. It is at version 0.6.3 and its public following is still small. The established comparison in our best Mac fan control apps guide for 2026 still stands.
  • If you try any new fan app, start in its monitoring-only mode. Watch temperatures and RPM for a few days before you approve the helper and change any fan behavior.
  • Prefer apps that clamp fan targets to the hardware range and hand control back to macOS automatically when they quit. Avoid any tool that cannot explain what its helper can and cannot do.
  • After any macOS update, update your fan app too. Sensor access can change between macOS versions, and stale readings after an update usually mean the app needs an update, not that your Mac is overheating.
  • Keep macOS Automatic as your default for everyday work. Use manual modes or earlier curves for a specific sustained job, like a long export or build, then return control to macOS when the job finishes.

Official sources

Sources

Smart Breeze documents its safety limits and supported Macs, so you can hold every fan app to the same standard. Download Smart Breeze