Display Capture is black or blank
Display Capture is entirely black even though the monitor shows a normal desktop.
Reference pages you can keep open on a second monitor while you set OBS Studio up: encoder comparisons, bitrate guidance, capture methods and the checks that tell you which setting is actually hurting you.
464 published pages in this section.
Display Capture is entirely black even though the monitor shows a normal desktop.
OBS cannot resolve or intermittently fails DNS for ingest hostnames.
The same action is bound twice or two actions share one combo, so hotkeys feel random.
Viewers hear doubled game or mic audio.
Encoding lag spikes when stingers, scene switches, or sudden overlays hit.
Encode keeps up until temperatures climb, then skipped frames appear mid-stream.
OBS reports Encoding overloaded! while the stream stutters or looks damaged.
Outbound RTMP/RTMPS blocked by firewall, antivirus network shield, or corporate policy.
Game Capture never attaches, or logs a hook failure for the target process.
Game Capture preview and output stay black while the game is visible on the desktop.
CPU is high from filters, browser sources, and software encode combined.
OBS hotkeys do not fire because the game or OS captures the same keys.
Output looks cropped, stretched, or letterboxed from canvas/output mismatches.
Stream fails to connect because the stream key is wrong, revoked, or accidentally exposed.
Laptop iGPU/dGPU affinity causes black capture, wrong encoder GPU, or terrible performance.
Showing 346–360 of 464.