How to Configure FPV Drone OSD
If you want faster lap timing, safer battery management, and less guesswork in the air, learning how to configure FPV drone OSD is one of the highest-value setup tasks you can do.
The right on-screen display turns raw telemetry into usable flight information, but only if you place the right elements in the right spots.
This guide explains how FPV OSD works, which data matters most, and how to build a clean layout for Betaflight, ExpressLRS, HDZero, and DJI FPV systems.
What the FPV OSD does
FPV OSD stands for on-screen display.
It overlays flight data directly onto the live video feed from your drone, so you can see information such as battery voltage, flight time, RSSI, GPS position, and warnings without looking away from the goggles or monitor.
Modern OSD systems are tightly linked to the flight controller and video transmission stack.
In analog builds, OSD is usually handled by the flight controller through Betaflight or iNav.
In digital systems like DJI O3 Air Unit or HDZero, OSD behavior depends on the video ecosystem and firmware support.
Why OSD matters in FPV
- Helps prevent low-voltage battery damage
- Shows flight mode and arming state
- Provides rescue data like GPS home arrow and distance
- Supports racing with lap times and timers
- Improves situational awareness in freestyle and long-range flying
What you need before configuring OSD
Before you start changing settings, confirm that the drone, flight controller, and video system support OSD output.
The exact menus vary, but the core requirements are similar across most builds.
- Flight controller firmware: Betaflight, iNav, or ArduPilot-compatible setup
- Video system: analog, HDZero, DJI, Walksnail, or other supported digital link
- Telemetry source: battery sensor, current sensor, GPS module, receiver telemetry, or ESC data
- Configurator access: Betaflight Configurator or the relevant firmware tool
If your OSD fields appear blank, the issue is often not the layout itself.
It may be a missing UART assignment, incorrect telemetry protocol, disabled features, or an unsupported video pipeline.
How to configure FPV drone OSD in Betaflight
Betaflight remains the most common platform for freestyle and racing drones, so it is a practical place to start.
The OSD tab lets you arrange, enable, and disable elements visually before saving them to the flight controller.
Step 1: Enable the right features
Open the Configuration and Ports tabs first.
Make sure the flight controller has the needed sensors and telemetry inputs enabled.
For many builds, that means activating battery voltage monitoring, current sensor support, GPS if installed, and the telemetry protocol used by your receiver or video system.
Common items to verify include:
- Battery voltage monitoring
- Current sensor calibration
- GPS support for long-range or rescue setups
- Receiver telemetry if your radio link provides RSSI, LQ, or SNR
Step 2: Open the OSD tab
In Betaflight Configurator, the OSD tab shows a grid where each widget can be placed.
You can drag items to different positions and test readability before flying.
Prioritize the elements you need mid-flight and remove clutter that distracts from the video feed.
Step 3: Place the essential elements
A clean OSD usually starts with core safety data.
These are the most useful fields for most FPV pilots:
- Battery voltage: primary low-voltage warning
- Timer or flight time: supports return planning and pack management
- RSSI, LQ, or SNR: receiver link quality for ExpressLRS, Crossfire, or similar systems
- Craft name: helpful when flying multiple drones
- Warnings: low battery, failsafe, GPS rescue, or arming disabled
If you fly freestyle, keep the screen simple.
If you fly long-range, add GPS coordinates, distance from home, altitude, and home arrow.
If you race, emphasize lap timing and a compact timer display.
Step 4: Calibrate battery values
Battery voltage must be accurate, or your OSD warning system becomes unreliable.
Check that the voltage shown in your goggles matches a multimeter reading.
If it does not, calibrate the voltage sensor in the firmware.
Do the same for current meters so mAh consumption estimates are realistic.
This matters because many pilots use OSD values to land before packs are over-discharged.
A poorly calibrated current sensor can make a 1300 mAh battery look half full when it is not.
How to configure OSD for different FPV systems
Analog FPV
Analog FPV usually routes OSD through the flight controller to the camera feed before it reaches the VTX.
This setup is straightforward and widely supported.
The key is making sure the flight controller’s OSD chip or software-based OSD is active and that the camera, FC, and video transmitter are wired correctly.
Analog pilots often need the simplest layouts because low-resolution video can become hard to read if too many elements overlap.
Use large, high-contrast widgets and avoid stacking data in one corner.
HDZero
HDZero provides digital low-latency video and supports OSD integration through its ecosystem.
The layout workflow is typically more flexible than analog, but you should still limit clutter.
HD video can show more information clearly, yet excessive overlays still reduce visibility during fast maneuvers.
DJI FPV systems
DJI digital FPV systems, including the O3 Air Unit and compatible goggles, use a different OSD workflow than analog builds.
OSD elements may be handled in the flight controller and rendered through the digital link, with feature availability depending on firmware and compatibility.
For DJI builds, check:
- Air unit firmware compatibility
- Betaflight support for DJI OSD protocol
- Correct MSP/telemetry settings where required
- Goggle-side OSD display options
Best OSD elements for most pilots
The best OSD layout is not the one with the most data.
It is the one that helps you make fast decisions without hiding the image you are trying to fly through.
Recommended core setup
- Voltage
- Flight timer
- RSSI/LQ
- Arming status
- Warnings
Recommended long-range additions
- GPS coordinates
- Home arrow
- Distance to home
- Altitude
- Sat count
Recommended racing additions
- Race timer
- Lap time
- Battery voltage
- Arming state
Common OSD problems and fixes
Many OSD issues come down to configuration mismatches rather than hardware failure.
If the screen is blank, scrambled, or missing key data, work through the system layer by layer.
- No OSD visible: confirm OSD is enabled in firmware and supported by the video system
- Wrong voltage reading: calibrate the battery sensor
- No GPS data: verify UART wiring, baud rate, and GPS protocol settings
- Missing RSSI or link quality: check receiver telemetry and protocol support
- Cluttered display: remove unnecessary fields and spread critical data across the screen
When testing, power the drone on a bench first, then arm it in a safe area with props removed if possible.
This lets you confirm the layout before depending on it in flight.
Tips for a cleaner, more readable OSD
Readable OSD design is mostly about hierarchy.
Put the most important data where your eye naturally lands, and keep the number of items low enough that the video remains usable in bright sun, low light, and rapid motion.
- Use one battery warning system, not several redundant ones
- Keep home and rescue data near the center for long-range flying
- Avoid overlapping icons and text
- Test the layout in real light conditions, not only on a bench
- Revisit the design after a few flights and remove fields you never check
A good FPV OSD should feel almost invisible until you need it.
When configured well, it gives you just enough information to fly harder, return safely, and manage batteries with confidence.