A black screen between videos in an OBS YouTube live stream can come from the scene or capture source, local rendering or encoding, or the outgoing stream. Compare OBS preview, a local recording and YouTube output first; the place where the fault appears helps choose the next check, but it does not prove one cause by itself.
If the preview is black, start with the active scene and source. If the preview looks right, test a recording and check OBS performance indicators and YouTube Live Control Room stream health rather than assuming that a healthy preview means the audience sees the same image.
Identify where the black screen appears
When the image disappears between clips, note the time and compare three views: the OBS preview, a recording made in OBS, and the YouTube live output. A short, controlled test is usually easier to interpret than changing settings during a long broadcast. Keep the same scene and content while you compare, and write down whether the screen is fully black, frozen on a frame, or simply waiting on a transition.
| What you see | Where to begin | What it suggests, not proves |
|---|---|---|
| OBS preview is black | Active scene, source visibility and capture target | A source or scene path may not be providing an image |
| Preview is visible, recording is black | Recording output, source behaviour at the transition, rendering and encoding | The preview is not a reliable test of the saved output |
| Preview and recording are visible, YouTube is black | OBS connection and performance indicators, then YouTube stream health | The outgoing path or ingest needs investigation |
| All views go black at the same point | Clip boundary, source switching and scene contents | The transition or media source deserves close inspection |
These are diagnostic starting points, not a formal set of exhaustive categories. A local recording is useful because it gives you another output to compare, but it cannot establish what YouTube received. Likewise, a visible preview tells you what OBS is composing at that moment, not that every later stage is healthy.
For a 24/7 playlist, mark whether every transition fails or only one particular video. If it is consistently the same clip, inspect that source and the scene change around it. If different clips fail at different times, record the OBS status counters and YouTube health messages as well. If the symptom is really the wrong item starting rather than a black image, the separate checks in why a scheduled YouTube livestream can start the wrong playlist may help distinguish playlist selection from a display fault.
If OBS preview is black, check the scene and source
First select the scene that is actually live. OBS can have several scenes with similar names, and the preview may show a different one from the scene you intended to use. In the Sources list, check that the expected source is present and visible. Also check whether an opaque image, colour source, browser layer or other item above it is covering the picture.
Look at the source itself. A Game Capture source needs to point at the intended game; a Window Capture source needs the correct window; a Display Capture source needs the monitor you expect. If a video source is inactive, stopped, or waiting for media to begin, the scene may show black until it has something to display. Check the source properties and, where relevant, whether the media file plays normally outside OBS.
For video sequences, transitions can expose a gap even when each clip works on its own. Test the same two videos in a simple scene, without overlays or other sources, and watch the change from the end of the first clip to the beginning of the next. That comparison can tell you whether the black interval follows a source change or exists within the clip itself. Do not infer from a single transition that every video file or every scene needs the same setting.
If the black image is from Game Capture, use the guidance for the selected game and capture mode in the OBS Game Capture troubleshooting guide and its Game Capture source guide. Some modes work only while the chosen game is open or active. A fullscreen game can stop rendering while you switch to another window; an empty preview after alt-tabbing is not, on its own, proof that the source is broken. Try a recording or observe OBS on another display while the game remains active.
The OBS guidance includes game-specific workarounds, not a universal recipe. For a particular game it may be worth testing Window Capture, windowed or borderless mode, or running OBS as administrator; another game may need a different approach. Follow the guidance for the game in question rather than applying every workaround at once. On a laptop or all-in-one with more than one graphics adapter, capture compatibility can also depend on the system and OBS version. The OBS laptop troubleshooting guide is a better starting point than assuming a single menu path applies to every Windows build.
Check visibility and capture mode
Visibility is simple to overlook when scenes are edited in a hurry. Confirm that the eye or visibility control for the intended source is on, then inspect the order of sources. A source can be enabled yet hidden behind a full-screen layer. Temporarily hide other sources one at a time, or make a minimal test scene containing only the image source. If the picture returns, add the other elements back individually to find what covers it.
Then confirm the capture mode and target. A Game Capture source may be set to capture a selected window or a game according to its mode; the selected target must match the content you are showing. Window titles can change, and a game launcher is not the same thing as the game window. For Display Capture, verify the display selection. For Window Capture, check that the intended application window is still open and that OBS has not been pointed at a different window.
Change one variable at a time. For example, leave the scene as it is and test the same source with the game active. If it remains black, try a game-specific mode from OBS's documentation. If the picture appears, repeat the test after the next transition. Keeping a note of the original setting makes it easier to reverse an experiment and stops several simultaneous changes from obscuring the cause.
If another capture method gives a picture, treat that as evidence about the path you tested, not proof that the first method is always unsuitable. A Window Capture workaround may be useful for one title, while a game-specific guide may recommend another approach for a different one. On multi-GPU systems, the graphics adapter used by OBS and the one used by the captured application can matter. Check the OS and OBS version before following instructions written for another configuration.
If preview is fine, inspect local rendering and encoding
A clear OBS preview does not establish that the recording or live output is clear. Make a short local recording that includes the transition where the problem usually appears. Play the file in a normal media player and note whether the black interval is present. If it is, the problem is not limited to what YouTube displays: investigate the source change, scene complexity and OBS rendering or encoding performance.
Use a deliberately simple test scene. Keep the video source and any essential audio, then disable resource-heavy browser sources, animated overlays and other elements temporarily. Repeat the same transition. OBS's encoding performance troubleshooting guide explains why GPU load, complex scenes and demanding sources can contribute to performance trouble. If simplifying the scene changes the result, restore sources one at a time to identify what adds load.
The aim is to isolate variables, not to make the permanent broadcast unattractive. A devotional channel might temporarily test just the bhajan video and a static title card; a study stream might keep the looped footage but remove a moving clock and browser widget. If a simple setup works, add the normal elements back gradually and observe whether the failure returns at a particular transition.
Do not choose a new resolution, hardware purchase or encoder preset based only on the words “black screen”. The symptom does not identify the computer, source type, operating system, graphics setup or OBS version. Change output settings only when a measured performance issue or documented requirement gives you a reason, then compare the recording and live test again.
Also consider software that can interfere with capture. OBS lists overlays and monitoring applications, some security software, and other recording or capture tools among potential conflicts. Temporarily close non-essential candidates and repeat the same controlled test. If that helps, reopen them one at a time; it is a way to isolate a conflict, not an assertion that every black-screen fault comes from other software.
For a channel built around repeated prerecorded videos, check the transition and file sequence as carefully as the OBS scene. A black interval in the source media will remain black in the broadcast. If your actual need is to combine a folder of video files into a continuous loop, the guide to looping a folder of gaming VODs with FFmpeg covers a different playback workflow; it does not replace checking the OBS output when OBS is the tool in use.
Check OBS dropped frames and performance
While the stream is running, look at OBS status information rather than relying on the preview alone. Note whether dropped frames are increasing, whether there are disconnections, and whether performance indicators show rendering or encoding strain. Record the time a black interval occurs and compare it with any change in those indicators. One observation is a clue; a pattern repeated during a controlled test is more useful.
OBS explains that increasing dropped frames can indicate an unstable connection between the computer and the remote ingest server, or a bitrate the connection cannot sustain. That is a network branch of troubleshooting, distinct from a source that is black in the preview. Consult OBS's stream connection troubleshooting guide and use YouTube's encoder settings guidance to choose settings suited to your upload and test the stream. Do not treat changing bitrate as a guaranteed black-screen fix: the counter and the test result should support that decision.
If rendering or encoding indicators point to load rather than connection trouble, return to the simple-scene test. Close unnecessary high-resource sources, check whether a particular overlay or transition coincides with the issue, and compare results. Keep a note of the OBS version, source type and what changed. That information is more useful than making several changes and then being unable to tell which one mattered.
For a long-running channel, test before returning to normal programming. Use a suitable private or unlisted test arrangement if that fits your channel, include movement and audio, and allow time to see the transition that previously failed. This is a practical way to observe the result, not a guarantee about how a public broadcast will behave under every condition. For network interruptions specifically, choosing a YouTube RTMP server region to reduce stream interruptions is relevant when the connection path is the concern; it is not a substitute for diagnosing a black OBS source.
Read YouTube Live Control Room health messages
When OBS preview and the local recording look normal but viewers see black, check the YouTube Live Control Room during the test. Read the stream-health messages and note their timing alongside OBS counters. YouTube recommends testing encoder settings and monitoring stream health; its messages provide evidence about the stream reaching YouTube, but they do not automatically identify a particular scene or capture setting as the cause.
If YouTube reports a health issue, follow the message and the current official guidance rather than changing unrelated source settings. If no clear message appears, do not assume the stream is fine: compare what you see in the live output with the recording and note whether the issue is repeatable. A YouTube-only symptom after a good local recording narrows the next checks towards the outgoing stream and ingest, but is not proof of one specific fault.
Avoid diagnosing an ingest problem from a viewer report alone. Ask when the black screen happened and whether it was visible in the live player, the archived video, or both. A short test with an identifiable scene change makes it easier to align that report with OBS status and the Control Room. The purpose is to gather evidence before adjusting the stream, not to promise that any dashboard state prevents a later fault.
A 24/7 stream also needs a way to recover from interruptions, separate from finding the original fault. If a crash or disconnect is the issue rather than a black scene, the PRISM Live Studio restart guide discusses that recovery question. Restarting a stream will not repair a source that remains invisible or a recurring gap inside the video.
Make a repeatable test before changing the live setup
Use a short checklist so that the next attempt answers a question. Record the operating system and OBS version, source type, selected scene, graphics setup if known, whether the local recording also went black, and the OBS counters at the time. If you need help from someone familiar with OBS, a log from the affected session and those details are more actionable than “YouTube went black”. Do not share your stream key when asking for support.
Run the test with one known video transition and keep the setup otherwise stable. First observe the preview, then save and review the recording, then inspect the YouTube output and health messages. If the problem is intermittent, note the time and repeat rather than changing several settings after one occurrence. That sequence makes it easier to distinguish a scene/source issue from output or connection trouble.
Once a change appears to help, test it again with the ordinary scene and overlays restored. A fix that works only in a stripped-down scene may show which source is causing trouble, but it does not yet confirm that the full overnight layout is stable. Keep the old settings recorded until the normal setup has been tested, so you can reverse the change if another symptom appears.
If the difficulty is keeping a prerecorded channel running after you have resolved the OBS diagnosis, StreamNeo can take away the need to leave your own computer on for a file-based YouTube broadcast; that is a different operating approach, not a repair for an OBS capture fault.
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 does the screen go black only between videos?
The transition may briefly expose a scene with no visible source, a source that has not started displaying its next file, or a gap in the media itself. Compare the same transition in preview and a local recording, then test it in a simple scene before changing unrelated output settings.
Does a good OBS preview prove YouTube is receiving video?
No. The preview shows what OBS is composing, not whether the recording or outgoing stream is healthy. Compare a local recording and YouTube output, then check OBS status and Live Control Room health messages.
Should I change bitrate to remove the black screen?
Only if the evidence points towards a connection problem, such as increasing dropped frames or disconnections, and a test supports the change. A black preview or a black local recording calls for source or performance checks first; bitrate is not a universal fix.
What details should I collect if the problem continues?
Write down your operating system and OBS version, source type, whether preview and recording also went black, and any dropped-frame, performance or YouTube health messages at the time. Include a log from the affected OBS session if you ask for troubleshooting help, but never include your stream key.