Your OSD is the difference between landing at 3.5V per cell and puffing a $40 LiPo because you flew blind. The default Betaflight OSD layout dumps every possible element onto the screen at once. That’s noise, not information. Here’s how to build a clean OSD that shows exactly what you need, exactly where you need it.
Step-by-Step Betaflight OSD Configuration
Step 1: Strip the Default Layout
Open Betaflight Configurator, OSD tab. Select “Font Manager” and upload a font — the default shows all characters. The Clarity font at 24px with “upload font” checkbox gives the cleanest read.
Now remove everything you don’t actively use. Default layouts include altitude, heading, GPS coordinates, and horizon bars that most pilots never look at. Each element you remove reduces screen clutter. My rule: if you haven’t looked at a data point in your last 5 flights, delete it.
Step 2: Build Your Core Elements
Position these on screen corners so they’re in your peripheral vision without blocking the center:
Top-left: Craft name (identifies which quad’s OSD you’re looking at in DVR). Main battery voltage with two decimals. Timer 1 (total flight time, starts on first arm).
Bottom-center: Throttle position as a horizontal bar. More useful than a number — you feel the stick, you don’t need to read “37%.”
Bottom-right: RSSI dBm value. Not the icon — the actual number. An icon says “signal exists.” -95dBm says “you have 10 seconds before failsafe.”
Center: Warnings only. Low battery, RX loss, failsafe. These auto-appear in the center. Don’t place permanent elements there — you’ll drown out the warnings.
Step 3: Configure Critical Alerts
Go to the Alarms section. Set these thresholds:
- Battery warning: 3.5V per cell average (14.0V for 4S, 21.0V for 6S). Land immediately.
- Battery critical: 3.3V per cell (13.2V for 4S, 19.8V for 6S). You’re in damage territory.
- RSSI warning: -95dBm for ELRS, -90dBm for Crossfire. Both links have usable range below these thresholds, but you need warning before failsafe, not at failsafe.
- Link quality: Below 70%. This is your real signal health metric — RFMD (RF Mode) matters more than pure RSSI.
Enable “flash on warning” — the flashing element grabs your peripheral vision faster than a static number.
Step 4: Add Flight Statistics (Post-Flight Disarmed Screen)
These elements show ONLY after disarming. They don’t clutter your in-flight view:
- Max altitude — useful for knowing if you’re pushing local limits
- Max distance from home — more useful than GPS coordinates during flight
- Total mAh drawn — better than voltage for gauging remaining flight time
- Average cell voltage at disarm — the most honest number for pack health
Step 5: Test With DVR Review
Fly one pack with the new layout. Review the DVR. Ask yourself: did I look at every element during flight? Elements you never glanced at are candidates for removal. Elements you had to search for need repositioning. Iterate. I revise my OSD every 10-15 flights as my information needs evolve.
Betaflight OSD Element Priority Table
| Element | Priority | Best Position | Show In-Flight? | Why It Matters |
|---|---|---|---|---|
| Main Battery Voltage | Critical | Top-left | Yes | Prevents over-discharge |
| RSSI dBm | Critical | Bottom-right | Yes | Link health before failsafe |
| Link Quality (LQ) | Critical | Bottom-right | Yes | RF reliability metric |
| Timer (Total Armed) | High | Top-right | Yes | Flight endurance |
| mAh Drawn | High | Bottom-left | Yes | More accurate than voltage |
| Throttle Position | Medium | Bottom-center | Optional | Stick-feel correlation |
| GPS Speed | Medium | Top-right | Optional | For long-range only |
| Craft Name | Low | Top-left | Yes | DVR identification |
| Warnings | Critical | Center (auto) | Auto | Can’t miss them |
| Home Arrow | Medium | Center-edge | For long-range | Return direction |
Common OSD Mistakes Pilots Make
Mistake 1: Using voltage alone to gauge battery. Voltage sags under load. A 4S pack showing 14.2V at hover could be at 3.6V per cell resting or 3.3V per cell under punch-out. Always pair voltage with mAh drawn. When mAh consumed hits 80% of pack capacity, land regardless of what voltage says.
Mistake 2: Cluttering the center of the screen. The center 40% of your OSD is your primary flight view. Obstacles, gaps, and lines appear here. Placing permanent elements in this zone obscures what you’re flying toward. Put everything in corners — your brain processes peripheral data faster than you think.
Mistake 3: Setting RSSI warning too low. -100dBm on ELRS is failsafe territory. If your RSSI warning is set to -100, by the time you see it, you’ve already lost control. Set warning at -95dBm minimum. On Crossfire, -92dBm. Give yourself a 3-5 second reaction window.
Mistake 4: Not updating the font when you add custom elements. Betaflight OSD fonts are bitmap-based — if a character isn’t in the font file, it renders as a blank space or garbage glyph. Every time you change your OSD element set, re-upload the font. As we covered in our Betaflight OSD Custom Fonts guide, font management is the first step to clean OSD rendering.
Mistake 5: Duplicating transmitter telemetry on OSD. If your transmitter already calls out “battery low” or vibrates at critical voltage, don’t also put huge voltage warnings on the OSD. Use OSD for what your transmitter can’t show you — link quality at the aircraft side, actual mAh consumed, post-flight stats.
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.
OSD and Your Build Workflow
OSD configuration isn’t isolated from the rest of your build. Your RSSI and LQ values come from your receiver protocol. As we explained in our Betaflight RSSI Setup guide, correct channel mapping on the Receiver tab is what feeds accurate RSSI numbers to the OSD. A misconfigured Aux channel feeding garbage RSSI data makes every warning threshold useless.
For GPS-equipped builds, read our Betaflight GPS Rescue Setup guide — the home arrow and distance elements on your OSD only work if GPS rescue itself is correctly configured and tested.
Product Recommendation
The SpeedyBee F405 V4 flight controller includes a dedicated OSD chip with 512 character memory, meaning you can upload the full Clarity font at maximum resolution without running out of character slots. Older AT7456-based OSD chips max out at 256 characters, which forces font compromises. The V4 handles every custom character you’ll ever need.