# Troubleshooting Betaflight OSD Missing: Fix “No OSD on Video” Issues
If you’ve just built a new FPV drone or updated your flight controller, discovering that your Betaflight OSD (On-Screen Display) is missing can be incredibly frustrating. You have video, but no telemetry data, battery voltage, or crosshairs. This guide provides a systematic, highly technical approach to diagnosing and fixing the Betaflight OSD missing issue.
## 1. Verify Video Format (NTSC vs PAL)
A mismatch between your camera’s video format and the Betaflight configuration is the most common cause of a missing OSD. If Betaflight is rendering the OSD outside the visible area of your goggles, you won’t see it.
* **Action:** Go to the **OSD Tab** in Betaflight Configurator.
* **Check:** Look at the **Video Format** setting on the left side.
* **Fix:** If it is set to `Auto`, change it explicitly to `NTSC` or `PAL` depending on your FPV camera. Save and reboot.
| Camera Output | Betaflight Setting | Result |
| :— | :— | :— |
| NTSC | Auto | Often fails, OSD missing |
| NTSC | NTSC | **Correct**, OSD visible |
| PAL | NTSC | OSD shifted off-screen or flashing |
## 2. Check the Physical Connections
The flight controller overlays the OSD onto the video signal. Therefore, the video signal *must* pass through the flight controller.
1. **Camera to FC:** The video wire (usually yellow) from your FPV camera must connect to the `VIN` or `CAM` pad on the flight controller.
2. **FC to VTX:** The `VOUT` or `VTX` pad on the flight controller must connect to the video input of your Video Transmitter (VTX).
3. **Grounding:** Ensure the Camera and VTX share a common ground with the flight controller to prevent noise and sync issues.
*If you are looking for a reliable, noise-free flight controller with an integrated, robust OSD chip, consider upgrading to the **UAVModel F405-HDTE Flight Controller** available at [uavmodel.com](https://www.uavmodel.com). It features dedicated, filtered power pads for VTX and camera, virtually eliminating OSD blackout issues.*
## 3. Font Upload and OSD Chip Status
Sometimes the MAX7456 OSD chip on the flight controller loses its font library, or the chip itself is not communicating with the MCU.
1. **Upload Font:** In the Betaflight OSD tab, click **Font Manager** (bottom right). Click **Upload Font**. Wait for the process to complete. If it hangs, there might be a hardware issue.
2. **CLI Verification:** Go to the CLI tab and type `status`. Look for the `I2C Errors` count. If it’s constantly climbing, the OSD chip might be damaged. Also, check if `OSD` is listed under the detected hardware.
## 4. Power Supply to the OSD Chip
The analog OSD chip requires a clean 5V supply. If your flight controller’s 5V regulator is failing or overloaded by a high-power VTX or power-hungry receiver, the OSD chip will shut down.
* **Test:** Power the quadcopter with a LiPo battery (PROPELLERS OFF!). Does the OSD appear? Sometimes USB power is insufficient to power the OSD chip.
## Video Walkthrough
Watch this detailed video for a visual guide on fixing Betaflight OSD issues:
—