Download Smart Breeze 1.1.1.
Build 43 is signed, notarized, and packaged for Apple-silicon Macs running macOS 13 or later.
Current verified release
Smart-Breeze-1.1.1-43-macos-arm64.dmg
- Price
- Free. No account needed.
- Size
- ~5.1 MB DMG
- Architecture
- Apple silicon (arm64)
- Requires
- macOS 13+
- Notarized
- November 9, 2026 UTC
By downloading, you agree to the Terms. No account needed. Payment is only collected if you unlock fan control.
Unlock fan control
Sent here from the app? You already have everything you need. One payment unlocks fan control on the copy you downloaded, on fan-equipped Apple-silicon Macs. Your license key arrives by email. Enter it in the app under Settings, in the License tab, and fan control turns on. No second download.
$14.99 one-time. Up to 3 Macs. Free 1.x updates. No subscription.
Release authenticity
Gatekeeper accepted
- Developer ID
- 5UP5B7P45Q
- Notarized
- November 9, 2026 UTC
- App ticket
- Stapled
- DMG ticket
- Stapled
Check what Build 43 supports on your Mac.
Hardware qualification is enforced inside the app. The download confirmation does not unlock fan control.
Monitoring, Smart Boost, timed Max, custom curves, and Manual diagnostics. Fan hardware is detected live; models with no fans stay monitoring-only.
No fans to control. Temperature monitoring and the sensor explorer stay available.
This release contains arm64 binaries only.
Keep one copy in Applications.
- Open the DMG. Drag Smart Breeze.app into /Applications. If Breeze.app is already there, do not replace it in place and do not keep both copies.
- Retire the older Breeze.app. In the old app, select System, turn off login if it is on, quit, then move /Applications/Breeze.app to the Trash without emptying it.
- Open only Smart Breeze from Applications. Eject the DMG first. Review why the fan helper needs approval before enabling control.
Verify the download.
Check the file with SHA-256:
shasum -a 256 ~/Downloads/Smart-Breeze-1.1.1-43-macos-arm64.dmgBefore the download begins, the server checks the stored file's path, byte count, and content type against the release record, then streams the file. The SHA-256 above is verified when the release is staged and again after each deployment.