A black screen can come from OBS, the capture source, the recording path, or YouTube itself. First identify whether the image is black in the OBS preview, in a local recording, or only on the YouTube live output.
That distinction determines the next step. If the preview is already black, inspect the scene and source. If the preview and recording look right but YouTube is black, leave the capture source alone and investigate the program, output, and live preview instead.
Locate the first point where the video disappears
Do not begin by changing encoder settings or blaming YouTube ingest. Run a short, controlled test and note the first place where the picture disappears.
Start with the OBS preview. Select the scene you intend to stream and look at the canvas. If the canvas is black, the problem is before OBS creates its output. The source may be hidden, pointed at the wrong application, unable to hook into the application, or affected by another programme.
If the preview looks correct, make a brief local recording. Watch the recording from beginning to end rather than checking only its thumbnail. A correct preview with a black recording points towards OBS's output or recording configuration, performance limits, or a difference between the preview and the programme being sent out.
Finally, compare the recording with the YouTube live view. YouTube may show a short delay, so use a recognisable moment in the video, such as a title card or a person moving across the frame. If the local recording is visible but the YouTube output is black, you are dealing with a stream-output branch, not a capture-source branch.
Write down these details before making changes:
| Check | What you see | Where to continue |
|---|---|---|
| OBS preview | Black canvas or missing source | Scene and capture-source checks |
| Local recording | Black file despite a visible preview | OBS output, performance, and recording checks |
| YouTube live view | Black only after sending the stream | Programme, output, and YouTube checks |
| One rectangle only | Desktop is visible but a player or application is black | Source-specific and playback checks |
This simple split prevents a common mistake: changing a YouTube setting when OBS never captured an image in the first place. It also helps if someone else is helping you, because “the stream is black” becomes a precise description rather than a guess.
If the live broadcast has ended rather than showing black video, use the separate sequence in Live Stream Ended Unexpectedly: Every Cause and Fix. An ended broadcast and a running broadcast with a black picture are different faults.
Confirm the active OBS scene and source
When the OBS preview is black, check the scene before changing capture methods. In the Scenes panel, select the scene that you expect to be live. Then check the Sources panel for the intended source.
A source can be present but invisible. Look for the eye icon beside it, and check whether another source is covering it. Sources higher in the list are normally drawn over sources below them. A full-screen colour, image, browser, or media source can therefore hide a working capture source without the capture source itself being broken.
Select the source and look at its properties. Confirm that it targets the application or display you intend to capture. A Window Capture source aimed at an old window may remain in the scene while the actual application has reopened under a different window title. A Game Capture source set to capture a specific window also needs that application to be running and selected.
OBS documents separate Game Capture modes, including a full-screen application mode, a mode for a specific window, and a hotkey-controlled mode. The correct choice depends on the application and how it behaves when it starts. Review the official OBS Game Capture setup guide rather than assuming that one mode works for every game.
Check transformations as well. A source can be moved outside the canvas, cropped until nothing remains, or scaled in a way that makes the visible area difficult to find. Right-click the source and use the transform options to centre it or fit it to the canvas, if appropriate. This is a reversible diagnostic, so record any deliberate cropping before changing it.
Also confirm that you are not previewing one scene while streaming another. OBS sends the active programme scene, not whichever scene you last edited. If Studio Mode is enabled, check the programme side as well as the preview side. A scene waiting in preview may be different from the scene currently being broadcast.
For a repeating devotional video, bhajan loop, study visual, or local news file, a Media Source may be simpler than capturing another player window. For a live desktop or application, Window Capture or Display Capture may be more suitable. The source type should match what you are trying to show, not what happened to work in an earlier test.
Troubleshoot the relevant capture source
Once you know the active scene contains the right source, follow the branch for that source. Do not apply game-capture remedies to every black rectangle.
Game Capture
Game Capture is intended for supported games and can fail when the game, OBS, or another utility prevents the capture hook from working. First close and reopen the game after confirming that the source is configured correctly. Some full-screen games stop rendering when minimised or when you switch to another application. In that case, OBS may look black while the game is inactive even though capture works during play.
Test while the game remains visible. If you have another monitor, leave the game on one screen and OBS on the other. Otherwise, make a short recording while the game is active and check the file afterwards. This separates “capture fails” from “the application stops drawing when inactive”.
If the application does not capture in full-screen mode, try its windowed or borderless mode and then use the corresponding OBS capture method. OBS lists cases where Window Capture is the recommended alternative for applications that Game Capture cannot hook. That is a compatibility choice, not a universal hierarchy: a different game may behave better with Game Capture.
Temporarily close overlays, frame-rate counters, and other utilities that draw over or hook into the game. OBS identifies software such as RivaTuner Statistics Server and MSI Afterburner as possible conflicts. Test one change at a time, so you know which programme caused the difference. If you use a newer version of RivaTuner Statistics Server, follow the current OBS guidance for its compatible setting rather than copying an old tutorial.
On some systems, OBS and the game may be assigned to different GPUs. OBS's laptop troubleshooting guidance explains why GPU selection can affect Game Capture and Display Capture. On a multi-GPU Windows computer, check the current OBS instructions for your OBS version, Windows version, and capture type. Older advice about forcing a particular executable onto a particular GPU may not apply to newer capture methods.
Some games require OBS to run with administrator permissions. Treat this as an application-specific test, not a permanent fix for every black screen. Try it only after the basic source and conflict checks, and return to normal permissions if it changes nothing.
Window Capture
For Window Capture, confirm that the target window is open and that the correct window is selected in the source properties. If the application has several windows, such as a launcher and a player, choose the one that actually displays the image.
A window can also show a black interior while its menus or surrounding desktop remain visible. That may indicate a rendering or playback restriction rather than an OBS scene error. Try the application's supported windowed or borderless mode, update the application through its normal channel, and test with an ordinary unprotected window before drawing a conclusion.
Display Capture
Display Capture is useful as a diagnostic comparison when you need to know whether OBS can see the desktop at all. Open a simple window, such as a folder or text editor, and check whether it appears. If the desktop is visible but one video-player rectangle is black, the problem is probably specific to that player or its rendering path.
Do not treat Display Capture as a way to defeat playback restrictions. YouTube's help guidance discusses hardware acceleration while troubleshooting a green video-player screen, but that does not make disabling acceleration a universal OBS remedy or guarantee that protected video will become capturable. Test only content you have the right to stream, and check the current guidance for the browser and operating system you use.
Browser or media playback
If you are playing a file in a browser or media player and only that player area is black, compare it with an ordinary web page or a locally owned test file. A browser can render video through a path that behaves differently from the rest of the desktop. Hardware acceleration changes may alter that behaviour, but they can also introduce other display problems, so change them only as a controlled test and reverse the change if it does not help.
For a long-running channel, consider whether the player is necessary. If your source is an owned video file, loading it directly into OBS as a Media Source can remove a browser window from the chain. That does not solve rights or format issues, but it gives you fewer moving parts to diagnose.
Compare OBS preview with a local recording
A local recording is the most useful dividing line after the preview. It shows what OBS actually encoded or wrote to disk, rather than what the canvas appears to show.
Use a short recording with an obvious visual change. Do not rely on a still image, because a frozen frame can look like a successful capture. Include movement, a transition, or a spoken introduction. Stop the recording and open the file in a normal player before changing anything else.
If the preview and recording are both black, return to the source branch. If the preview is black but the recording contains video, check whether you were looking at the wrong scene, whether Studio Mode was involved, or whether the preview display itself was being obscured. If the preview is visible but the recording is black, inspect the output settings and the computer's ability to render and encode the scene.
OBS's encoding-performance guidance recommends considering the encoder, output resolution, frame rate, and scene complexity when assessing performance. A computer can meet the baseline OBS requirements and still struggle with a particular combination of sources and output settings. Baseline compatibility is not a promise that every scene will encode successfully.
Watch for dropped frames, rendering lag, encoder overload, or a recording that stops updating. These symptoms are different from a clean black file and can point to a performance problem. Reduce one demanding element for the test, such as a high-resolution source or animated browser content, and record again. Keep a note of the original settings so you can restore them after the diagnosis.
If you are running a 24/7 channel, do not use an overnight broadcast as the first test. A ten-minute local recording and a short private or unlisted live test are easier to inspect. Once the image is stable, you can use the practical checks in Running a 24/7 Channel as a Side Business: A Realistic Weekly Time Budget to plan monitoring rather than discovering problems during sleep.
If the preview is correct, inspect the programme and output path
When OBS preview and local recording are correct, stop changing the capture source. The remaining question is what OBS is sending to the live output and what YouTube is receiving.
First confirm that the local recording used the same active programme scene as the live test. In Studio Mode, the preview scene and programme scene can differ. A source may look correct on the editing side while the programme side still contains an empty scene or a hidden source.
Next check the stream settings and output destination. Confirm that the intended YouTube account and stream key are selected, and that you have not started a different OBS profile with another scene collection or output configuration. You do not need to expose the stream key while troubleshooting; treat it as a private credential.
Check the OBS status indicators while live. A stable connection does not prove that the image is correct, but warnings about dropped frames, rendering, or encoding help distinguish an output problem from a YouTube display problem. Make another short local recording during the live test if you changed any output setting.
If a local file remains visible while the live page is black, collect the OBS log, OBS version, operating system, GPU arrangement, source type, and the exact test result. Include whether the YouTube live control room preview is black, whether the public watch page is black, and whether both show the same thing. This evidence is more useful than saying only that “YouTube is not showing the stream”.
Do not assume that changing bitrate will restore a missing picture. Bitrate, resolution, and frame rate matter to the output, but a black live image with a healthy local recording can have a different cause from a source that never appeared in OBS. For background on the handoff between an encoder and a live platform, see What Is RTMP? The 5-Minute Explanation Every 24/7 Streamer Needs.
Check YouTube's preview and stream health
Open the YouTube Live control room and compare its preview with the public watch page. Allow for the normal delay, and use a recognisable visual event to compare them. If the control-room preview is visible but the public page is not, the issue is different from a black preview in both places.
Check that the broadcast is actually live and that the selected event or stream is the one connected to OBS. A channel with several scheduled events can make it easy to inspect the wrong watch page. Verify the title or event details without changing the stream key unnecessarily.
Review YouTube's stream-health messages and any warnings. They may identify a connection or format issue, but they do not replace the OBS-versus-recording test. If the health panel is normal and the local recording is visible, preserve the evidence and avoid random changes that make the original state harder to reproduce.
YouTube's official live streaming troubleshooting guidance is the appropriate reference for current control-room and playback checks. YouTube changes its interface, so use the labels shown in your account rather than relying on an old screenshot.
If viewers report black video while you see a normal preview, ask one viewer to test another device or network and note whether audio continues. A single viewer's playback problem is not proof that the broadcast itself is black. Conversely, several viewers seeing the same black image while OBS and the local recording are normal gives you a stronger case for an output or platform-side investigation.
For a long-running loop, also check the stream after a restart rather than only at launch. A source can appear during the first minutes and fail when the application changes state, the computer locks, or the player reaches a transition. The YouTube loop stream black-screen guide covers the separate checks that matter when a repeating broadcast changes state over time.
Make the next test safe to interpret
Troubleshooting becomes slower when several settings change together. Use a small test plan: one scene, one source, a visible moving image, a local recording, and a short live test. Change one item, repeat the test, and write down the result.
Keep the source type, OBS version, operating system, and GPU arrangement in your notes. These details determine whether advice about Game Capture, Window Capture, Display Capture, or GPU assignment applies. If you ask for help, include the result at each checkpoint rather than only the final symptom.
For overnight use, test the exact file and scene you intend to run. A still devotional image, a browser-based player, a game, and a long video file exercise different parts of the system. Confirm that the computer does not sleep, the source remains available, and the local recording remains visible before relying on the setup unattended.
If you want to remove the need for a computer to stay awake for a YouTube-only uploaded-video channel, StreamNeo can take an uploaded file, connect it to your YouTube stream key, and keep the broadcast running with automatic monitoring and restarts. That is a different operating model from diagnosing an OBS capture source, so first confirm that your content and channel workflow suit it.
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 preview black but my desktop is visible?
The active source may be hidden, aimed at the wrong window, covered by another source, or incompatible with the selected capture method. Check the scene first, then follow the branch for Game Capture, Window Capture, Display Capture, or browser playback rather than changing YouTube settings.
Should I use Display Capture instead of Game Capture?
Not automatically. Display Capture can be a useful diagnostic comparison, while Window Capture may suit an application that Game Capture cannot hook. The right choice depends on the application, its window mode, your operating system, and your OBS and GPU setup.
Why is the local recording fine but YouTube Live is black?
That places the failure after the basic capture test. Check the active programme scene, stream destination, stream key, YouTube event, control-room preview, and stream-health messages, then collect the OBS log and test details before changing the source.
Can disabling hardware acceleration fix a black video player?
It can change how a browser renders video, but it is not a guaranteed OBS fix and may not make protected content capturable. Test it only for content you have the right to stream, change one setting at a time, and reverse it if the result does not improve.