Betaflight Setup Basics

Betaflight is the configuration software that turns a physically assembled FPV quad into a flyable aircraft, handling everything from receiver communication to motor response tuning. This guide picks up once the physical build described in the FPV first build walkthrough is complete, and it treats one setting, failsafe, as more important than every other setting combined, because it is the one setting that specifically governs what the aircraft does when something goes wrong.

Before opening the configurator, confirm the radio itself is set up correctly on its own end. Our FPV radio roundup covers the transmitters most builders pair with a first Betaflight setup, and a solid bench soldering setup, covered in best FPV tools and soldering gear, makes any last wiring fix along the way far less frustrating.

Ports: telling Betaflight what is connected where

The Ports tab tells the flight controller firmware which physical UART connections are used for which purpose, commonly the receiver, an OSD or telemetry link, and a GPS module if one is installed like the HGLRC Mini M100 GPS module. Getting a port assignment wrong is a common source of a receiver that appears connected physically but shows no signal in Betaflight, so confirm each port matches your specific wiring before troubleshooting anything else if a connected peripheral is not responding.

Receiver: binding and verifying signal

Bind the receiver to your transmitter following the exact procedure for your specific radio protocol, since binding steps and required firmware versions differ between protocols. Once bound, open the Receiver tab with the transmitter powered on and confirm every channel bar moves smoothly and proportionally with its corresponding stick or switch. A stuck, jittery, or reversed channel here will cause real problems in flight and is far easier to diagnose and fix on the bench than in the air.

Modes: arming and flight mode assignment

Assign arming to a dedicated switch that is not used for anything else and is positioned so it cannot be bumped accidentally while carrying or handling the aircraft. Set up angle mode, which self-levels the aircraft, on a separate switch for learning to fly, since full manual acro mode with no self-leveling is significantly harder to control for a first flight. Confirm in the Modes tab that the aircraft genuinely refuses to arm unless every configured pre-arm condition is met, rather than assuming the switch alone is sufficient protection against an accidental arm.

Betaflight setup sequence

Step	Tab	What to configure
1	Ports	Assign UARTs to receiver, OSD, GPS as applicable
2	Receiver	Bind and verify smooth, correct channel response
3	Modes	Assign arming and angle mode to dedicated switches
4	PID and Rates	Start with moderate rates, tune gradually
5	Failsafe	Set to Drop, test and verify before flying
6	Motors	Verify correct spin direction with props off

Rates: resist the temptation to start aggressive

Rates determine how quickly the aircraft rotates for a given amount of stick deflection, and it is common for beginners to copy rate settings from freestyle pilots whose footage looks impressive, without accounting for how much harder aggressive rates are to fly smoothly at a beginner skill level. Start with moderate rates that let you make small, controlled corrections without the aircraft snapping into fast rotation from a small stick movement, and increase rates gradually as your stick precision improves over real flight time, not as a one-time setting decided before ever flying.

Failsafe: the setting that matters most

Failsafe defines exactly what the flight controller does the moment it stops receiving valid signal from the receiver, whether from a lost radio link, a dead transmitter battery, or flying out of range. For most builds, setting failsafe to Drop, which cuts motor output entirely and lets the aircraft fall, is the safest default, because an aircraft sitting motionless on the ground after an uncontrolled drop is a contained, recoverable problem, while an aircraft that continues flying on stale or default commands after losing signal is not. Some experienced pilots configure a landing-style failsafe instead of a hard drop, but only after building real trust in their specific setup's reliability, and even then with a full understanding of what that configuration will do over different terrain.

Test failsafe deliberately before ever trusting the aircraft with real altitude or distance. With propellers removed for safety, power on the aircraft and receiver, confirm normal control response, then power off the transmitter and confirm the aircraft's configured failsafe behavior triggers correctly and promptly. Skipping this test and assuming the default configuration is correct is one of the more consequential shortcuts a new builder can take, since failsafe is specifically the safety net for the one scenario, lost control link, that every other setting in this guide assumes will not happen.

Backing up and restoring a working configuration

Once a Betaflight configuration is working correctly, including a verified failsafe and receiver setup, save a backup of the complete configuration through the CLI tab's dump or diff command before making any further experimental changes. This single habit turns an experiment that goes wrong, whether from a bad rate change, an accidental setting reset, or a firmware update that resets configuration, from a full redo back into a quick restore from the saved backup. Store the backup file somewhere durable, such as cloud storage or a notes app, rather than only on the computer used for the original setup, since that computer may not be the one available the next time a restore is actually needed.

This habit matters even more for a builder maintaining several quads, since configurations drift apart between aircraft over time as individual tweaks accumulate, and a saved backup per aircraft is the only reliable way to recreate a specific known-good setup after a hardware swap, a replacement flight controller following a crash, or simply wanting to build a second quad configured identically to a first one that already flies well.

PID tuning: a brief note for a first setup

PID tuning, which governs how aggressively the flight controller corrects deviation from your commanded attitude, is a deep topic in its own right and not something a first build needs to chase perfection on before flying. Betaflight's default PID values, or the values a reputable preset from your specific stack's manufacturer provides, fly acceptably well on a well-built 5 inch quad without any manual tuning at all. Resist the urge to aggressively tune PIDs before a single flight has happened; it is far more productive to fly the defaults first, observe how the aircraft actually behaves, whether it oscillates, feels sluggish, or feels twitchy, and only then make small, deliberate adjustments based on what the aircraft is actually doing rather than guessing at settings in advance of any real flight data.

OSD and telemetry: useful, not required for a first flight

An on-screen display showing battery voltage, flight timer and signal strength directly in the video feed is genuinely useful once flying, but setting it up in detail is not a prerequisite for a safe first hover. If your stack includes OSD hardware, confirm at minimum that battery voltage displays correctly, since flying without any voltage awareness risks discovering a critically low pack only when the aircraft can no longer maintain altitude. Beyond that basic voltage readout, treat deeper OSD customization, additional telemetry elements, and layout preferences as something to refine after the aircraft is flying reliably, not before.

Motor direction and a safe first test

With propellers still removed, use Betaflight's motor test tab to confirm each motor spins in the correct direction for its position, correcting through software motor direction settings or by swapping two motor wires if any corner is reversed. Only reinstall propellers, checking correct orientation for each position, once motor direction, receiver response and failsafe have all been verified independently. From here, the transition to an actual first flight is covered in the FPV first build walkthrough, and any persistent vibration or shaky footage once flying is covered in fixing jello and vibration.