# Betaflight OSD Missing? The Ultimate Troubleshooting Guide
If you’re flying an FPV drone and your On-Screen Display (OSD) suddenly vanishes or fails to show up on a new build, you’re flying blind. The OSD provides critical flight data like battery voltage, flight mode, and warnings. Without it, your quad is at risk. This guide walks you through the step-by-step process of diagnosing and fixing a missing Betaflight OSD.
## 1. Verify Betaflight Config Settings
The first and most common reason for a missing OSD is incorrect configuration in the Betaflight Configurator.
* **Enable OSD Feature:** Go to the **Configuration** tab and ensure the `OSD` toggle under *Other Features* is enabled.
* **Video Format:** In the **OSD** tab, check the *Video Format*. If it’s set to `Auto`, change it manually to match your camera (`PAL` or `NTSC`). A mismatch here often causes the OSD to disappear off the edge of the screen or not render at all.
### Common Video Format Mismatches
| Camera Format | Betaflight Setting | Symptom if Mismatched |
| :— | :— | :— |
| NTSC | PAL | OSD shifted off-screen or flashing |
| PAL | NTSC | OSD cut off at the bottom |
| Auto | Auto | Intermittent OSD display |
## 2. Check Wiring and Hardware Connections
If the software settings are correct, the issue usually lies in the hardware layer. The video signal must pass *through* the flight controller’s OSD chip to overlay the text.
* **Camera Video Out to FC Video In:** Ensure the camera’s yellow video wire is soldered to the `VIN` or `CAM` pad on the flight controller.
* **FC Video Out to VTX Video In:** Ensure the flight controller’s `VOUT` or `VTX` pad is soldered to the VTX’s video input.
* **Ground Loops:** Ensure the camera and VTX share a common ground with the flight controller to prevent noise from disrupting the OSD chip.
*Need a reliable flight controller with a robust OSD chip? Check out the [UAVModel F405 Flight Controller](https://www.uavmodel.com) designed for clean video routing and noise isolation.*
## 3. Font Upload and Display Issues
Sometimes the OSD is “there” but displays as gibberish or nothing at all because the character set (fonts) isn’t loaded correctly onto the OSD chip.
* Connect your quad, go to the **OSD** tab, click **Font Manager**, and click **Upload Font**.
* Wait for the upload to complete. **Do not disconnect the battery or USB during this process.**
## 4. Hardware Failure (The MAX7456 Chip)
Analog OSD is typically generated by a MAX7456 (or clone) chip on the flight controller. These chips are sensitive to voltage spikes.
* If the chip is excessively hot to the touch, it may be burnt out.
* If Betaflight refuses to upload fonts, the chip might be dead, requiring a flight controller replacement.
## Visual Guide to OSD Troubleshooting
Here is an excellent visual walk-through from Joshua Bardwell on fixing OSD issues: