Short version: Betaflight will swap numeric versioning for year.month.patch labels and publish two major releases each year. The Configurator becomes a Progressive Web App (PWA).
TL;DR
From December, Betaflight will use date-based versions like 2025.12.0. Major releases will target June and December. The Configurator app will match firmware versions and move to app.betaflight.com as a PWA you can install for offline use.
Why this matters
Date-based labels tell you when firmware shipped at a glance. That helps pilots pick a build and helps the devs plan predictable releases.
Current (old) versioning
Today Betaflight uses major.minor.patch — for example 4.5.2. That shows feature series and fixes, but not the release date.
The new date-based scheme
From December the format will be YEAR.MONTH.PATCH. Example: 2025.12.0 where 2025 is year, 12 is month, and 0 is patch.
The team will aim for two major releases per year — June and December. Patches will increment the last digit for hotfixes inside the month.
Firmware and Configurator alignment
The Configurator app version will match the aircraft firmware version. That reduces confusion when picking a build in the dropdown.
Betaflight is replacing the old downloadable Configurator with a browser-based PWA at app.betaflight.com. The PWA keeps feature parity with the old app and stays up to date.
Installing the PWA for offline use
You can install the PWA to run offline. Open app.betaflight.com, click the browser install option (top-right or browser menu), and it behaves like a standalone app.
Examples and backward compatibility
Labels for past releases will not change — Betaflight will only use the new scheme going forward. The video shows how older numeric versions would map to the new names as an example.
So 4.5.2 would be shown as an example like 2025.5.5 in the graphic, but the old 4.5.2 tags remain in history.
Support and funding
Betaflight is open source. Mads points to PayPal and Patreon links in the Configurator donate area and on the project pages. Community funding keeps builds and infrastructure running.
FAQ
When does the new versioning start?
Start date: the rollout begins in December. The launch build will be 2025.12.0.
Will old versions be renamed?
No. Existing historic releases keep their numeric names. The new scheme applies only to future releases.
Does the Configurator stop being an executable app?
They replaced the traditional installer with a PWA at app.betaflight.com. You can install the PWA for local/offline use — it behaves like a native app.
How often will major changes land?
Two major releases per year: June and December. Minor patches occur as needed inside those month releases.
Conclusion
Betaflight moves to a simpler, calendar-based label and a predictable biannual cadence. The Configurator becomes a PWA and the app and firmware versions will align. If you run firmware labs, this makes life easier.
Takeaways:
Betaflight uses YEAR.MONTH.PATCH from December — first release 2025.12.0.
Two major releases each year: June and December — patches increment within the month.
The Configurator moves to app.betaflight.com as a PWA — installable for offline field use.
Credits
Source: Mads Tech's video "Betaflight New Versioning System Explained - Bi Annual Releases & PWA App". Visit app.betaflight.com for the web Configurator and the Betaflight PayPal/Patreon pages to support the project.
This article was based from the video Betaflight New Versioning System Explained - Bi Annual Releases & PWA App
