Your OSD flickers between screens, the voltage reading drifts by 0.3V mid-flight, and you can’t find your mAh counter when you need it most — all because the OSD tab isn’t configured properly. Here’s every setting that matters, in the order you need them.
Betaflight OSD Step-by-Step Configuration
Step 1: Enable the OSD Feature
Open Betaflight Configurator, go to the Configuration tab, and scroll to “Other Features.” Toggle OSD on. Without this, the OSD tab won’t even appear in the sidebar. Save and reboot. If the OSD tab is grayed out after reboot, your flight controller’s OSD chip isn’t detected — check soldering on the AT7456E or MAX7456 pads if you’re using an external OSD module.
Step 2: Select Video Format
In the OSD tab, find the Video Format dropdown at the top right. Choose Auto for most setups, or manually set PAL/NTSC to match your camera. Mismatched format causes the OSD text to appear off-screen or not at all. If you see only half the OSD elements, your camera is outputting PAL while the OSD expects NTSC (or vice versa).
Step 3: Position Core Telemetry Elements
Drag these elements onto the grid in the OSD tab preview window. Each position maps to a character cell on your video feed. Elements too close to the edge get cropped by many goggles — keep a 3-character margin.
- Battery Voltage: Top-right corner. Shows real-time pack voltage.
- Current Draw (Amps) : Below voltage. Essential for throttle management.
- mAh Drawn: Below amps. Your fuel gauge — land at 80% of pack capacity.
- RSSI: Top-left corner. Signal strength from your radio link.
- Link Quality (ELRS): Below RSSI. More useful than RSSI for ELRS — signals dropouts before they happen.
- Flight Mode: Center-bottom. Confirms you’re in Angle/Horizon/Acro.
- Timer: Bottom-right. Total flight duration.
- GPS Coordinates (if equipped): Bottom-center. Critical for crash recovery.
Step 4: Configure Warning Thresholds
Click the Warnings tab within the OSD configuration. Set:
– Battery Warning Voltage: 3.5V per cell (3.5 × cell count). Example: 14.0V for 4S.
– RSSI Warning: 20% for Crossfire, 35% for ELRS LQ mode.
– mAh Warning: 80% of your typical pack capacity. For a 1300mAh pack, set 1040mAh.
Warnings that trigger too early become noise you ignore. Set them at the last safe moment, not a comfortable margin.
Step 5: Verify Font Upload
The OSD tab has a Font Manager button. Click it and upload the default font. If you see garbled characters or missing elements, your font is corrupted — re-upload. Some custom builds use Analog OSD chips that require specific font files. The standard Betaflight font covers all default elements.
Betaflight OSD Parameter Reference Table
| OSD Element | Recommended Position | Display Type | Effect If Misconfigured |
|---|---|---|---|
| Battery Voltage | Top-right | Numeric | Wrong cell count leads to early or late landing |
| mAh Drawn | Right column, below voltage | Numeric | No current sensor = always shows 0 |
| RSSI / LQ | Top-left | Numeric or icon | Incorrect channel or provider = frozen value |
| Flight Timer | Bottom-right | Timer | Wrong alarm threshold = ignored warning |
| Craft Name | Top-center | Text | Long names overlap adjacent elements |
| Warnings | Center | Text | Too many warnings = pilot ignores all |
| GPS Speed | Bottom-center | Numeric | GPS not locked = dashes (—) |
| Horizon Bar | Center | Graphic | Artificial horizon drifts without well-calibrated accelerometer |
Common OSD Mistakes Most Pilots Miss
Mistake 1: Setting Voltage Warning at Storage Voltage
Setting the warning at 3.8V/cell means the alarm triggers at storage charge — essentially immediately on a fresh pack. The warning should fire when you’re at 3.5V/cell under load, which typically recovers to 3.7-3.75V after landing. If your OSD screams “LOW BATTERY” 30 seconds into a flight, you’ve confused storage voltage with landing voltage.
Mistake 2: Hiding the mAh Counter to “Save Screen Space”
Every pilot who’s ever lost a quad in tall grass because they flew past their battery capacity has, at some point, removed the mAh counter because “I can feel when the pack sags.” You can’t feel sag on a cold day with a high-C pack until it’s too late. The mAh counter is the one element that tells you exactly how much fuel remains — keep it prominent.
Mistake 3: Not Testing OSD After Firmware Flash
A Betaflight firmware update resets the OSD configuration to defaults. If you flash a new version and head to the field without checking the OSD tab, you’ll find all your custom element positions wiped. After every firmware update, reconnect to the Configurator, load a diff backup, or manually reposition your elements.
Mistake 4: Trusting the Simulated Preview
The drag-and-drop preview in Betaflight Configurator uses a fixed grid that doesn’t account for your specific camera’s FOV, your goggles’ cropping, or the analog-vs-digital video pipeline. What looks centered in the preview might be cut off in-flight. Test with goggles powered on, then adjust.
Mistake 5: Enabling Too Many Warnings
Enable warnings for voltage and RSSI. Disable “angle mode warning,” “arming disabled warning,” and every other visibility warning. When everything flashes red, nothing matters. If your OSD is a wall of warning text, you’ve trained yourself to dismiss all of it — including the one you actually needed.
⚠️ Regulatory Notice: The OSD configuration recommendations in this article should be implemented in accordance with the latest 2026 drone regulations in your country or region. Some jurisdictions mandate specific OSD elements — such as Remote ID identification or registration numbers — to be visible during flight. Always verify local laws regarding in-flight telemetry display requirements. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
As we covered in our Betaflight CLI Mastery guide, many OSD settings can also be configured through CLI commands for faster batch setup. If you’re running RPM filters, check our Betaflight RPM Filtering guide — bidirectional DShot is required for ESC telemetry to populate OSD RPM data.
The SpeedyBee F405 V4 flight controller includes a built-in AT7456E OSD chip with full Betaflight OSD support and 4 UARTs for clean peripheral wiring. Available at uavmodel.com with same-day shipping for US orders.