How to flash and update Betaflight firmware in the App 2026.6

New Betaflight firmware goes onto your flight controller (FC) through the “Firmware Flasher” tab of the Betaflight App: detect the board, pick the version and build options, flash. Here is every step for the App 2026.6, which options are included by default, what “Full chip erase” and DFU mode mean, what’s different after the update and what to do about common errors. Checked against the source code of the App and firmware 2026.6.2, the Betaflight docs and Betaflight’s build server, as of November 12, 2026.

Before you flash

The firmware installation docs start with a brake: “Resist the urge to flash your flight controller with the latest firmware right away. If it is a pre-built drone, the manufacturer has likely pre-configured it with the correct settings, and flashing will wipe all of that.” So connect and look first, then decide. If you flash:

  • Back up your settings: with diff all in the CLI tab, as described in Betaflight backup with diff all. By default the App also makes its own backup before flashing and asks where to save it, but only when the FC is connected normally over USB, not in DFU mode (useFirmwareFlashing.js).
  • Latest App: that’s the first preparation step in the flasher docs. On November 12, 2026 that’s version 2026.6.2, in the browser at app.betaflight.com or as a program.
  • Browser and cable: to flash, the browser App needs WebUSB, so use Chrome or Edge; Firefox can’t flash in DFU mode. Plus a USB cable that carries data. More in Betaflight not connecting.
  • Internet: the board list, versions and the finished firmware come from the build server build.betaflight.com (BuildApi.js).

This is only about Betaflight on the FC: according to the docs, the tab is used to update the flight controller’s firmware. ESC firmware such as Bluejay or AM32 is flashed with its own tools; on its ESC Firmware page the documentation names ESC Configurator. The firmware of an ELRS receiver on a serial port doesn’t belong here either; an ELRS receiver right on the FC (SPI), on the other hand, runs as part of Betaflight, more on that below.

Firmware Flasher, step by step

The App only shows the “Firmware Flasher” tab while it’s not connected (sidebar_items.js). Since 2026.6 it has two sub-tabs, “Board & Build” and “Flash” (2026.6 release notes).

  1. Plug in: connect the FC to your computer over USB and select it in the device list at the top, but don’t click “Connect”. If it isn’t in the list the first time in the browser, the entry “--- I can’t find my USB device ---” helps.
  2. Board: “Firmware Flasher” tab, “Board & Build” sub-tab, click “Detect”. The App connects briefly, reads the FC’s board name (board_name) and picks the board with that name from the list (AutoDetect.js). The log then says “App has successfully detected and verified the board: …”. Above the selection the App shows whether Betaflight has reviewed the board (“✅ Verified Partner”) or whether only the manufacturer or the community supports it. Without “Detect” you type the name into the “Search for a board...” field; the commands below this list show which one it is.
  3. Version: the App selects the latest stable version (FirmwareFlasherTab.vue). Release candidates only appear after you switch on “Show release candidates” and choose “Release And Release Candidate”, development builds only in expert mode and with a warning you have to confirm.
  4. Build Configuration: check Radio Protocol, Telemetry Protocol, OSD Protocol, Motor Protocol and “Other Options”, see Build options.
  5. Build it: click “Load Firmware [Online]” at the bottom. The build server builds the firmware, the App shows the build status with a ring and a “Show Log” link and switches to the “Flash” sub-tab.
  6. Flash: click “Flash Firmware”. By default the App first backs up your settings with diff all and asks where to save the file. Then it checks that the board name matches the board you picked, reboots the FC into the bootloader by itself and flashes (webstm32.js). The status goes through erasing, flashing and verifying to “Programming: SUCCESSFUL”. Don’t unplug in between.
  7. Afterwards: the FC reboots. If there was a backup, the App offers a “Restore Backup” button. Whether to use it is covered in What’s different after the update.
# Target quad: <name of your quad>
# both commands only print, they change nothing
board_name
version

board_name on its own only shows the board name, version prints the firmware version with target and board name (cli.c). The CLI needs a connection, so disconnect again before you go to the Firmware Flasher.

Build options: what’s included by default

Since Betaflight 4.4 the build server builds the firmware for your board, with exactly the parts you select. The Build Options docs give the reason: “Flash memory on a flight controller is limited. Thus, the firmware does not contain all parts at the same time. You select the parts that you need before you flash the firmware.” What the App preselects without “Detect”, according to the build server for version 2026.6.2 on November 12, 2026:

Selected by defaultAdd if you need it
Radio Protocol (one)
CRSF, for Crossfire and ExpressLRSFPORT, GHOST, IBUS, JETIEXBUS, MAVLINK, PPM, SBUS, SPEKTRUM, SRXL2, SUMD, SUMH, XBUS
Telemetry Protocol (one)
“Automatically Included” with CRSF, FPORT, GHOST and JETIEXBUSFRSKY_HUB, HOTT, IBUS EXTENDED, LTM, MAVLINK, SMARTPORT, SRXL
OSD Protocol (one)
none, the App asksAnalog, Digital, FrSky
Motor Protocol (one)
DSHOTBRUSHED, MULTISHOT, ONESHOT, PROSHOT, PWM
Other Options (several)
Acro Trainer, GPS, LED Strip, Optical Flow, Pin IO, Range Finder, VTXAKK (SA FIX), Altitude Hold, Batt. Continue, Cam. Control, Chirp, Dashboard, EMFAT (AutoRun, Icon), ESC Serial (SK) inc. 4way, Flight Plan, LED Strip (64), Magnetometers, Position Hold, Race Pro, Servos, Soft Serial, Wing
Custom Defines (expert mode only)
emptynames without USE_, such as ELRSV4 or BLACKBOX

If you click “Detect” first, the App adds the options of your current firmware to the preselection, for firmware from Betaflight 4.5 on (MSPHelper.js). According to the code, the radio protocol still stays on CRSF unless you picked a different one in the flasher before, which the App remembers (FirmwareFlasherTab.vue). So check every field. The list comes from the server and, according to the docs, can change between releases.

  • OSD: “Analog” is the OSD through the MAX7456 chip for analog video, “Digital” the OSD for HD systems through MSP DisplayPort (Build Options). If none is selected, the App asks before it builds.
  • Chirp: you add the chirp mode for the App’s Autotune tab yourself, see Does Betaflight have autotune?.
  • Blackbox: according to the docs, boards with a flash chip or an SD card already have it. Only for logging to a serial device do you enter BLACKBOX under “Custom Defines”.
  • ELRS on the FC (SPI): the default is ELRS 3. If your transmitter runs ELRS 4, enter ELRSV4 under “Custom Defines” in expert mode (2026.6 release notes, Build Options).
  • “Core Only”: according to the App it builds firmware with only the hardware drivers, to detect the hardware. Functions you need for flying are missing then.

Full chip erase: what it does and when to turn it off

The App describes the option “Full chip erase” as “Wipes all configuration data currently stored on the board.” The flasher docs are more precise: “Full chip erase completely wipes the NVRAM, deleting all your saved configuration data, and replaces it with new default values and the new data structure for the new firmware.”

  • On by default: “and for good reason”, as the docs put it. The App switches the option back on every time it starts (main.js). You only see the switch in expert mode, in the “Advanced” box of the “Flash” sub-tab (FlasherFlashTab.vue).
  • When to turn it off: “Full chip erase should only be disabled when you are 100% certain that the configuration data structure has not changed since the last flash, otherwise incorrect configuration values may be retrieved by the new firmware, with potentially disastrous results.” Without the option, the App only erases the areas the new firmware is written to (usbdfu.js).
  • Result: after flashing everything is back to defaults, your rates too, see Check after flashing.

How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.

Check my log for free

No log yet? See a real example · Turn on logging, with pictures

For your next flying day
  • Betaflight App, Blackbox tab: logging device onboard flash or SD card, logging rate 1 kHz
  • RC Commands, Setpoint and Gyro on, then “Save and reboot”
  • Fly 3 to 5 packs of normal acro
  • Then get the log off the quad and drop it into the free check

DFU mode and the boot button

In DFU mode the processor’s bootloader runs instead of Betaflight, and that’s the only way to flash. Normally you don’t have to do anything: the App reboots the FC into the bootloader by itself when flashing (webstm32.js). If that doesn’t work, according to the flasher docs you can also get there like this:

  • hold the boot button on the FC while you plug in USB,
  • click “Activate Boot Loader / DFU” in the Setup tab,
  • or type bl in the CLI tab.

If the FC is already in DFU mode, select it as a DFU device in the device list and pick the board by hand, because “Detect” needs the normal connection. The App then flashes right away, without making a backup first (useFirmwareFlashing.js). The App describes the “No reboot sequence” switch in the “Advanced” box like this: “Enable if your FC is in boot mode. i.e. if you powered on your FC with the bootloader pins jumped or whilst holding your FC's BOOT button.” To leave DFU mode without flashing, use “Exit DFU Mode” in the menu next to “Flash Firmware”.

Drivers on Windows (WinUSB), the browser’s permission and udev rules on Linux are covered in Betaflight not connecting: DFU mode. According to the docs, a receiver or GPS on the FC can stop it from entering DFU mode; what helps then is in the faults.

What’s different after the update

With “Full chip erase” all settings are gone and the FC starts with the defaults of the new firmware. You need your backup file now, but not necessarily for pasting. The CLI docs are strict about it: “Never paste a diff or dump from one firmware version into a different version — variable names and valid ranges change between releases and will silently corrupt the configuration.” The flasher docs recommend: “Generally, we recommend full manual re-configuration. When the flash is from the same point version, usually it's OK to import a saved Preset, or paste a Diff. Parts of a diff can also be selectively pasted into the CLI, eg the VTX Table, or the modes and aux settings.”

  • “Restore Backup”: the button after flashing sends your old backup to the FC line by line. Lines the new firmware rejects are skipped, the rest is saved anyway; at the end the App says how many lines were skipped (AutoRestore.js). It needs firmware 4.5.4 or newer. On the same version that’s fine; on a new version, according to the docs, you’re better off setting up by hand.
  • An example from 2026.6: on boards with the IIM-42652 gyro the measuring range was corrected. According to the release notes this effectively doubles your existing PID gains: reset and re-tune your PIDs after the update, don’t arm on your old tune. “Restore Backup” would write the old PID values back if the backup contains them.
  • More examples (removed settings, rates without rates_type) and how to paste parts such as the modes selectively: Betaflight backup: after a firmware update.
  • Back to the old version: according to the docs it’s the same process, just with the old version; then you restore your saved file. The App 2026.6.2 only connects to Betaflight 4.3 and newer, though (Which App, which browser).

Check after flashing

  1. Connect and calibrate: “Once the firmware is flashed, re-connect, calibrate your accelerometer, and re-configure your settings.” The “Calibrate Accelerometer” button is in the Setup tab.
  2. Set up again: tab by tab, with the backup file next to you as a cheat sheet, for example Ports, Receiver, Modes and OSD.
  3. Rates: they are now at the firmware default, in 2026.6.2 Actual Rates 70/670/0.00 for center, max and expo (controlrate_profile.c). Enter your own again as described in Setting up Betaflight rates.
  4. Arming: if the quad won’t arm, status in the CLI tab shows why; every reason is listed in Quad won’t arm: all arming flags.
  5. Before the first flight: “After flashing, always check that every setting is 'as it should be', before test flying.” According to the docs, fly the first test flights cautiously and in a safe place.

Whether your rates still suit your stick after the update, the free check shows on your next blackbox log. The blackbox settings are back to defaults after the erase too; how to set up logging and read out the log is in Blackbox logging: setup and downloading your log.

Faults: symptom, cause, fix

Sorted by the moment things go wrong. The messages are shown as the App 2026.6.2 displays them; when each one appears is in the App’s source code. Problems with connecting itself (no port, drivers, browser) are covered in Betaflight not connecting.

Board and build

The board list is empty, “Detect” logs:

App message“No targets loaded”

Cause
Boards, versions and the build come from Betaflight’s build server. Without internet, or with the option “Disable internet access (for metered or slow connections)”, the list stays empty.
Fix
Check your internet connection, switch the option off in the App’s settings, then open the tab again.

“Detect” logs:

App message“Please select valid serial port”

Cause
“Detect” asks the flight controller (FC) over the normal USB connection. If no serial port is selected in the device list, for example because the FC is in DFU mode, that doesn’t work.
Fix
Plug the FC in normally and select it in the device list. In DFU mode, search for the board in the list by hand.

“Detect” finds a board but no target:

App message“App has detected the board: … but no official Betaflight target was found”

Cause
The board name the FC reports (board_name) is not in the build server’s list.
Fix
Search the list for the board by hand. If it isn’t there, the manufacturer’s firmware via “Load Firmware [Local]” is what’s left; according to the docs the manufacturer builds and supports it.

“Detect” fails:

App message“The App failed to verify the board. If this persists, try switching tabs and retry, reconnect the USB, or connect first if you might have forgotten to apply custom defaults.”

Cause
The App couldn’t confirm the board over the USB connection. If “App has detected the board: …” comes first, only the name is missing from the list, see the case above.
Fix
What the message says: switch tabs and retry, replug USB, or connect normally first. If connecting fails too, see Betaflight not connecting.

After “Load Firmware [Online]” the App asks:

App message“OSD protocol not selected”

Cause
The “OSD Protocol” field is empty. Without “Detect” the App preselects nothing there, and according to the App a build needs an OSD protocol (“You must select an OSD protocol to build a firmware.”).
Fix
“Select OSD protocol”, then choose “Analog” (analog video, OSD chip on the FC) or “Digital” (HD video). Use “Continue without OSD protocol” only if the quad needs no OSD. See Build options.

The build status shows:

App message“failed (please check log)”

Cause
The build server couldn’t build the firmware. One reason according to the docs: every option uses flash memory, and if the firmware is too large, the build fails.
Fix
Open “Show Log” next to it, the reason is in there. Remove options you don’t need, check your own “Custom Defines” and load again.

The build status shows:

App message“timed out (please retry)”

Cause
The build wasn’t finished when the App’s waiting time ran out.
Fix
Click “Load Firmware [Online]” again.

While flashing

When flashing, this appears:

App message“Firmware mismatch. The connected board is … while you selected … Do you want to continue flashing?”

Cause
The board name of the connected FC doesn’t match the board you selected. The App itself warns: flashing a binary for the wrong target can cause bad things to happen.
Fix
Click “Abort”, pick the right board with “Detect” and load again. “Continue” only if you know for sure that the board you picked is right.

Flashing stops right away:

App message“Backup cancelled, flashing aborted”

Cause
Before flashing, the App backs up your settings with diff all by default and asks where to save the file. You canceled the save dialog.
Fix
Flash again and save the file. How to use it later is in Betaflight backup with diff all.

After the reboot into the bootloader you see:

App message“USB DFU not found”

Cause
For flashing, the FC reboots into DFU mode and shows up as a different USB device. The browser needs its own permission for it, Windows may need a driver.
Fix
Pick the DFU device in the browser’s window. Permission, drivers (WinUSB) and browsers without WebUSB are covered in Betaflight not connecting.

The FC won’t enter DFU mode although drivers and cable are fine

Cause
According to the docs, the bootloader also listens on the serial ports (UARTs). If a device such as a receiver or GPS sends something that looks valid there, it hijacks the bootloader.
Fix
Power the device down or disconnect it while flashing. Many receivers only send once they are bound to the transmitter: switch the radio off before the receiver gets power.

The App says:

App message“Board seems read protected. Unprotecting. Do not disconnect/unplug!”

Cause
The FC’s memory is read-protected. The App removes the protection and waits at least 20 seconds while the memory is erased.
Fix
Don’t unplug, wait. Afterwards the App asks: “ACTION REQUIRED: Unplug and re-connect flight controller in DFU mode to try flashing again!” Do exactly that.

Flashing aborted, the FC no longer responds:

App message“Programming: FAILED”

Cause
The firmware wasn’t written completely, for example because the cable came out while flashing. According to the App, the STM32 bootloader is in ROM and cannot be bricked.
Fix
The “Recovery / Lost communication” box in the flasher: power off, in expert mode enable “No reboot sequence” and “Full chip erase”, jumper the BOOT pins or hold the boot button, power on, install drivers if needed, then flash the right firmware. More under DFU mode.

After flashing

Sensors greyed out, OSD or other parts missing

Cause
According to Troubleshooting: the wrong target was flashed, so the sensor drivers are missing, or the cloud build lacked the options you need.
Fix
Pick the right board with “Detect”, check the build options and flash again. If the manufacturer needs data from you: according to the docs, flash with “Core Only” and click “Submit Support Data” in the CLI tab.

The radio controls nothing, nothing moves in the Receiver tab

Cause
Two possible reasons: “Full chip erase” also reset the port and receiver settings to defaults, or your radio protocol is missing from the build. By default only CRSF is included (Crossfire and ExpressLRS).
Fix
Set up ports and receiver again. If your receiver uses SBUS, GHOST, FPORT or another protocol, choose it under “Radio Protocol” and flash again.

The ELRS receiver on the FC (SPI) no longer links with the radio

Cause
According to the 2026.6 release notes, ELRS 3 is the default when flashing, and it doesn’t work with a transmitter on ELRS 4.
Fix
If your transmitter runs ELRS 4: in expert mode, enter ELRSV4 under “Custom Defines” and flash again. According to the docs, an ELRS receiver on a serial port doesn’t need it.

After “Restore Backup” the App says:

App message“Configuration backup restored, … line(s) skipped.”

Cause
The new firmware rejected some lines of your old backup. The App skips them and saves the rest anyway.
Fix
Set the settings from those lines by hand and check everything. With a new version the docs recommend setting up by hand anyway, see What’s different after the update.

Sources

As of November 12, 2026, checked against Betaflight 2026.6.2 (App and firmware from September 16, 2026, the latest versions on that day). Nothing here was tested on a device; procedures and messages come from the docs and source code.

Last updated: Nov 14, 2026 · checked with Betaflight 2026.6.2