# How to Set Up Betaflight OSD Elements: Custom Layout, Warnings, and Craft Name
Getting your on-screen display (OSD) dialed in is one of the most satisfying parts of an FPV build. A well-configured OSD puts critical flight data right where you need it — battery voltage, RSSI, flight mode, GPS coordinates — without cluttering your view. In this guide, you will learn how to configure every OSD element in Betaflight, arrange a clean custom layout, and set up smart warnings that can save your quad.
## Why Your OSD Layout Matters
A cluttered OSD is worse than no OSD at all. When you are flying at speed, you have milliseconds to glance at voltage or link quality. The goal is to place high-priority elements in your natural focal zone and push secondary data to the edges. Here is a quick priority breakdown:
| Priority | Element | Recommended Position |
|———-|———|———————-|
| Critical | Battery Voltage / mAh Drawn | Bottom center |
| Critical | RSSI / LQ (Link Quality) | Top right |
| High | Flight Mode / Arm Status | Top left |
| High | Timer (Total / Armed) | Top center |
| Medium | GPS Speed / Altitude | Bottom right |
| Medium | Warnings (Land Now, RX Loss) | Center (transient) |
| Low | Craft Name, Callsign | Bottom corners |
## Step 1: Enable OSD in Betaflight Configurator
First, make sure your flight controller has an OSD chip (most modern F4/F7/H7 FCs include an AT7456E or MAX7456 chip). Connect to Betaflight Configurator and go to the **Configuration** tab. Under “Other Features,” ensure **OSD** is toggled ON. Click “Save and Reboot.”
If you are using an external OSD module (like a MinimOSD with MWOSD firmware), you will need to configure it separately via its own GUI — but this is increasingly rare in 2025.
## Step 2: Access the OSD Tab
Navigate to the **OSD** tab in Betaflight Configurator (version 10.10+). You will see a preview canvas with a grid overlay representing your video feed. On the right, a list of available elements with checkboxes.
**Key sections:**
– **Elements**: Toggle individual data points on/off
– **Font Manager**: Upload custom fonts (we will cover this)
– **Alarms**: Configure voltage, RSSI, and timer warnings
– **Video Format**: Set to Auto, PAL, or NTSC (match your camera)
## Step 3: Configure Essential OSD Elements
Here are the elements every pilot should enable, with recommended settings:
| Element | Enable? | Notes |
|———|———|——-|
| Battery Voltage | ✅ Yes | Show average cell voltage as well |
| Battery Current (Amps) | ✅ Yes | Useful for detecting power system issues |
| mAh Drawn | ✅ Yes | Better than voltage for estimating remaining flight time |
| Timer (Total Armed) | ✅ Yes | Helps plan landing before battery is drained |
| RSSI Value | ✅ Yes | Raw dBm or percentage based on receiver protocol |
| Link Quality | ✅ Yes | ExpressLRS LQ is more reliable than RSSI |
| Warnings | ✅ Yes | Displays “LAND NOW,” “RX LOSS,” and custom warnings |
| Craft Name | Optional | Useful if you fly multiple quads |
| GPS Speed | If GPS installed | Ground speed in km/h or mph |
| GPS Satellites | If GPS installed | Confirms GPS lock quality |
| Flight Mode | ✅ Yes | Shows current mode: Acro, Angle, or GPS Rescue |
### Pro Tip: Show Average Cell Voltage
Instead of total pack voltage (e.g., 14.8 V), enable **Battery Average Cell Voltage** in the OSD elements list. This makes it easier to gauge battery health at a glance — you know 3.7 V per cell means time to land, regardless of whether you are flying 4S or 6S.
## Step 4: Arrange Your OSD Layout
In the OSD canvas, you can drag-and-drop elements to any position. Here is a clean, proven layout:
“`
[Craft Name] [RSSI: 99] [LQ: 2:100]
[Flight Mode: ACRO]
[GPS: 12 SAT]
[WARNINGS]
[Timer 2:34] [14.8V] [mAh: 850]
“`
### Practical Rules:
– Keep elements **at least 2 grid squares away** from the edge of the canvas — some goggles crop the edges
– Do not place elements over the center crosshair
– Use the **”Profile” dropdown (1-3)** to create different layouts for racing, freestyle, and long-range. Switch profiles with an AUX switch via the **OSD Profile** element in the Adjustments tab.
## Step 5: Upload Custom Fonts
The default Betaflight font is functional but basic. For better readability, especially with HD systems (DJI O3, Walksnail, HDZero):
1. Download the **Betaflight OSD Font Manager** or use the built-in Font Manager tab
2. Select a bold, high-contrast font (e.g., “Clarity” or “Bold”)
3. Click **Upload Font** — this takes about 30 seconds
4. Verify the font looks clean in your goggles; re-upload if characters appear corrupted
## Step 6: Set Up Alarms and Warnings
Go to the **Alarms** section in the OSD tab:
| Warning | Recommended Threshold | Why |
|———|———————-|—–|
| Battery Warning | 3.5 V per cell | First alert — time to head home |
| Battery Critical | 3.3 V per cell | Land immediately |
| RSSI Warning | 20% (or -95 dBm for dBm mode) | Signal degradation alert |
| mAh Warning | 80% of pack capacity | Backup to voltage-based warning |
Enable **”Warning”** as a display element so these alerts flash on-screen.
## Step 7: Add Custom Warnings via CLI
For warnings not available in the GUI, use the Betaflight CLI:
“`
set osd_warn_core_temp = ON
set osd_warn_fail_safe = ON
set osd_warn_launch_control = ON
save
“`
You can also display a custom craft name:
“`
set display_name = NIMBUS5
save
“`
## Recommended Component
A clean OSD depends on a flight controller with a reliable OSD chip and plenty of UARTs for GPS and receiver telemetry. The **SpeedyBee F405 V4** stack available at [uavmodel.com](https://uavmodel.com) includes a high-quality AT7456E OSD chip, Bluetooth for wireless Betaflight configuration, and 6 UARTs — giving you full flexibility for OSD profiles and telemetry.
## Watch: Betaflight OSD Full Setup Walkthrough
## Frequently Asked Questions
**Q: My OSD is not showing any overlay on the video feed. What should I check?**
Check that OSD is enabled in the Configuration tab, your VTX and camera are wired to the correct video pads (CAM to CAM, VTX to VTX), and your flight controller actually has an OSD chip. Not all FCs include one — the AT7456E and MAX7456 are the common OSD ICs.
**Q: Can I use the Betaflight OSD with DJI O3 Air Unit?**
Yes. The DJI O3 has its own native OSD (called “Custom OSD”) that reads Betaflight MSP telemetry through the UART connection. You configure it in the DJI Goggles menu, not in Betaflight’s OSD tab. However, Betaflight OSD elements configured in the OSD tab do NOT appear in DJI goggles — you must use DJI’s built-in layout editor.
**Q: Why do my OSD elements flicker or overlap?**
This usually indicates a PAL/NTSC mismatch. Go to the OSD tab, check your video format, and ensure it matches your camera output (PAL = 576i, NTSC = 480i). If unsure, set it to “Auto.”
**Q: How do I switch OSD profiles mid-flight?**
In the Adjustments tab, create an adjustment for “OSD Profile” and assign it to an AUX switch. You can then toggle between up to 3 layouts in flight.
