A blank OSD with just voltage and a timer wastes the most valuable real estate on your quad. Every element you don’t configure is a data point you could have used to save a battery, avoid a failsafe, or diagnose a mid-flight issue. Here’s how to build a fully custom OSD that gives you exactly what you need.
Betaflight OSD Elements: What to Display and Why
The OSD tab in Betaflight Configurator gives you roughly 30 elements. Most pilots run way too few. Here’s the minimum viable setup I run on every quad, from 3-inch toothpicks to 7-inch long-range rigs.
Step 1: Core Flight Data (Non-Negotiable)
- Main Battery Voltage — Place top-center or bottom-center. This is your fuel gauge. Set the warning threshold at 3.5V per cell under load so it flashes amber before you hit 3.3V where sag becomes dangerous.
- Cell Voltage (per-cell average) — I put this right next to main voltage. It gives you a faster read on individual cell health. If cell voltage drops below 3.2V under throttle while the pack average is fine, one cell is going bad.
- mAh Drawn — Place next to voltage. More useful than voltage alone because it accounts for sag. Set a warning at 80% of pack capacity. For a 1300mAh pack, flash the warning at 1040mAh.
- Fly Time — Timer starts on arm, resets on disarm. Pair it with mAh drawn — you’ll quickly learn that your 5-inch on 1300mAh gets about 4:00 of aggressive flying or 6:30 of cruising.
- RSSI / LQ — RSSI for analog, LQ (Link Quality) for ExpressLRS. Place upper-right or upper-left where your eye naturally drifts. If LQ drops below 80 continuously, turn back. At LQ 50 and below, you’re milliseconds from a failsafe.
Step 2: Diagnostic Elements (Add These or Regret It Later)
- GPS Coordinates — Even if you’re not running GPS rescue, lat/lon on the OSD means when you crash in a field, your DVR footage contains the exact location. I’ve recovered three quads this way.
- GPS Speed — Useful for long-range and cinematic flying. Know your ground speed without looking away.
- Home Arrow + Distance to Home — Direction and distance back to the arm point. Critical when you lose orientation at range.
- Throttle Position — I keep this as a thin bar on the left edge. Helps diagnose why you’re sagging voltage — if you’re at 90% throttle and voltage drops, that’s expected. If you’re at 30% and voltage tanks, you have a bad pack.
- Warnings — Enable the warnings element and configure it to show: RX_LOSS, FAILSAFE, LOW_BATTERY with audible beep.
Verification: Arm the quad (props off), power up your goggles, and confirm every element appears where you placed it and updates in real time. GPS coordinates should populate within 30-60 seconds of acquiring satellites.
Step 3: Custom Fonts and Craft Name
Betaflight OSD uses MAX7456-compatible font sets. The default font is legible but boring. Here’s how to upload a custom one:
- Download a community font pack (SNEAKY_FPV, Waffle, or CLARITY are the most readable).
- In Betaflight Configurator → OSD tab → Font Manager, click “Upload Font.”
- Select the
.mcmfile and wait for the upload to complete. Takes about 15-20 seconds. - The craft name is set in the OSD tab under “Craft Name.” Use something that identifies the quad (e.g., “APEX 5IN”) — this appears on boot and in your DVR, making it easy to match footage to the right quad later.
Pitfall: If the font upload fails mid-way, your OSD will show garbage characters. Re-upload immediately. If it still fails, try a different USB cable — bad data transfer on cheap cables is the #1 cause of failed font uploads.
Betaflight OSD Parameter Comparison: Elements That Matter
| Element | Recommended Position | Warning Threshold | Why It Matters |
|---|---|---|---|
| Main Battery Voltage | Top-center | 3.5V/cell (amber), 3.3V/cell (red) | Fuel gauge — land before damage |
| mAh Drawn | Next to voltage | 80% of pack capacity | Ignores sag, accurate consumption |
| Link Quality (LQ) | Upper-right | Below 80 (amber), below 50 (red) | Know your signal before failsafe |
| GPS Speed | Near center | N/A | Ground speed without looking away |
| Home Arrow | Lower-center | N/A | Direction home when disoriented |
| Throttle Position | Left edge bar | N/A | Correlate throttle to voltage sag |
| Warnings | Anywhere visible | RX_LOSS, FAILSAFE, LOW_BATTERY | Audio + visual alerts |
What Most Pilots Get Wrong with OSD
Mistake 1: Running Too Few Elements
The default Betaflight OSD has maybe 4-5 items. The pilot assumes “I’ll feel it when the battery is low.” You won’t. You’ll puff a pack. Add mAh drawn and cell voltage today.
Mistake 2: Placing Critical Data in the Corners on Widescreen
If you fly 16:9 (DJI, Walksnail, HDZero), corners are the hardest place for your eye to reach. Place voltage, mAh, and LQ in a column slightly in from the edge — your peripheral vision catches them faster.
Mistake 3: Ignoring the Font Manager Entirely
Default Betaflight font has poor readability for numbers at speed. A quality font like CLARITY increases digit size by ~15% without taking more screen space. This matters when you’re flying 90mph and need to read voltage in 0.3 seconds.
Mistake 4: Setting GPS Coordinate Display to Always-On
GPS lat/lon coordinates update every 200ms by default, which adds processing overhead on F411 and even some F405 boards. Set the display to only show on a switch (arm it via OSD profile or modes tab). Your CPU will thank you, especially on resource-constrained AIO boards.
Mistake 5: Not Testing Warning Thresholds Before Flying
Set your voltage warning to 3.5V/cell and go fly. If it’s flashing immediately on punch-outs, your threshold is too conservative for your flying style. Tune thresholds based on actual flight data — what voltage does your quad hit under your typical max throttle, and where is the safe landing floor?
Internal Links for Deeper Reading
As we covered in our Betaflight RPM Filter Setup, bidirectional DShot telemetry feeds RPM data to the OSD, and we discussed voltage sag troubleshooting separately — the OSD is your in-flight tool for catching these problems before they become crashes.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
Recommended Product
If you’re building a new quad and want clean OSD with full UART availability plus reliable GPS, the SpeedyBee F405 V4 stack is my go-to recommendation for 5-inch builds. Available at uavmodel.com, it includes Bluetooth configuration so you can adjust OSD elements from your phone at the field without a laptop.