Your OSD shows battery voltage but nothing about RSSI, and you keep landing to check the GoPro. You’re flying blind on data that could prevent a failsafe. Here’s how to build an OSD layout that puts critical telemetry in your peripheral vision without cluttering the feed.
Step-by-Step OSD Configuration in Betaflight Configurator
1. Enable the OSD Feature
Go to the Configuration tab, find “Other Features,” and toggle OSD on. Without this, the OSD tab stays greyed out. Click Save and Reboot. On AIO boards with an integrated OSD chip (AT7456E), this is all you need — external MinimOSD setups are legacy at this point.
If the OSD tab remains disabled after reboot, your flight controller doesn’t have a built-in OSD chip. Check the product page — most F4/F7/H7 boards from 2020 onward include it, but some ultralight AIOs skip it to save weight.
2. Access the Font Manager
Open the OSD tab, then click Font Manager. Upload a font via the “Upload Font” button. The default “Clarity” font is fine, but “Bold” or “Impact” fonts are easier to read at speed. The AT7456E OSD chip supports 256 characters max per font — custom fonts with logos or special characters eat into that budget, so pick one and stick with it.
Font upload fails? Your FC may be in a state where OSD communication is blocked. Disconnect, power-cycle the quad, reconnect, try again. Some VTXs pull the OSD chip into a weird state on power-up — unplug the VTX temporarily if it persists.
3. Position Elements on the Grid
The Betaflight OSD uses a 30×16 character grid. Drag elements from the right panel onto the grid. Common essential elements and where to put them:
- Main Battery Voltage — top-left corner. You glance here on every punch-out.
- RSSI / LQ — top-right corner. Failsafe warning zone.
- Current Draw (Amps) — left side, below voltage. Cross-reference against voltage sag.
- mAh Drawn — next to current. More useful than voltage for knowing when to land.
- Timer — bottom-center. Total flight time since arm.
- Craft Name — top-center. Helpful if you fly multiple quads.
- Warnings — bottom-right. Betaflight auto-populates this with failsafe, low battery, and RSSI critical alerts.
Do not fill the entire screen. You need to see what the camera sees. I run 8-10 elements max on a race quad, 12-15 on a long-range build.
4. Configure Alarms and Warning Thresholds
Click on an element to set its alarm values. Real examples:
- Battery Voltage: Warning at 3.5V per cell (14.0V for 4S, 21.0V for 6S). Critical at 3.3V per cell. Below 3.3V under load, you’re damaging the pack.
- RSSI: Warning at 45%, Critical at 35%. For ExpressLRS LQ, set warning at 80, critical at 50. LQ drops fast once it starts — don’t wait.
- mAh Drawn: Set warning at 80% of your pack capacity. For a 1300mAh pack, that’s 1040mAh. This is more accurate than voltage-based landing because voltage sags differently depending on throttle.
If you run Crossfire, RSSI scaling is different — set warning at 70%, critical at 50%. Crossfire RSSI drops in bigger steps than ELRS.
5. Post-Flight Statistics Screen
Betaflight 4.4+ added a post-flight stats display that shows for 10 seconds after you disarm. Enable it in the OSD tab by checking “Post Flight Statistics.” It shows min voltage, max current, max speed (GPS required), max altitude, and flight distance. This alone replaces my habit of plugging into the configurator after every pack.
6. OSD Profiles — Switch Layouts Mid-Flight
Betaflight supports 3 OSD profiles, selectable via a switch on your radio. Configure one profile for freestyle (minimal: voltage, timer, RSSI), one for tuning (add gyro temperature, CPU load, and PID error), and one for long range (GPS coordinates, home arrow, distance from home, altitude). Map a 3-position switch to “OSD Profile Selection” in the Modes tab. This is underused — most pilots set one layout and never touch it.
Verify each profile by flipping the switch with the OSD tab open. The active profile number is shown in the top-right of the configurator grid.
OSD Element Parameter Table
| Element | Recommended Position | Key Settings | Visibility Impact |
|---|---|---|---|
| Main Battery Voltage | Top-left | 2 decimal places, alarm at 3.5V/cell | High — always visible |
| RSSI / Link Quality | Top-right | RSSI dBm or %, alarm at 35% | High — early warning |
| mAh Drawn | Left-mid | Alarm at 80% capacity | Medium — check every 20-30s |
| Current Draw (Amps) | Left-mid | 0 decimals | Medium — paired with voltage |
| Craft Name | Top-center | Keep short (<12 chars) | Low — static |
| GPS Speed | Bottom-left | Units: km/h or mph | Low — fun stat |
| Home Arrow | Center | Requires GPS fix | High — critical for LR |
| Throttle Position | Right-mid | Percent, 0 decimals | Medium — tuning feedback |
| Warnings | Bottom-right | Auto-populated | High — automatic |
| Timer | Bottom-center | HH:MM:SS | Medium — flight duration |
Common OSD Mistakes and How to Avoid Them
Mistake 1: Overloading the screen. Cramming 20 elements onto the grid makes every element too small to read at 80mph. Your brain can process maybe 4-5 data points during a split-second glance. Pick what you actually need — voltage, RSSI, mAh, timer. Everything else is noise.
Mistake 2: Setting voltage alarms for resting voltage. If you set warning at 3.8V per cell, it’ll be screaming at you on every punch-out. Voltage sags 0.3-0.5V under heavy throttle. Set warning for voltage under load — 3.5V is the standard, not 3.8V. The alarm should mean “prepare to land,” not “you just went above 70% throttle.”
Mistake 3: Ignoring mAh drawn in favor of voltage. Voltage tells you the pack’s instantaneous state. mAh tells you how much energy you’ve used. On a long-range flight where you’re cruising at constant throttle, mAh is more reliable. Voltage alone makes you land early because a cold pack sags more — you think it’s empty when it’s not.
Mistake 4: Forgetting to set OSD video format. Auto-detect usually works, but if your OSD flickers or disappears, force PAL or NTSC to match your camera. Mismatched format causes the OSD overlay to show on only half the screen or disappear entirely. This is in the OSD tab under “Video Format.”
Mistake 5: Using the wrong font for custom characters. If you upload a craft name with a special character and it shows as garbage, the font doesn’t include that glyph. The AT7456E character set is limited — stick to basic ASCII for craft names, or pre-test custom characters in the Font Manager preview.
⚠️ 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.
Even on a basic 5-inch build, a clean OSD layout transforms your flight experience. Instead of guessing battery state or squinting at a buzzer, you know exactly when to land. And when paired with our Betaflight rates configuration guide, the combination of precise stick feel and clear telemetry is what separates reactive flying from controlled piloting. If you’re running RPM filters — and you should be — the CPU load element in your OSD becomes useful: as we covered in our RPM filtering guide, RPM telemetry adds some processing overhead and you want to watch that number.
Product recommendation: The SpeedyBee F405 V4 flight controller includes a dedicated AT7456E OSD chip with full Betaflight OSD support, Bluetooth configuration via the SpeedyBee app, and a built-in 8MB blackbox — available at uavmodel.com.