How to flash Betaflight on an FPV drone
Flashing Betaflight is the process of installing the firmware that runs your flight controller and controls how your FPV drone flies.
If you choose the right target, save your settings first, and verify each step, the process is straightforward and repeatable.
This guide explains how to flash Betaflight on FPV drone builds safely, what tools you need, how to avoid common mistakes, and what to do after the firmware is installed.
What Betaflight does on an FPV drone
Betaflight is one of the most widely used flight controller firmware platforms for FPV drones, especially freestyle, racing, and lightweight cinewhoop builds.
It manages gyro data, receiver input, motor mixing, arming logic, failsafe behavior, and many tuning features through the Betaflight Configurator.
When you flash new Betaflight firmware, you are updating the software on the flight controller board, not the ESC firmware or your radio transmitter.
This distinction matters because the flight controller, ESCs, receiver, and VTX each serve different roles in the system.
What you need before flashing Betaflight
Gather everything first so you do not disconnect the drone mid-process or lose settings you still need.
- A computer with Windows, macOS, or Linux
- Betaflight Configurator installed
- A USB data cable that supports data transfer, not just charging
- The drone battery disconnected for safety
- The correct firmware target for your flight controller
- Backup files or screenshots of your current setup
If your build uses a removable receiver, VTX table, or custom resource mapping, a backup becomes especially important.
Modern Betaflight versions can restore many settings from a dump file, but not every board-specific quirk survives an upgrade without review.
How to identify the correct flight controller target
The most important step in flashing firmware is selecting the correct target.
Betaflight firmware is board-specific, and the wrong target can prevent the flight controller from booting.
Look for the board name printed on the flight controller PCB, on the product page, or inside the Betaflight Configurator when the board is connected.
Common manufacturers include iFlight, SpeedyBee, Holybro, Diatone, Matek, HGLRC, and others, but the crucial detail is the actual MCU and board target, such as an F405, F722, or H743-based target with a specific board identifier.
If you are unsure, check:
- The flight controller silk screen
- The manufacturer documentation
- The board listing on the Betaflight target page
- Any sticker or QR code on the FC
Never guess.
A few minutes spent confirming the target is better than recovering a board that will not initialize after flashing.
How to back up your current Betaflight settings
Before changing firmware, save your current configuration in Betaflight Configurator.
This gives you a fallback if you need to restore CLI commands, rates, receiver settings, or OSD customizations.
Use the CLI dump or diff
Open the CLI tab and copy the full diff all output or a full dump if you want a more complete snapshot.
A diff is usually easier to reuse because it focuses on settings that differ from defaults.
Save screenshots of key tabs
Also capture screenshots of these areas:
- Ports tab
- Configuration tab
- Receiver tab
- Modes tab
- PID Tuning or Rates tab
- OSD tab
These screenshots help if a restore requires manual editing.
They also help verify UART assignments after flashing.
How to flash Betaflight on FPV drone in Betaflight Configurator
Once the target is confirmed and your settings are backed up, you can flash the firmware.
- Connect the flight controller to your computer using USB.
- Open Betaflight Configurator and click Connect if the board is already recognized.
- Go to the Firmware Flasher tab.
- Select the correct firmware target for your board.
- Choose the Betaflight version you want to install.
- Enable Full chip erase if you want a clean install, which is usually recommended during major upgrades.
- Click Load Firmware [Online] or download and flash the local file if needed.
- Click Flash Firmware and wait for the process to complete.
If flashing succeeds, the board will reboot and reconnect.
If it does not reconnect immediately, unplug the USB cable, reconnect it, and try again.
Some boards require holding the boot button or shorting boot pads to enter DFU mode.
What to do if Betaflight does not detect the board
Connection problems are common, especially on first-time setups or after a firmware update.
- Try a different USB cable, preferably one known to support data
- Use a different USB port on the computer
- Install or update USB drivers on Windows if needed
- Check whether the board has power indicators when plugged in
- Press the boot button while connecting, if the board supports it
- Verify that the flight controller is not damaged or shorted
If the board enters DFU mode but still cannot flash, the issue may be driver-related or target-related.
In that case, reinstalling the correct driver package or confirming the firmware target usually resolves it.
How to restore settings after flashing
After the firmware is installed, reconnect to Betaflight Configurator and review the major setup pages before flying.
A fresh flash resets many values to defaults, so do not assume your old configuration is still active.
Restore or verify these items:
- Receiver protocol and UART assignment
- Serial RX enable settings in the Ports tab
- Motor order and motor direction
- Gyro orientation
- Arming switch and flight modes
- OSD elements and warning thresholds
- Failsafe settings
Then paste your saved CLI diff if the settings are compatible with the new Betaflight version.
If the version changed significantly, compare settings carefully instead of restoring everything blindly.
Why first-flight safety checks matter
Even if the flash process is successful, one wrong setting can cause a crash on takeoff.
Run bench checks with the props removed before installing them again.
Check motor order and direction
Arm the quad only when the props are off and the drone is secured.
Move the sticks slowly and confirm the correct motors respond.
Then check each motor direction against the Betaflight motor layout diagram.
Verify receiver input and arming
Confirm that stick movement is visible in the Receiver tab and that your arming switch works as intended.
If endpoints are wrong or channels are mapped incorrectly, fix that before flight.
Test failsafe behavior
Failsafe should stop the motors quickly and predictably if the receiver signal is lost.
This is one of the most important safety checks in any Betaflight setup.
Common mistakes when flashing Betaflight
Most problems come from a few recurring errors rather than from the flashing tool itself.
- Using the wrong firmware target
- Forgetting to back up settings before erasing the chip
- Restoring a CLI dump from a different Betaflight version without checking compatibility
- Ignoring motor direction after a flash
- Leaving props on during testing
- Assuming UART assignments survived the upgrade unchanged
A clean process and careful verification matter more than the firmware version number alone.
Betaflight is designed to be updated, but the surrounding setup still needs attention.
When to use a clean flash versus an upgrade
A clean flash is best when you are changing to a major Betaflight version, recovering from a corrupted setup, or starting fresh on a new build.
An upgrade with partial restoration can work well when you are moving between close versions and want to preserve tuning and custom settings.
Use a clean flash if you notice unexplained behavior, inconsistent OSD settings, or lingering configuration problems after earlier updates.
Use a cautious restore if your current tune is stable and you mainly want access to newer features or bug fixes.
Helpful Betaflight terms to know
- Flight controller: The board that runs Betaflight and processes sensor data
- Target: The specific firmware build for your board
- DFU mode: A USB flashing mode used to install firmware
- CLI: Command Line Interface for viewing and changing settings
- UART: Serial port used for receiver, GPS, VTX, or other peripherals
- Failsafe: The behavior triggered when signal is lost
Knowing these terms makes the Betaflight Configurator easier to navigate and reduces the chance of applying the wrong fix during setup.
When to reflash Betaflight again
Reflashing is useful if the board becomes unstable, a configuration becomes corrupted, or a new feature or bug fix matters for your build.
It is also common after replacing the flight controller, swapping to a different board revision, or resetting a quad that has accumulated years of changes.
Keep a clean backup workflow so each update is easier than the last.
That habit turns Betaflight flashing from a risky chore into a routine maintenance task for any FPV drone pilot.