A black picture during a YouTube live rerun can begin in the OBS scene, the local recording, the encoder output or YouTube itself. Compare those points in order before changing settings: the first place the image disappears is the best clue to what needs attention.
The cause cannot be identified from the symptom alone. The right check depends on your operating system, OBS version, whether the VOD is playing in a game or a separate app, and what each preview shows.
Find the first black point
Keep the playback and scene consistent while you check three views: OBS preview, a short local recording, and YouTube's Live Control Room preview or live output. Note what each shows and when it changes. A source that is black in OBS calls for a different investigation from a clean OBS recording followed by a black picture on YouTube.
| What you see | Where to investigate first |
|---|---|
| OBS preview is black | Active scene, source visibility and order, capture method, target window or game |
| OBS preview looks right, recording is black | What changes during recording, such as source visibility or fullscreen rendering behaviour |
| Preview and recording look right, YouTube is black | Outgoing encoder feed, stream connection and Live Control Room preview |
| OBS shows the VOD, but YouTube replaces it or interrupts the stream | YouTube Live Control Room warnings and possible live-content restrictions |
This is a way to narrow down the fault, not a guarantee that each symptom has only one explanation. If the picture comes and goes, record the moment and what you were doing—minimising a window, switching scenes or starting playback can matter. Avoid changing several settings before noting the original result, or you may lose the clue about where the failure began.
YouTube advises creators to check the Live Control Room preview before starting and to monitor the stream's audio and video. See YouTube's live streaming tips for computers for its current guidance. A platform preview is a separate checkpoint from the preview inside OBS.
Check the active OBS scene and source
If the OBS preview is already black, first confirm that you are looking at the scene intended for the rerun. Select it explicitly, then inspect the Sources list. Check that the relevant source is visible, that it has not been hidden, and that another opaque source is not covering it. If the scene has several layers, temporarily hide them one at a time to see whether the image returns.
Then identify what OBS is meant to capture. A game running as a process and a VOD playing in a browser or media player are not necessarily the same kind of target. Game Capture is designed to hook supported game processes; it may not be the right source for an application window. If you are capturing a player, verify that the selected window is the one actually playing the video and that the source has not retained a stale target after the app was reopened.
OBS's Game Capture troubleshooting guide describes compatibility checks, conflicts and alternatives for particular games. It does not establish one capture method as a universal fix. If a game does not permit the Game Capture hook, OBS documents Window Capture as an alternative in some cases. Display Capture can help as a short diagnostic comparison: if it shows the image while the other source does not, the issue may be in that capture path. Keep private desktop material off-screen while testing, because Display Capture records the monitor rather than just the intended player.
If the source list is confusing, make a duplicate test scene with only the suspected source and no overlays. This isolates layering without disrupting your main layout. Once the test is finished, remove or clearly label the duplicate so it cannot accidentally become the live scene later. For general source distinctions, the blog's guide to sharing a screen in Talk Studio offers a useful comparison of capturing an application versus a broader screen.
Compare OBS preview with a local recording
A preview is not the same test as a recording. Start a brief local recording with the same scene and playback, then stop it and inspect the resulting file in a player. This checks whether the image is present in OBS's captured output, rather than relying only on what appears in the interface before encoding and writing the file.
If the preview is correct but the recording is black, repeat the test while watching for changes: does the source disappear when playback begins, when the game loses focus, or when the scene changes? Check whether the source is visible in the recording's scene and whether a transition or filter changes the picture. If you use a fullscreen game, do not minimise it during the first test unless minimising is part of the normal rerun. OBS notes that some fullscreen games stop rendering when you alt-tab away, so OBS may no longer receive a picture while the game is minimised. That observation is about game rendering and focus; it is not evidence that a VOD is protected or universally impossible to capture.
Try keeping the game visible, using a second monitor, or making a test recording while the game remains in view. OBS recommends these checks in its troubleshooting guidance. If the local file is black only after the game loses focus, compare windowed or borderless fullscreen behaviour where the game supports it. Do not infer that the same setting will solve a black player window or a YouTube-only problem.
If the local recording is also black, check the source during playback rather than changing encoder settings first. A recording can help you tell whether the source disappeared, was covered, or remained black throughout. Keep the test short and use content you have permission to record and rebroadcast.
Check the outgoing feed and YouTube preview
If OBS preview and the local recording both show the VOD, the source is at least producing a picture locally. Next inspect the outgoing stream path and YouTube's Live Control Room preview. Do not treat a clean OBS preview as proof that viewers are receiving the same image: OBS still has to send an encoded feed, and YouTube has to receive and display it.
Before a public rerun, use an appropriately private or unlisted test if that fits your channel's workflow. Confirm the intended stream is selected in YouTube Studio, start the encoder only when ready, and wait for the Live Control Room preview to appear. Compare the picture there with OBS at the same moment. If the preview is black or has a warning while OBS remains correct, note the exact message and check connection or stream-status indicators instead of repeatedly changing capture sources.
YouTube's encoder streaming overview explains the encoder workflow; its live streaming tips advise checking the preview and monitoring audio and video. If the Live Control Room preview is correct but the public player is not, note whether the issue is limited to one playback device or browser before concluding that the encoder is at fault.
A different pattern is possible: OBS shows the VOD, but YouTube replaces the picture with a placeholder or interrupts the stream. YouTube says it scans live streams for third-party content, and its copyright guidance for live streams explains that streams can be interrupted or replaced when such material is identified. Check Studio for a warning before treating a placeholder as an OBS capture failure. This is not proof that every black live picture during VOD playback is a copyright action. YouTube's live streaming terms also require the streamer to have the necessary rights to the material. If you do not own or have permission to rebroadcast a game VOD, do not assume that being able to capture it means you may stream it.
Match the capture method to the source
Once you know the image disappears in OBS, check whether the source matches the material being played. For a supported game, Game Capture may be appropriate, but it depends on the game's behaviour and OBS's ability to hook it. OBS identifies Window Capture as an option for some games that do not allow Game Capture hooking. For a VOD in a browser or media player, select the relevant application window as the test target rather than assuming the game capture source will follow it.
| Method | What it targets | Useful diagnostic question | Trade-off to consider |
|---|---|---|---|
| Game Capture | A supported game process | Does the game image appear when this game is the target? | Compatibility and focus behaviour can vary by game |
| Window Capture | A selected application window | Does the player window appear while the VOD runs? | The selected window may change when the app is reopened or switched |
| Display Capture | A monitor | Does the image appear anywhere on the desktop? | It can also capture unrelated windows or notifications |
Treat the table as a starting point, not a ranking. If Window Capture shows the player but Game Capture does not, that points to a difference in target or compatibility; it does not prove a particular setting is faulty. If Display Capture is the only method showing the image, check framing and privacy before using it for a public stream. If none show the image, return to the player itself and confirm that it is actually displaying a picture on the desktop.
Do not assume DRM is responsible because a video area is black. The available symptoms do not establish that, and the black area might instead reflect a wrong target, a source hidden behind another layer, or a platform interruption. Describe the exact route—browser or player, source type, and which previews show the image—before investigating a protection-related explanation.
Change one thing at a time
After locating the first black point, change one relevant factor, then repeat the same short test. For an OBS-source problem, a sensible order is to confirm the target and visibility, then test an appropriate alternative capture source, then check game focus or display mode if relevant. For an output-only problem, preserve the source configuration while checking the outgoing feed and Live Control Room status. This keeps the evidence useful.
For Game Capture, OBS recommends checking setup and conflicts. Close overlays or monitoring tools only as a diagnostic test if they are present; OBS's guide notes known conflicts, including RTSS/MSI Afterburner, and gives version-specific notes. If the game or OBS documentation indicates an elevation requirement, test OBS as administrator for that case. Do not elevate by habit, and do not infer that administrator mode repairs every black screen.
On a laptop or multi-GPU computer, compare which GPU is assigned to OBS and the game. OBS links to GPU-selection guidance and notes cases where the applications need to use the same GPU. Treat that as a targeted check, not a general instruction for every system. Likewise, a game-specific compatibility note should take precedence over a generic tweak: OBS lists distinct workarounds for particular titles, which is why copying a setting from another game can lead you away from the cause.
Keep a simple test note: source type, scene, whether the game or player had focus, and what appeared in OBS, the local recording and YouTube. If a change makes no difference, revert it before trying the next one. This is particularly useful when preparing a long rerun, where an unrecorded trial can leave the scene in a state that is hard to reproduce after the next restart.
Gather details if it remains black
If the image still disappears, collect the details that distinguish the paths rather than trying a long list of unrelated settings. Note your operating system and version, OBS version, game title or player app, source type, scene layout, and whether the game was fullscreen, borderless or windowed. Record exactly which checkpoints are black and whether the symptom begins at startup, on playback, after a focus change or later in the stream.
A short local recording or screenshot of the OBS preview and source list can make the report clearer. Include the Live Control Room warning text if there is one, but avoid publishing your stream key or other account credentials. If you ask the OBS community for help, use its current support instructions and share only logs or diagnostic material requested through its official channels. A symptom description such as “OBS preview is fine, but the local recording and YouTube are black” is more useful than “OBS is broken”, because it points to a different stage of the path.
For a rerun that should keep going while your own computer is off, a cloud-based loop removes the specific burden of leaving OBS and that computer running overnight. StreamNeo turns an uploaded file into a YouTube live stream; it is YouTube-only, so it does not solve an OBS capture problem or remove the need to have rights to the video. The blog's explanation of uploading once versus streaming continuously describes that workflow, while its notes on OBS playlist versus VLC video source can help if the local playback source itself is under review.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is OBS showing a black screen when a game VOD plays?
There is no single cause established by that symptom. Check whether the black picture is already in the OBS preview, appears only in the recording, or starts at YouTube, then inspect the source and playback behaviour at the first failing point.
Why does the OBS preview work but YouTube show black?
A correct OBS preview does not confirm that YouTube is receiving and displaying the same picture. Compare a local recording with the Live Control Room preview, and check for stream-status or content warnings before changing the capture source.
Should I use Game Capture, Window Capture or Display Capture?
Use the method that matches the thing you are capturing: a supported game, an application window, or a monitor. Test alternatives only to isolate the source path, and consider privacy before using Display Capture in a live scene.
Is a black VOD picture proof of a copyright block?
No. A wrong source target or capture problem can also produce a black picture, and the symptom alone does not establish a rights action. If YouTube shows a placeholder or warning, review the Live Control Room and current YouTube guidance, and stream only material you have permission to use.