Betaflight setup guide for the 2026.6 App: connect, configure and arm safely
Quick answer
Betaflight setup in the 2026.6 App takes eleven steps. Open app.betaflight.com, take the props off, connect by USB and save a diff all backup. Then calibrate the accelerometer, give the receiver one Serial RX port (or choose SPI on a whoop board), set the receiver protocol, assign an arm switch, check motor order and direction, set failsafe and finish with a props-off arm check. Each step is written for the 2026.6 layout. Where 2025.12 differs, we say so.
Contents
- Before you start
- Step 1: Connect and back up
- Step 2: Calibrate the accelerometer and check orientation
- Step 3: Ports tab: one Serial RX UART
- Step 4: Configuration tab and ESC/motor essentials
- Step 5: Receiver and ExpressLRS
- Step 6: Presets (optional, but recommended for BNFs)
- Step 7: Modes tab: arm switch, angle, beeper, turtle
- Turtle mode (FLIP OVER AFTER CRASH) spins the props on one side in reverse to flip a crashed quad, and needs DShot betaflight.com. Betaflight warns: "This puts extreme stress on motors and ESCs when the motors are obstructed after a crash." betaflight.com
- Step 8: Motors tab: order and direction (props off)
- Step 9: Failsafe
- Step 10: OSD and VTX basics
- Step 11: Rates and PIDs: leave the defaults for your first flight
- Final props-off arm check
- Coming from an older guide? What's different in 2026.6
- Troubleshooting quick list
- FAQ
- Next step
Researched from the official Betaflight docs, the Betaflight 2026.6 and 2025.12 release notes and the ExpressLRS docs; sources checked on the date shown above. We have not run these steps on our own hardware yet, and the diagrams are drawn from the documentation, not screen captures.
Versions covered
| Software | Version this guide follows | Released |
|---|---|---|
| Betaflight App | 2026.6.2 | Sep 16, 2026 github.com |
| Betaflight firmware | 2026.6.2 (notes for 2025.12.5 users) | Sep 16, 2026 / Jun 28, 2026 github.com |
| ExpressLRS (receiver step) | 4.1.0 and 3.6.4 | Jul 17, 2026 / Jun 8, 2026 github.com |
Scroll the table sideways for more columns.
Since 2025.12 the App uses the same version number as the firmware it matches betaflight.com. Using 2025.12? Look for the "2025.12 note" lines.
Deeper topics link to their own guides; all of them are in the Betaflight hub.
Before you start
- Props off. Remove every propeller before you plug in a battery, and leave them off for this whole guide.
- A data USB cable. Betaflight's guide lists this first when the board won't connect: "Make sure you are using a USB cable that is capable of data transfer." betaflight.com Still no port? See Betaflight App: download, versions and connection problems.
- A supported browser. Betaflight's App page asks for a Chromium-based desktop browser such as Chrome or Edge betaflight.com. The 2026.6 notes add that Firefox 151 now ships WebSerial and "the app runs natively on Firefox" betaflight.com. If something misbehaves, try Chrome or Edge first.
- Know your path. Betaflight says pre-built drones are "often already configured correctly by the manufacturer" betaflight.com. On a BNF, connect, back up, inspect each tab and change only what's wrong (receiver protocol, arm switch, failsafe), often by applying the maker's preset. On a scratch build, you set every step yourself.
- Battery safety. You need a LiPo only for the steps that spin or arm motors. Follow the safety instructions in your battery's and charger's manuals, including what they say about damaged or swollen packs, and unplug the battery as soon as you're done. Our research method page explains where our safety guidance comes from.
- Need a radio? Our RadioMaster Pocket ELRS setup guide covers one popular option from power-on to binding.
Step 1: Connect and back up
Connect over USB (browser port dialog)
The web App can't see a USB device until you grant it access betaflight.com:
- Open app.betaflight.com and plug in the quad (no battery needed).
- In the port dropdown, choose "I can't find my USB device".
- In the browser's device dialog, select your flight controller and click Connect.
- Pick the board in the port dropdown and click Connect.
What's different in 2026.6: "The top header bar has been retired." Connection status and options now "live in the sidebar and each tab's own toolbar", and Virtual Connect and Manual Connect are hidden unless Expert Mode is on in the Options tab betaflight.com. That's why the top-right Connect button from older videos is missing.
Save a diff all before you change anything
Betaflight's guide says to "send either the diff all or dump command, then copy or save the output" before changing anything betaflight.com.
- Open the CLI tab.
- Type
diff alland press Enter. - Save the output to a text file named after the quad and the date (for example
meteor75-2026-10-13-diff-all.txt), somewhere other than Downloads.
The CLI reference describes diff all as "Show all non-default settings across all profiles" betaflight.com, so it's short and readable.
2026.6 adds a Restore button: "The Backups tab now has a Restore button that writes a backup straight back to a connected flight controller." betaflight.com Make a Backups-tab backup too, but keep the diff all file: you can read it and copy parts of it. (2025.12 note: no Restore button.)
Check the firmware version; update only if you need to
Type version in the CLI ("Show firmware version string") and note the result with your backup betaflight.com. On a new BNF, don't flash just because a newer version exists. If the quad connects, the receiver works and the maker's preset fits, set it up as shipped.
If you do update, read How to update Betaflight to 2026.6 safely and the official 2026.6 release notes first. In short:
- The Flasher docs warn: "This will ALWAYS erase all previous configuration data from the flight controller!" betaflight.com
- Click auto-detect and "ensure the correct board name appears in the list" betaflight.com. If you flash the wrong target, reflash the correct one in bootloader/DFU mode as described in the Firmware Flasher docs.
- In 2026.6 the Flasher has two sub-tabs, Board & Build and Flash, and can restore a backup captured before flashing betaflight.com.
Step 2: Calibrate the accelerometer and check orientation
The accelerometer is used for "self stabilization features, like angle, horizon, acro trainer, and even GPS rescue" betaflight.com.
- "Place the quad on a flat, level surface and do not move it during calibration." betaflight.com
- Click Calibrate. The button reads Calibrating... while it runs.
- Tilt the quad by hand and confirm the 3D model follows: nose down shows nose down, right side down shows right side down betaflight.com.
Where's the button? The current docs place accelerometer calibration in the Sensors tab, which "consolidates sensor setup that was previously split across the Configuration and Setup tabs" betaflight.com. The Setup tab page still lists Calibrate Accelerometer betaflight.com. Check both.
Model moves the wrong way? The 2026.6 Sensors tab adds a Board Alignment Wizard that reads the accelerometer and gyro while you tilt the board as instructed. The docs say it appears "On firmware with API >= 1.48" betaflight.com; the 2026.6.2 firmware source sets MSP API 1.48 github.com. Without the wizard, "Go in increments of 90 degrees (45 if it's a diagonally mounted FC) and test the preview after each change." betaflight.com
Coming from 4.5 or older? 2025.12 removed the "non-user serviceable" gyro alignment. If the quad flips after updating, check board alignment; with the board's arrow pointing forward, it should be 0 betaflight.com.
Don't click Reset Settings on the Setup tab unless you mean to start from defaults. "This is not a "Factory Reset" for your drone or flight controller" betaflight.com.
Step 3: Ports tab: one Serial RX UART
The Ports tab sets what each serial port (UART) does. Check three things:
- Serial RX is on for the UART your ELRS receiver is wired to. ExpressLRS's Betaflight steps start here expresslrs.org.
- Only one UART has Serial RX. 2026.6 enforces it: "Only one UART can be assigned as the Serial RX input in the Ports tab" betaflight.com.
- The VTX UART matches your video system: SmartAudio or Tramp for analog, "VTX (MSP + Displayport)" for digital betaflight.com.
Whoop with a built-in receiver? "If your flight controller has a built-in SPI receiver, no UART configuration is needed." betaflight.com Set the receiver mode to SPI in Step 5.
| Ports-tab mistake | What you'll see | Fix |
|---|---|---|
| MSP and Serial RX on the receiver's UART | Settings won't save: "Enabling both MSP and Serial RX on the same UART causes a conflict" betaflight.com | Leave only Serial RX on that UART |
| Configuration/MSP used as a "toggle" for a port | Conflicting options "cause your config to not save" betaflight.com | Turn on only the function the port needs |
| Serial RX on the wrong UART | No stick movement in the Receiver tab | Check the board's wiring diagram and move Serial RX |
| Telemetry Output on for ELRS | Nothing gained: "This is not used for most modern radio systems like ELRS." betaflight.com | Leave it off |
| Analog VTX control off | Band, channel and power can't be changed | Enable SmartAudio or Tramp "in the Ports tab" betaflight.com |
Scroll the table sideways for more columns.
Click Save (in 2026.6, in the tab's toolbar). The board reboots.
Step 4: Configuration tab and ESC/motor essentials
On a BNF, most of this is already set. Check it; change it only with a reason.
- Arming angle. The Configuration tab limits how far the quad can be tilted and still arm; "setting it to 180 degrees will disable the check" betaflight.com. The
small_angledefault is 25 degrees betaflight.com. Leave the check on. - ESC/motor protocol sits under ESC/Motor features in the Motors tab; "DShot is standard for modern builds" betaflight.com. Betaflight's guide: "DShot300 is better for slower processors (e.g. F411 boards) and gyros running at 3.2 kHz (e.g. BMI270)" and "DShot600 is better for faster processors (e.g. F7 family)" betaflight.com. On a BNF, keep what the maker set.
- Motor idle "Sets a minimum motor output value to ensure the motor is able to smoothly speed up from idle." betaflight.com The docs give no default, so we don't quote one. Use the maker's value or preset.
Step 5: Receiver and ExpressLRS
For an ELRS receiver on a UART, ExpressLRS's Betaflight steps are expresslrs.org:
- Serial RX on for the receiver's UART (Step 3).
- In the Receiver tab, set the receiver mode to Serial and the Serial Receiver Provider to CRSF.
- Set Telemetry to Enabled.
- Set RSSI Channel to Disabled "if you are using an Analog FPV System" (the page also covers MSP DisplayPort systems), and make sure RSSI ADC is disabled.
For a built-in SPI receiver, set the receiver mode to SPI, the option "Used for most integrated receivers, like ExpressLRS on tinywhoop AIO boards" betaflight.com.
Check the sticks. Bind first (how to bind an ELRS receiver), then move each stick and switch and watch the Receiver tab bars:
- Roll, pitch, yaw and throttle should each move their own bar, in the right direction.
- Wrong bar? "If your radio input does not match up to what you see in the preview, you need to change the channel map." betaflight.com
- Nothing moves? Check the protocol: "Selecting the incorrect protocol will lead to no signal being detected, or the signal being interpreted incorrectly." betaflight.com
New in 2026.6: the failsafe banner. In failsafe, "the Receiver tab shows a banner and tints the channel bars, so failsafe output values are not mistaken for a broken receiver" betaflight.com. With the radio off, the banner is expected. Turn the radio on and wait for the link. (2025.12 note: no banner.)
The full walk-through and a "sticks don't move" checklist are in Betaflight receiver setup for ELRS.
Step 6: Presets (optional, but recommended for BNFs)
"Presets offer an easy way to configure your settings." Each one is a small batch of CLI commands betaflight.com. For a BNF, the maker's preset is often the quickest good starting point.
- Make sure today's
diff allis saved. - In Presets, filter by Category, Keywords, Author, Firmware or Status betaflight.com.
- Read the description, set any options (some ask for motor KV) and click Apply.
- Recheck Steps 3 to 5 in case the preset changed ports or receiver settings.
Finding the right preset is covered in Betaflight presets.
Step 7: Modes tab: arm switch, angle, beeper, turtle
Betaflight's guide recommends ARM, plus BEEPER and ANGLE betaflight.com.
- Open the Modes tab.
- Under ARM, click Add Range. This "creates a range slider tied to an AUX channel."
- Leave the channel on AUTO and flip your arm switch: "The AUTO dropdown auto-selects the AUX channel when you flip the switch you want to use." betaflight.com
- Drag the range so the marker sits inside it only in the arm position.
- Repeat for ANGLE (self-levelling) and BEEPER ("useful for locating crashed craft") betaflight.com.
- Click Save.
ELRS 4 arm channel. The 4.0.0 notes say "CH14 now carries the 1 bit arming flag in 8ch and 12ch mode" github.com. If the arm switch misbehaves on ELRS 4, see ExpressLRS 4 vs 3 and EdgeTX model setup.
Turtle mode (FLIP OVER AFTER CRASH) spins the props on one side in reverse to flip a crashed quad, and needs DShot betaflight.com. Betaflight warns: "This puts extreme stress on motors and ESCs when the motors are obstructed after a crash." betaflight.com
Step 8: Motors tab: order and direction (props off)
- Confirm the props are off, then plug in the battery.
- In Mixer, confirm the layout: "Typical quadcopters use the "QUAD X" setting so set this if you are unsure." betaflight.com
- Spin each motor on its own with the test sliders and check that it's the motor the Mixer diagram shows for that number.
- Check each motor's direction against the diagram.
- Wrong direction? The motor direction tool lets you "gently spin motors and easily reverse motors" betaflight.com.
- Unplug the battery.
Props in vs props out. The normal setting spins the props toward the camera ("props in"); Motor direction is reversed spins them away ("props out"), which pilots use to "prevent debris from being pushed into the camera" betaflight.com. Change it only if your frame or preset calls for it, and mount props to match.
A motor direction guide is coming.
Step 9: Failsafe
Failsafe decides what the quad does when the radio link drops. The Failsafe tab docs describe two stages betaflight.com:
- Stage 1 starts when "there is no signal from the receiver for 100ms or more" (or on invalid pulses or a receiver-reported failsafe). It lasts
failsafe_delay, which "defaults to 1.5s". With Auto, roll, pitch and yaw centre and throttle goes to minimum. - Stage 2 follows if the link is still lost. The default, Drop, means "The craft will disarm and fall out of the sky." The alternatives are Land and GPS Rescue.
For a first quad, keep the defaults and test them: "arm your craft with your props off, then turn off your transmitter." "The motors should stop after the configured failsafe delay time." betaflight.com Disconnect the App first, since it blocks arming (see the final check).
Betaflight also warns: "We do NOT recommend using receiver based failsafe!" betaflight.com
GPS Rescue, Landing mode and ELRS behaviour are in Betaflight failsafe with ELRS.
Step 10: OSD and VTX basics
OSD. Betaflight's guide says "At minimum, enable:" Warnings, average cell voltage, and one link-quality or RSSI item betaflight.com.
- Analog (MAX7456): the PAL/NTSC setting "must match the camera signal", and "Font upload may be required when upgrading from older versions of Betaflight." betaflight.com
- HD (MSP DisplayPort): "HD OSD defaults to a 53 column x 20 row grid", and Betaflight queries the VTX for the best grid once it's online betaflight.com.
VTX. To set band, channel and power from Betaflight on analog, enable SmartAudio or Tramp (Step 3) and use the Video Transmitter tab; "You may need a VTX Table for your specific VTX" betaflight.com. "Remember that not all frequencies are legal in all regions." betaflight.com Use only the bands and power levels allowed where you fly. Digital systems use "VTX (MSP + Displayport)", and the Presets tab has system-specific presets betaflight.com.
A full OSD guide is coming.
Step 11: Rates and PIDs: leave the defaults for your first flight
Don't touch PIDs for a first flight. Use the firmware defaults or your maker's preset. The exception: an IIM-42652 board updated to 2026.6 must go back to defaults or a fresh tune (Step 1 warning).
Rates set how fast the quad rotates for a given stick movement. They're personal; you can match your simulator rates later. Until our rates guide is live, the presets guide shows how to apply a rates preset without touching PIDs.
Skip the Autotune tab for now. 2026.6 lists it as "Autotune Tab (Experimental)" and gates it behind Expert Mode betaflight.com.
Final props-off arm check
The App blocks arming while connected: the MSP flag means "MSP connection is active, probably via Betaflight App", and the fix is "Terminate the Betaflight App connection (disconnect)" betaflight.com. Run this check unplugged from USB, on battery, props off.
Once everything passes, fit the props in the direction Step 8 confirmed and make your first hover in an open space away from people. Our drone rules page links each regulator. Rules change, so check your regulator's page before you fly somewhere new.
Coming from an older guide? What's different in 2026.6
Most top-ranking guides still show Betaflight Configurator 10.x or the 2025.12 App. Here is where things went.
| In older guides | In the 2026.6 App | Source |
|---|---|---|
| Top header bar with Connect | Retired; status and connection in the sidebar and per-tab toolbars | 2026.6 notes |
| Accelerometer calibration on the Setup tab | Docs place it in the Sensors tab; the Setup tab page still lists it (check both) | Sensors tab, Setup tab |
| Board alignment in the Configuration tab | Also in the Sensors tab, with a Board Alignment Wizard (API 1.48+) | Sensors tab |
| Four Flasher sub-tabs | Two: Board & Build, and Flash; restore after flash | 2026.6 notes |
| Transponder tab | Tab removed; transponder provider and data are managed via the CLI | 2026.6 notes |
| Virtual / Manual Connect always visible | Hidden unless Expert Mode is on | 2026.6 notes |
| Serial RX on several UARTs | Only one UART can be Serial RX | 2026.6 notes |
| — | New tabs: Preflight, Autotune (Expert Mode), Flight Plan (simulation only), Blackbox Viewer | 2026.6 notes |
| Chromium browsers only | Firefox 151+ also runs the App | 2026.6 notes |
Scroll the table sideways for more columns.
Version-gated warnings
| Hardware / setting | Version | What to do | Source |
|---|---|---|---|
| IIM-42652 gyro | 2026.6 | ±4000 → ±2000 DPS "effectively doubles your existing PID gains". Reset and re-tune; don't arm on the old tune | 2026.6 notes |
| IST8310 compass | 2025.12 | Default address 0x0C (12) → 0x0E (14). Not detected? set mag_i2c_address = 12, then save | 2025.12 notes |
trust_mag | 2026.6 | New, default OFF; compass users opt in with set trust_mag = ON | 2026.6 notes |
d_max_advance | 2026.6 | Now defaults to 0; an old diff brings back your old value | 2026.6 notes |
poshold_without_mag | 2026.6 | Removed; "any saved diff referencing it will be rejected on load" | 2026.6 notes |
Legacy GPS Rescue settings (gps_rescue_velocity_p/i/d, gps_rescue_max_angle, gps_rescue_roll_mix and others) | 2026.6 | Removed; old diff lines for them won't apply | 2026.6 notes |
Absolute Control (abs_control_*) | 2026.6 | Retired | 2026.6 notes |
| SPI ELRS receivers | 2026.6 | V3 by default; V4 needs the ELRSV4 build flag | 2026.6 notes |
Scroll the table sideways for more columns.
Troubleshooting quick list
| Problem | First thing to check | Where |
|---|---|---|
| App doesn't see the quad | Data cable, "I can't find my USB device", browser | Betaflight App guide |
| Ports tab won't save | MSP and Serial RX on the same UART | Step 3 |
| No stick movement | Serial RX UART, Serial vs SPI, CRSF, bind, ELRS 3 vs 4 | Receiver setup for ELRS |
| Won't arm | OSD warning: MSP, ANGLE, THROTTLE, RXLOSS | Final check |
| Wrong motor or direction | Mixer layout, motor direction tool | Step 8 |
| 3D model moves wrong | Board alignment / wizard | Step 2 |
Scroll the table sideways for more columns.
FAQ
Do I need to update the firmware on a new quad?
Usually not right away. Per the Firmware Flasher docs, flashing always erases the configuration, so back up and follow our update guide if you do.
Why does my Betaflight look different from tutorials?
Most tutorials show Configurator 10.x or 2025.12. The 2026.6 App retired the header bar and moved controls to the sidebar and tab toolbars. See the table above.
Is it safe to paste my old diff into 2026.6?
Not blindly. The Firmware Flasher docs say "Generally, we recommend full manual re-configuration", and pasting a diff is "usually" OK only "When the flash is from the same point version". Copy over only values you understand, and never old PIDs onto an IIM-42652 board.
Do I need to change PIDs?
No. Fly on defaults or the maker's preset first, except on IIM-42652 boards after a 2026.6 update (reset them).
Next step
Your quad is set up. Next, check its link and switches in Betaflight receiver setup for ELRS, then read Betaflight presets and Betaflight failsafe with ELRS.
Sources and versions checked (October 13, 2026; release tags re-checked October 14, 2026)
- Betaflight 2026.6 release notes: https://betaflight.com/docs/wiki/release/Betaflight-2026-6-Release-Notes
- Betaflight 2025.12 release notes: https://betaflight.com/docs/wiki/release/Betaflight-2025-12-Release-Notes
- Betaflight firmware releases (2026.6.2 Latest, Sep 16, 2026; 2025.12.5, Jun 28, 2026): https://github.com/betaflight/betaflight/releases
- Betaflight App releases (2026.6.2 Latest, Sep 16, 2026): https://github.com/betaflight/betaflight-configurator/releases
- MSP API version in 2026.6.2 firmware source: https://github.com/betaflight/betaflight/blob/2026.6.2/src/main/msp/msp_protocol.h
- Betaflight docs: setup guide, App page, Setup, Sensors, Ports, Configuration, Receiver, Modes, Motors, Failsafe, Presets, OSD, VTX and Firmware Flasher tab pages, CLI reference, Failsafe guide, Arming Sequence & Safety (URLs in the page metadata)
- ExpressLRS: Configuring FC (https://www.expresslrs.org/quick-start/receivers/configuring-fc/), 4.0.0 release notes, releases page (4.1.0 Jul 17, 2026; 3.6.4 Jun 8, 2026)
Researched from the official docs and release notes listed above. We have not run these steps on our own hardware yet; when we do, this page will name the board, firmware and date.