# How to Fix Betaflight OSD Missing: Troubleshooting VTX & FC Connections
Losing your On-Screen Display (OSD) mid-flight or right after a fresh build is one of the most common—and frustrating—issues in FPV. Without OSD, you lose critical telemetry like battery voltage, link quality (LQ), and artificial horizon, which are essential for a safe flight.
In this technical guide, we’ll walk through the exact steps to diagnose and fix a missing Betaflight OSD, covering both hardware wiring and software configuration.
## Common Causes of Missing OSD
* **Incorrect Wiring:** VTX video wire connected to the wrong pad or bypassed the FC entirely.
* **Betaflight Configuration:** OSD toggle disabled or Video Format (NTSC/PAL) mismatch.
* **Fried OSD Chip:** The AT7456E (or similar) OSD chip on the flight controller is damaged.
* **Camera Issues:** The FPV camera is outputting a signal that the FC cannot overlay data onto.
* **Font Issues:** Betaflight fonts not uploaded correctly.
## Step 1: Verify Hardware Wiring
For the flight controller to overlay data, the video signal must pass *through* the FC.
| Component | Connects To (Flight Controller Pad) |
| :— | :— |
| **FPV Camera Video Out** | `VIN` / `CAM` / `VI` |
| **FPV Camera Ground** | `GND` (preferably next to VIN) |
| **VTX Video In** | `VOUT` / `VTX` / `VO` |
| **VTX Ground** | `GND` (preferably next to VOUT) |
**Pro Tip:** Do not wire the camera directly to the VTX. The camera must go to the FC, and the FC must go to the VTX.
## Step 2: Betaflight Configuration Checks
Connect your quad to Betaflight Configurator and check the following parameters:
1. **Enable OSD Feature:** Go to the *Configuration* tab. Scroll down to *Other Features* and ensure **OSD** is toggled ON.
2. **Video Format Mismatch:** Go to the *OSD* tab. Under *Video Format*, try explicitly setting it to **NTSC** or **PAL** instead of Auto. A mismatch here is the #1 cause of a flickering or entirely missing OSD.
3. **Upload Fonts:** In the *OSD* tab, click **Font Manager** (bottom right) and click **Upload Font**. Sometimes a firmware flash clears the font memory, causing OSD elements to render as blank spaces or weird symbols.
## Hardware Upgrade: SpeedyBee F405 V3 Flight Controller
If you’ve verified wiring and software, but your OSD is still missing (or if your video feed goes black when the VTX is connected to the FC), your FC’s internal OSD chip might be fried. This is common after voltage spikes.
Instead of fighting a dead board, consider upgrading to the **SpeedyBee F405 V3 Flight Controller**, available at [uavmodel.com](https://www.uavmodel.com).
**Why the SpeedyBee F405 V3?**
* **Dedicated OSD Chip:** Features a robust AT7456E OSD chip designed to handle voltage spikes better than older designs.
* **Plug-and-Play VTX Connector:** Includes direct plug sockets for popular VTX units (like DJI O3, RunCam Link, and analog VTXs), completely eliminating wiring errors.
* **Built-in Bluetooth/WiFi:** Flash firmware and adjust Betaflight settings wirelessly from your phone at the field.
## Step 3: Check CLI Status
If the OSD chip is physically damaged, Betaflight will tell you. Go to the *CLI* tab and type:
`status`
Look for the `I2C Errors` or `SPI Errors`. If you see a high number of errors, or if the `OSD` hardware is missing from the detected devices list, the chip is dead.
## Video Tutorial: OSD Troubleshooting
For a visual walkthrough of diagnosing VTX and camera wiring, check out this excellent breakdown:
—
*Fly safe, double-check your grounds, and always use a smoke stopper on a new build!*