RetroArch black screen or no video

Black, blank, or corrupted — they differ

A black screen in RetroArch is not one failure. Watch for which one you get:

• Nothing at all, no menu — the video driver failed before drawing, so this is a startup driver problem.
• Menu fine, game black — the core started but never produced a frame; usually a core setting or a missing renderer feature.
• Corrupted frames or garbage colours — the core asked for a renderer feature the driver is not providing.
• Flicker on fast-moving scenes — threaded video interacting badly with hardware-rendered cores.

The distinction matters because only the last two are worth changing video settings for.

Get the driver back

1. Start RetroArch and open Settings → Drivers → Video.
2. Switch between Vulkan and GL. If Vulkan is black, try GL first — this is the fastest single test.
3. On macOS use Metal; on Android use Vulkan and fall back to GLES only if the device is old.
4. Set Settings → Video → Scaling → Aspect Ratio to 4:3 or 16:9. The “Config” option can produce a zero-size viewport with certain cores.
5. Restart RetroArch fully — closing to the menu is not enough for a driver change.

Rule out the core’s own renderer

Threaded video is the usual culprit behind flicker and corrupted output on hardware-rendered cores. Turn Settings → Video → Threaded Video off and test the same game. If the picture is correct but slower, the core needs threaded video and the real fix is a different core build.

A tracked report describes a core that fails to request GLES3 and renders corrupted frames — that is a core bug, and no RetroArch setting fixes it. Switching to the core’s alternative build does.

When only one system is black

If PS1 renders and N64 does not, you are looking at a core problem, not a video driver problem. Compare with a different core for that system before changing global settings — global changes tend to break the systems that were working.

On Android specifically

Black screens on Android are usually surface-loss problems: the emulator loses the surface when the app is backgrounded and does not recreate it. Lock the app in the recent-apps view, disable battery optimisation for RetroArch, and relaunch rather than resuming.