If your 24/7 study stream is black, first check whether the picture is missing in the OBS preview, in YouTube playback, or in both. Then identify whether the scene uses Display Capture, Window Capture, Game Capture, or another source; the useful fix depends on that combination, not on one universal cause.
A blank preview usually points you towards the source or its capture settings, while a correct preview paired with a blank or buffering YouTube stream calls for a separate output and connection check. Work through the branches below one change at a time, and verify the picture before leaving the stream unattended.
Check where the picture disappears
Look at the OBS preview while the stream is meant to be showing your study scene. If it is black there, start with the scene and source: is the source enabled, is the correct window or display selected, and is the source type appropriate? You do not yet know that a GPU setting or a particular capture method is at fault.
If the preview is correct but the audience reports black video, keep the capture source as a separate possibility rather than immediately changing it. Check whether OBS reports that it is streaming, whether the stream has an active connection, and whether the YouTube player is showing black, buffering, or an error. These symptoms may look similar to viewers but point to different parts of the chain.
If both preview and YouTube are black, the live output may simply be receiving the same blank scene. Confirm that OBS is sending the intended scene and that no transition or scene change has left a different, empty scene active. Then diagnose its sources.
A useful distinction: a black source in preview is not the same thing as dropped frames or an intermittent disconnection. OBS describes dropped frames and disconnections as problems with the connection between your computer and the streaming ingest server. For that branch, use separate steps for a stream that keeps reconnecting, rather than treating network changes as a remedy for a source that is already black in OBS.
Identify the source type
In the Sources list, identify the item responsible for the study picture. Common choices include Display Capture for a whole desktop, Window Capture for one application, and Game Capture for a Windows game. On macOS, OBS describes a Screen Capture source instead. The OBS Quick Start Guide explains the source types and their intended uses. Match the following checks to what you actually added.
| Source in the scene | What it is intended to show | First thing to verify |
|---|---|---|
| Display Capture | A desktop or display | The selected display and, where relevant, the capture method |
| Window Capture | One application window | The selected application and whether its window is available to capture |
| Game Capture | A Windows game | Whether the scene is intended to capture a game, rather than a study app or desktop |
| Other or custom source | A browser, media, or other input | The source’s own status and settings in OBS |
This is a diagnostic map, not a guarantee that a given source will work in every operating system or OBS version. A study stream may show a timer, a document, a music player, a looping visual, or a whole desktop; choose a source for the actual picture you need, not merely the source name you remember using. If you are unsure, inspect the source properties and note its type before editing anything.
For a study scene built from a desktop and a separate application window, there may be more than one source in the scene. Check which source is meant to provide the visible picture, and whether another source is covering it. Avoid deleting and rebuilding the scene until you have written down its current source names and settings.
Check source visibility and settings
In OBS, a source can exist in a scene without being visible. Check the visibility control beside the source name, then make sure the source is not hidden behind another opaque source in the list. If you use a group, expand it and inspect the individual items. A hidden source or a source covered by a background can produce a black-looking preview even if its capture configuration is otherwise correct.
Select the source and open its properties. Confirm that it refers to the intended display or window, rather than an old monitor, a closed app, or a similarly named window. If the application was restarted or the display arrangement changed, reselect the intended target where the source offers that option. Do not change several options at once: note the current value, make one adjustment, and check the preview.
Also check whether the source has been transformed or cropped out of the canvas. Select it and inspect its position and size; use the preview to see whether the content is simply outside the visible area or reduced to a thin edge. A black rectangle in the scene may be a deliberately added background, an image source, or a media source that is not playing, rather than a failure in the desktop capture. Temporarily hide other sources one by one to isolate which item is producing the visible result.
If you need to reconstruct a scene after diagnosis, keep the study elements plainly named, such as “desktop”, “timer window”, and “background”. A tidy scene makes it easier to tell whether the problem is one source or the complete output. For an always-on setup, document the working source selection so you can restore it after a software or display change without guessing.
Troubleshoot display, window, and game capture separately
If Display Capture is black
First confirm the selected display and whether that display is active and showing the intended content. If the source properties offer a capture-method choice, record the current option before testing another. On Windows, OBS documents a specific case: for Windows 10 version 1903 or higher with OBS 27 or higher, its newer display capture method applies; if Automatic does not work, the laptop troubleshooting guide suggests manually trying “Windows 10”. See the current OBS laptop troubleshooting guidance before using that version-specific step.
That instruction is not a universal Windows fix, and it should not be applied to macOS or Linux. The guide is older than many current Windows and OBS releases, so recheck the current documentation and the labels in your own version before changing the method. If you do not have the stated Windows and OBS versions, continue with the source and system checks rather than assuming the same option is appropriate.
On a Windows laptop with integrated and discrete graphics, GPU assignment can affect capture. OBS has separate advice for laptop troubleshooting and for GPU selection by source type; the recommended GPU can depend on whether you use Display Capture or Window/Game Capture. Read the OBS GPU selection guide for your source and follow its current instructions for your Windows version. If a setting requests that you restart OBS, do so before judging the result. Do not copy a GPU choice from another person’s setup without checking which source they use.
If Window Capture is black
Make sure the target application is open, its window is present, and the source properties select that exact window. If several windows have similar names, identify the correct one by opening the application and checking the selection again. A minimized, closed, or replaced window may not be the same target you configured earlier.
If the window remains black, do not switch immediately to unrelated display or network settings. Note your operating system, OBS version, application, and whether the issue began after a change. OBS source behaviour can depend on the system and capture configuration; the available facts do not establish one fix for all Window Capture cases.
If Game Capture is black
Game Capture is a Windows-only source in the OBS Quick Start material and is intended for games, not as a general way to capture a study desktop. If your scene is showing a timer, notes, or a browser, use the source type suited to that content rather than assuming Game Capture is the right choice. If the study stream genuinely includes a Windows game, check that the intended game is running and selected, and consult OBS’s current guidance for your setup.
For a multi-GPU laptop, follow the GPU selection advice for Game Capture rather than borrowing the Display Capture recommendation. If you are not using Windows, do not apply Windows-only Game Capture or GPU steps. Record the source type and system details first, then choose the matching official instructions.
Check the OBS preview after each change
After each single adjustment, look at the preview and wait long enough to see whether the intended content appears. If it returns, avoid further changes that are not needed. If it stays black, restore the previous setting if the new one made no difference, then proceed to the next relevant check. This keeps your troubleshooting reversible and helps you identify what actually changed the picture.
If the preview is choppy rather than black, or OBS reports rendering or encoding strain, that is a different branch. OBS’s encoding performance troubleshooting guide discusses reducing load, including simplifying scenes and reducing output resolution or frame rate where needed. Those adjustments may help overloaded rendering or encoding; they are not a confirmed fix for a source that is blank in preview.
A 24/7 stream also needs a realistic preflight, not only a momentary image check. OBS recommends testing settings for a few minutes before relying on them. For a channel you intend to leave running, extend your own validation to include the actual scene, normal content changes, and the time of day when the computer is usually unattended. That longer test is a prudent operating practice, not a guarantee that the stream will run continuously.
Before leaving the stream, confirm that the picture remains correct after switching scenes or reopening the study application, and note any OBS status warnings. If a change fixes the source, keep the tested configuration and avoid unrelated updates immediately before an unattended session. No particular test duration can guarantee that a long-running broadcast will remain uninterrupted.
Verify the live picture in YouTube
A good OBS preview is necessary, but it does not prove that viewers receive a good picture. Start a private or otherwise appropriate test broadcast if that suits your channel, then check the YouTube live destination in a separate browser or device. Confirm that the picture appears and moves as expected, that audio is appropriate if used, and that the stream is not merely showing a buffering state.
If OBS preview remains correct while YouTube is black or repeatedly buffering, check OBS’s stream status and YouTube’s live controls, then investigate output and connection. OBS’s connection troubleshooting guide says dropped frames or intermittent disconnections point to an unstable connection to the ingest server or a bitrate the connection cannot sustain; it includes wired networking as one troubleshooting step. See OBS stream connection troubleshooting. This is not a reason to buy equipment for a black source in preview.
For a fixed study scene, a few minutes of working playback is useful but does not test every overnight condition. Observe the actual destination, not only the local preview, and check again after the scene has run through any normal changes. Keep a note of whether the failure is blank video, buffering, a stopped stream, or dropped frames; those observations make later diagnosis more precise.
If the picture disappears only after the broadcast has been running, note the time, whether OBS still shows the source correctly, and what its stream status indicates. A source that remains visible locally while the destination loses playback points you towards output or connection evidence. If the local preview also goes black, return to the source branch and note what changed in the scene or target application.
When to gather more system details
If the source-specific checks do not restore the picture, stop making speculative changes and gather details that determine which advice applies. Record your operating system and version, OBS version, exact source type, whether the preview is black, and whether YouTube playback is black, buffering, or disconnected. For a Windows laptop, note whether it has integrated and discrete graphics and which GPU assignment or capture-method settings you changed.
Include what happened immediately before the problem began: an OBS update, an operating-system update, connecting a monitor, changing display arrangement, restarting the captured app, or editing the scene. If the problem is intermittent, write down when it occurs and whether the OBS preview and YouTube output differ at that moment. A screenshot of the Sources list and source properties can be more useful than a long description, provided it does not expose private material.
For an always-on channel, keep a small recovery note with the working scene, source type, and the last known-good settings. If a computer restart, power cut, or scheduled maintenance is also part of the problem, separate that from the capture failure; the practical considerations in this guide to keeping OBS running during scheduled power cuts in India concern continuity of the computer, not a guaranteed fix for a black source.
If the video is correct but the channel’s study material itself needs to loop reliably, treat that as a separate content and playback question. A useful checklist for organising files for an always-on YouTube stream can help with file preparation, but it will not resolve a capture source that is black in OBS.
If you cannot identify the cause, share the system details with an appropriate OBS support channel and describe what you have already tested. Ask for guidance tied to your exact source, operating system, OBS version, and graphics setup rather than requesting a universal black-screen fix. Do not assume that replacing a GPU, display, cable, or capture device is necessary based only on a blank preview.
For a study stream that does not need a live desktop or interactive capture, a file-based broadcast may avoid the specific task of keeping OBS open on your computer. StreamNeo can take that computer-off workload away when your study picture is already prepared as a video, but it does not diagnose or repair an OBS capture source and it is for YouTube only.
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 YouTube has no picture?
When the preview itself is black, first inspect the scene, source visibility, selected target, and capture settings. YouTube may be receiving that same blank scene, so confirm the preview before changing connection settings.
Why is the OBS preview fine but the YouTube stream is black?
That points away from a wholly blank local source, but it does not identify the cause by itself. Check OBS stream status, the YouTube live destination, and whether the symptom is black video, buffering, or disconnection; investigate connection issues separately.
Should I change GPU settings to fix every OBS black screen?
No. GPU guidance is relevant only in particular setups, including some Windows laptops with more than one GPU, and OBS distinguishes recommendations by capture type. Check the official instructions for your source and system before changing an assignment.
Can a black preview be fixed by lowering bitrate?
Not necessarily. Bitrate and connection checks belong to an output or network problem, while a source that is black in preview needs source and capture diagnosis first. Lowering resolution or frame rate is a possible response to performance strain, not a universal black-screen remedy.