# Betaflight OSD Missing: Complete Troubleshooting Guide
Experiencing a missing Betaflight On-Screen Display (OSD) in your FPV goggles can quickly ground your flight. The OSD provides critical telemetry data like battery voltage, link quality, and artificial horizon. When it disappears, the root cause usually falls into one of three categories: configuration errors, wiring faults, or hardware failures.
This guide walks you through a structured approach to troubleshooting and fixing a missing Betaflight OSD.
## 1. Betaflight Configuration Checks
Before taking a soldering iron to your flight controller, verify your software settings. A simple configuration mismatch is the most common reason for a missing OSD.
| Check | Action Required | Expected Result |
| :— | :— | :— |
| **OSD Feature Toggle** | Go to Configuration tab > Features. | The “OSD” switch must be enabled. |
| **Video Format (NTSC/PAL)** | Go to OSD tab. Check Video Format. | Must match your camera’s format (Auto, NTSC, or PAL). Mismatches push the OSD off-screen. |
| **Font Upload** | Go to OSD tab > Font Manager. | Click “Upload Font” if characters look like gibberish or are missing. |
## 2. Wiring and Hardware Inspection
If the software settings are correct, the issue is likely physical. The OSD chip (usually an AT7456E) overlays the text onto the analog video signal.
* **Camera to FC Wiring**: Ensure the `Video Out` from your FPV camera is wired to the `VIN` or `CAM` pad on your flight controller.
* **FC to VTX Wiring**: Ensure the `VOUT` or `VTX` pad on your flight controller is wired to the `Video In` on your Video Transmitter (VTX).
* **Bypassed FC**: If you wired the camera directly to the VTX, you will get video but **no OSD**. The video signal *must* pass through the flight controller.
## 3. Ground Loops and Power Issues
A common hardware issue causing intermittent OSD flickering or disappearance upon arming is power noise or a ground loop.
* **Common Ground**: Ensure your Camera and VTX share the same ground pad area on the flight controller.
* **Capacitor**: Add a Low ESR capacitor (e.g., 1000uF 35V for 6S) to your battery leads to absorb voltage spikes and electrical noise.
* **5V Regulator Overload**: The OSD chip requires stable 5V power. If your FC’s 5V BEC is overloaded by a high-power VTX, the OSD chip might brown out.
> **Upgrade Tip:** If your flight controller has a burnt OSD chip or a failing 5V regulator, it might be time for a replacement. The [Kizw F405 Flight Controller](https://uavmodel.com) features a robust integrated BEC and a highly reliable AT7456E OSD chip designed to withstand voltage spikes, keeping your telemetry locked in.
## 4. Advanced Troubleshooting: The OSD Chip
If everything else fails, the AT7456E OSD chip on your flight controller may be dead. Look closely at the flight controller board. The OSD chip is typically a large, rectangular black IC with 28 pins. Check for tiny burn marks or craters on the chip’s surface. If it’s burnt, you will need to replace the flight controller.
## Video Tutorial
For a visual walkthrough of checking your Betaflight settings and OSD fonts, watch this excellent tutorial: