The Betaflight OSD (On-Screen Display) is the only information channel you have while flying goggles-down. When your quad is half a kilometer out and the video starts breaking up, a well-configured OSD tells you RSSI, battery voltage, and GPS coordinates — all at a glance, without taking your eyes off the gap. A cluttered OSD buries critical warnings under decorative elements you never look at. This guide walks through every OSD setting that matters, from element placement to custom fonts.
Accessing the OSD Tab
In Betaflight Configurator (10.10.0 or newer), the OSD tab shows a preview of your video feed with draggable elements. Connect your flight controller via USB, plug in a battery (VTX and camera do not need to be connected), and you can arrange every element on the grid. Each element has a position (row/column), and the preview updates in real time. The grid is 30 columns by 16 rows for standard Betaflight OSD — elements that extend beyond column 30 or row 16 will be cut off on most cameras and goggles.
Essential OSD Elements: What to Enable and Where
With over 50 available elements, the key is restraint. Every element you add splits your attention. Here is the minimum viable OSD for each flying style:
| Element | Racing | Freestyle | Long-Range | Placement |
|---|---|---|---|---|
| Craft Name | ✓ | ✓ | ✓ | Top center or top-left |
| Battery Voltage (Average) | ✓ | ✓ | ✓ | Bottom-left |
| Battery Current Draw | — | ✓ | ✓ | Below voltage |
| mAh Drawn | — | ✓ | ✓ | Below current |
| Link Quality (LQ) | — | ✓ | ✓ | Top-right corner |
| RSSI dBm | — | — | ✓ | Below LQ |
| GPS Speed | — | — | ✓ | Center-bottom |
| GPS Satellites | — | — | ✓ | Below speed |
| Home Arrow | — | — | ✓ | Center (compass style) |
| Home Distance | — | — | ✓ | Below home arrow |
| Altitude | — | — | ✓ | Right side |
| Timer (Total Armed) | ✓ | ✓ | ✓ | Bottom-center |
| Fly Mode | — | ✓ | ✓ | Bottom-center, small |
| Throttle Position | — | ✓ | — | Left side |
| Warnings | ✓ | ✓ | ✓ | Center (auto-positions) |
Racing minimalism: In a race, you have half a second to glance at your OSD. Voltage and a lap timer. Nothing else. Racers in MultiGP often disable everything except craft name (for VTx channel identification) and battery warnings.
Warnings Configuration
The warnings system is what makes the OSD truly useful, not just decorative. Each warning can be configured with a threshold and a display duration:
| Warning | Recommended Threshold | Why It Matters |
|---|---|---|
| Battery Low | 3.5V per cell (14.0V for 4S, 21.0V for 6S) | Time to head home — still have ~20% capacity |
| Battery Critical | 3.3V per cell (13.2V for 4S, 19.8V for 6S) | Land NOW — battery is at 5-10% and sagging fast |
| Link Quality | 70 (for ELRS/Crossfire LQ mode) | Below 70 = you are on borrowed time. Turn back. |
| RSSI dBm | -105 dBm (ELRS 900MHz) / -100 dBm (2.4GHz) | ELRS failsafe threshold is typically -112 to -108 dBm |
| RX Loss | Auto (triggers on failsafe) | “RX LOSS” flashes center-screen on failsafe |
| GPS Rescue Unavailable | Auto (sats < 8 or no 3D fix) | Critical for long-range — know when your safety net is gone |
Warnings display duration: Set to 10 seconds minimum. If a warning flashes for only 3 seconds and you are mid-power-loop, you will miss it. Long-range pilots should push this to 20 seconds for critical warnings (battery, link quality).
Craft Name: More Than a Label
The craft name field in the OSD tab (max 16 characters) is not just cosmetic. It appears in your DVR recording, identifying which quad produced the footage. At races and events, it is how race directors check your VTx frequency. At a meetup, your buddy can confirm “I see ‘GEKKO5’ on R8” before you plug in. Name your quads meaningfully: frame name plus build type. Examples: GEKKO5-FR (freestyle), REKON7-LR (long-range), CHIM7-HD (cinematic HD). Spaces and special characters work in Betaflight 4.4+.
Font Manager: Custom Fonts for Better Readability
The default Betaflight font is blocky and wastes screen real estate. The Font Manager button in the OSD tab opens a tool for uploading custom fonts to the FC’s OSD chip (AT7456E or AB7456 on most boards). The best community font is “Clarity” by Steve Evans — it is sharper, narrower, and far more readable at speed than the default. Other popular options:
- Clarity — Clean, narrow, best all-rounder
- Bold — Thicker strokes, better for small text on analog
- Digital — 7-segment display style, looks great for voltage/speed readouts
- Impact / Sneaky — Large, aggressive style for craft name
To upload a font: download the .mcm file from a community source (Betaflight font repository on GitHub), click Font Manager → Open Font File, select your .mcm, then click Upload Font. The FC must be connected and powered. Upload takes 10-15 seconds — do not disconnect during the process or you risk corrupting the OSD chip’s memory.
Advanced OSD Features
DisplayPort and HD OSD
If you fly DJI O3/O4 Air Unit, Walksnail, or HDZero, the OSD is rendered by the VTX, not the FC. Betaflight sends OSD data over MSP DisplayPort, and the VTX overlays it. This means your OSD font and layout are determined by the VTX firmware, not the Betaflight Font Manager. DJI’s OSD only supports a subset of Betaflight elements — notably missing are custom warnings, some GPS elements, and craft name on older firmware. Walksnail and HDZero support the full Betaflight OSD element set. The OSD tab’s preview grid still works for layout, but font uploads go through the VTX’s own tooling (DJI does not support custom fonts at all).
OSD Profiles
Betaflight supports 3 OSD profiles, switchable via the OSD tab or through stick commands (yaw left + pitch up on the OSD menu). Use Profile 1 for freestyle (voltage, timer, LQ, fly mode), Profile 2 for racing (voltage only, timer), and Profile 3 for long-range (GPS elements, altitude, home arrow, full telemetry). You cannot switch profiles from a radio switch — OSD profiles are independent of PID/rate profiles — so change them in the OSD menu before the flight that needs it.
Common OSD Problems and Fixes
- OSD not showing after DJI O3/Walksnail upgrade: The VTX needs MSP DisplayPort enabled on the correct UART. In Betaflight Ports tab, the UART connected to your VTX must have “MSP” toggled ON (not just “VTX (TBS SmartAudio)”). Baud rate is typically 115200.
- OSD elements flickering or jumping: PAL/NTSC mismatch between camera and Betaflight OSD setting. In the OSD tab, check Video Format — set it to AUTO or match your camera’s output format explicitly.
- Font upload fails (stuck at “Uploading…”): The OSD chip is write-protected. Power-cycle the FC, reconnect, and try again. If it persistently fails, the OSD chip may be locked — a full chip erase via Betaflight CLI (
diff allfirst, then flash firmware with “Full Chip Erase” checked) resolves it. - Warnings overlay important elements: Warnings always render on top and center-screen. Move critical elements (voltage, LQ) to the top and bottom edges where warnings do not overlap them.
- Craft name cut off: The 16-character limit includes spaces. “GEKKO5-FREESTYLE” is 17 characters and will be truncated to “GEKKO5-FREESTYL”. Count your characters.
A clean OSD is a safety feature, not a cosmetic choice. When your quad is 2km out and the video is barely holding together, you need voltage and home direction — not decorative horizon bars or artificial horizon clutter. Spend 20 minutes in the OSD tab, strip it down to what you actually use, and add one element back only after you have missed it in flight. Your future self, squinting through static at 500m, will thank you.