How to Identify Betaflight Firmware Target and Version

by Oscar

In this tutorial I will show you how to check the Betaflight firmware target and version of your flight controller. Different FC might use different Betaflight firmware targets, if you flash the wrong firmware to your FC, you could “brick” the board and unable to connect or flash it again.

Some of the links on this page are affiliate links. I receive a commission (at no extra cost to you) if you make a purchase after clicking on one of these affiliate links. This helps support the free content for the community on this website. Please read our Affiliate Link Policy for more information.

Although it’s possible to fix “bricked” FC as it’s only a software issue, but it’s inconvenient all the same.

Check out this post for more Betaflight Tutorials.

What’s a Firmware Target?

A firmware target is a specific firmware file for a particular flight controller.

Sometimes multiple flight controllers might share the same firmware target. For example, The Onmibus F4 AIO V2 uses the “Onmibus F4 SD” target, while the DYS F4 Pro V2, as well as the Rotor Riot Control FC also use the same target.

This can be confusing sometimes, your flight controller might be called something completely different from the name of the firmware target.

You can usually find out what the exact Betaflight firmware you should use from the manual. Alternatively, you can check in Betaflight configurator.

How to Identify FC Target/Version?

Simply connect to Betaflight configurator, go to CLI and enter:


The result tells you what the target and version of Betaflight firmware is installed on your board.

# Betaflight / [Target] [Version] [Date]

It’s that simple :) Happy flying.

Auto Detect Flight Controller

In the latest Betaflight Configurator it’s possible to use the “Auto Detect” function when you flash firmware and it minimizes the chance of user error. Go to the Firmware Flasher in the Configurator, plug in the FC via USB cable, select the COM Port, and click “Auto-Detect” and it will pick the correct flight controller target for you.

Betaflight 4.3 Auto Detect Fc Board

Leave a Comment

By using this form, you agree with the storage and handling of your data by this website. Note that all comments are held for moderation before appearing.


Normen 23rd May 2023 - 9:30 pm

Hallo. Ich hab ein Baby nano 1s v1. Und finde bei betaflight nicht das richtige target mit der Fr Endung. Was haben die Endungen zu bedeuten?!?

Jar 15th October 2021 - 3:42 am

Thank you for this

Mr Chris D Guillaume 18th July 2021 - 7:58 am

I flashed the rush blade f722 analogue with stm32f7x2, didn’t backup diff/dump and now the gyro isn’t working :( can you help?

Oscar 18th July 2021 - 9:27 am

Flash it again with the correct firmware, and when you connect the FC to Betaflight it should ask if you want to apply custom settings, just press yes.

brendon 9th April 2019 - 6:45 am

does anyone know the target for the millivolt osd?

Mike 20th March 2019 - 11:36 pm

I have learned so much from you and I appreciate all of your hard work in sharing your knowledge. My question is on the FRSKYxsrf4po combo flight Controller, power distribution board, and receiver. I checked the version of the flight controller on betaflight. It told be omnibus. So I flashed the firmware and all went well. My question is, since it is FRSKY, shouldn’t I have flashed the firmware from FRYSky? Thank you.


Manfred Bycek 23rd February 2019 - 2:45 pm

How do i know which target to use if i acccidently flashed the wrong firmmware?

You describe the way to look at what is installed, not what has to be installed.

Oscar 25th February 2019 - 5:13 pm

So what do you get when you type version in CLI?

David Sherman 25th September 2018 - 6:16 pm

Frst I want to tell you that you have some of the BEST reviews and articals written on the subject of drones! Next,
I have looked everywhere for info on oled installation on my drone, with no luck. I have a Kakute f4v2a new oled. the oled led comes on but the screen is blank. I have no idea what to do or check. The I2C connections are correct (scl, sda) I dont know what else go try. Thank you.

Brian Granger 1st August 2018 - 6:11 am

Good article.
Question? Are you verifying the firmware FC target name in case there are system updates to download?

Oscar 6th August 2018 - 6:04 pm

When flashing firmware, you have to pick a flight controller in the firmware list, sometimes the target is called something else (not your flight controller). So it’s always best to verify what target your FC uses :)