How to Update Betaflight Firmware Without Losing Your Tune

Betaflight 2026.6.2 is the current stable firmware, and a GPS freeze fix is waiting for 2026.12. Use this five-step routine for every update, patch or major release, so your settings come through safely.

By the FPV Drone Essentials editors · Build · Published October 7, 2026

Betaflight 2026.6.2 came out on September 16, 2026, and it is now the current stable firmware. It is a small patch with a single fix, carried back to the 2026.6 line, that protects I2C bus access when no bus has been assigned. The previous patch, 2026.6.1, came out on August 2.

Use the same routine for a one-fix patch like this one and for a major release, where much more changes. It has five steps: save a diff, read the notes, choose a release channel, flash the correct target, then restore and check everything before the first pack.

First, understand the new version numbers

Betaflight no longer uses 4.x numbering. It switched to calendar versioning, written as year, month and patch. The release after 4.5 was 2025.12.0, and 2026.6.0 came next. The plan is two major releases a year, one in June and one in December. Each one gets roughly a month as a release candidate under a feature freeze before it ships.

So the next major release should be 2026.12. As of October 1 it has no release candidate, and its timing is an estimate based on the June and December schedule, not a date the project has announced.

The desktop Configurator has been replaced by the Betaflight app. It runs in a web browser for stable firmware, and there are Android and iOS versions. Development builds live at a separate address. The app and the firmware now share a major version number, and matching versions are designed to work together. Use the 2026.6 app with 2026.6 firmware and skip the development app unless you are testing on purpose.

Step 1: Save a diff before you touch anything

According to Betaflight's flasher documentation, you should back up before any upgrade, either with a diff from the CLI tab or with the backup option in the Presets tab. A diff lists only the settings you changed from the defaults: your rates, PIDs, filters, ports, modes, OSD layout and everything else you set up. That short list is your tune.

The backup is important because a full chip erase clears the flight controller's stored configuration and loads factory defaults. Once you erase, the file on your computer is the only copy of your setup. Name it with the quad, the board, the firmware version and the date, and keep it somewhere other than your downloads folder.

Many older guides tell you to save both a full dump and a diff. Current docs focus on the diff and specifically warn against pasting the profile or master sections of an old dump into new firmware. Those sections contain every default from the old version, including ones the new version may have changed on purpose. If you set up your quad using our Betaflight First Setup guide, your diff is probably short and easy to read.

Step 2: Read the release notes and known issues

Read the notes before you flash. They tell you which settings changed meaning between versions, and those are the settings a restored diff can get wrong without any warning.

The 2026.6 release notes list several changes that matter on upgrade:

• thrust_linear: the same value you used before now gives a slightly different curve shape. If your tune depends on it, test before you trust it.
• Compass: the firmware uses a magnetometer for heading only after you opt in with trust_mag. If you fly GPS Rescue with a compass, see Betaflight GPS Rescue Setup: Do You Need a Compass?
• Autopilot and Flight Plan: labeled experimental and tested only in simulation. The notes call the underlying firmware not flight-ready, so leave it off on a quad you care about.
• ESP32 support: also labeled experimental.

A gyro can also be a reason not to restore your old tune. Oscar Liang's 2026.6 write-up recommends that anyone with an IIM-42652 gyro who moves to 2026.6 start from a reset tune and retune, instead of carrying over the old PID values. On those boards, restore the rest of the diff but leave out the PID lines.

The GPS freeze to know about right now

This is the most important known issue for anyone who has a GPS port set up. A researcher at YarosFPV traced a fault that can make a flight controller lock up in the air. The quad falls, the OSD stops updating, the flight controller ignores stick input, and it only recovers after a power cycle.

The cause, described in pull request #15685: if a UART is assigned to GPS and no module responds, the firmware keeps searching for a baud rate. It reconfigures the port about once a second and never stops. That repeated reconfiguration can collide with other work on the flight controller and freeze it.

The scope is still uncertain. The pull request says the freeze was reliably reproduced on F7 processors and may affect other types. The researcher's blog says Betaflight 4.4 and later are affected, with F7 and H7 boards most at risk, but that claim comes from the researcher and not from Betaflight's release notes. The problem only occurs when a GPS port is enabled and nothing answers on it.

The fix was merged on September 21, 2026, for the 2026.12 milestone. That was five days after 2026.6.2 shipped, so no stable release includes it, and no backport to 2026.6 has been confirmed. Until the fix ships, the workaround is simple: turn GPS on in the Ports tab only when a module is actually wired to that UART. If you remove a GPS module for a race build, turn the port off too. The researcher also advises against arming if GPS elements you expect in the OSD are missing before takeoff.

Step 3: Choose stable or release candidate

The flasher hides release candidates by default. To see them, you turn on Expert Mode and then the option to show release candidates. For a normal update, leave both off.

An RC exists so pilots can find problems before the final release. If you want to help, flash it on a quad you can afford to crash, and do not put it on the one you fly every weekend.

Step 4: Flash with the right target and options

Open the Betaflight app, plug in the quad, and go to the Firmware Flasher tab. Firmware is now built in the cloud from the board and options you select, so a correct target matters. The docs recommend clicking auto-detect and confirming that the correct board name appears. Do not guess from the box or an online listing.

If the board will not connect for flashing, put it into DFU mode. You can hold the boot button while plugging in, use the bootloader button in the Setup tab, or type bl in the CLI.

If you choose a full chip erase, remember what it does: every saved setting on the flight controller is replaced with defaults. The diff from Step 1 is what brings your setup back.

Step 5: Restore, then bench-test before the first pack

Reconnect the quad, open the CLI tab and paste in your diff. Before you do, read through it. Remove any lines the release notes flagged, such as PID values on an IIM-42652 board, and never paste the profile or master blocks from an old full dump.

Next, go through every tab. The docs are firm that each setting should be confirmed before a test flight. Check these in particular:

1. Ports: the receiver UART is correct, and GPS is enabled only if a module is connected.
2. Receiver: channels move the right way and the link is solid.
3. Modes: arm, beeper and any other switches trigger where you expect.
4. Motors: with props off, every motor spins in the correct direction.
5. OSD: your layout is back, including GPS elements if you fly with GPS.
6. Failsafe: the settings match your old setup.

Then fly one easy pack. Hover, make some gentle turns, and land to check motor temperatures before you push harder. If thrust_linear or a new gyro setup has changed how the quad feels, you will notice it here and not in the middle of a hard move.

If this is your first flash, the Installing Betaflight chapter of FPV Drone Essentials covers the app and flashing from the beginning, and the Finishing the build chapter explains the checks that come before a first flight.

Sources

• GitHub betaflight/betaflight releases
• GitHub betaflight/betaflight releases API
• Betaflight blog – Calendar Versioning Change
• Betaflight docs – Firmware Flasher Tab
• Betaflight 2026.6 Release Notes
• Oscar Liang – Betaflight 2026.6
• GitHub betaflight PR #15685
• YarosFPV blog (researcher who filed the PR)

Facts checked against the sources above as of October 1, 2026. Drone rules and firmware change; check the current version before you rely on a detail.