If you are asking how to fix OBS showing a black screen between videos on YouTube Live, first check whether the black appears in OBS’s own preview or only on YouTube. That distinction tells you where to investigate next; the OBS documentation describes source behaviour, but does not confirm a YouTube-specific fault or a single cause for this symptom.
If OBS preview also goes black, work through the scene and source that should be showing at that moment. If OBS remains correct while YouTube viewers see black, keep the diagnosis open and gather evidence before changing unrelated OBS settings.
Locate where the screen first goes black
Watch the OBS preview during a gap, not just before and after it. If you can, have someone check the YouTube playback at the same time. Write down whether both views change together, and whether the change follows a clip ending, a scene switch, or some other repeatable event.
A black image in the OBS preview points first to something in the local composition: a source may be hidden, covered by another source, between playback events, or reloading after becoming active. It does not prove which of those is responsible. Check the state of the scene and the source at the time of the gap rather than selecting a familiar fix in advance.
If OBS’s preview looks correct while the YouTube stream is black, you have located a difference between the local view and the viewer-facing result. That is useful evidence, but it does not by itself show whether the issue is in transmission, platform playback, or some other part of the path. The OBS help material cited here does not establish a YouTube-only cause. Media Source settings are worth checking when the local preview also reflects a playback gap; they are not a proven remedy for a discrepancy visible only on YouTube.
For a useful first record, note the time, the scene name, the source type, and what both views showed. A brief screen recording of the OBS preview and the YouTube playback can make an intermittent boundary easier to describe. Avoid restarting everything before you have captured what the fault looks like, if doing so would erase information you need.
Check OBS scene and source visibility
In the Sources dock, find the source that should supply the video and check its eye icon. A disabled eye means the source is not visible in the scene. If the eye is enabled, inspect the order of sources: OBS displays sources higher in the list above lower ones, so an opaque source above a video can cover it. A still image, colour source, browser source, or another media source may be relevant if it occupies that part of the scene.
Source visibility can change between scenes or through deliberate actions in a production. Compare the scene shown during the black interval with the scene used while the video is visible. Do not assume that a source being present in the Sources dock means it is visible in the current scene, or that the same source is enabled in every scene where you have added it.
The OBS guide to sources and their order explains the visibility and stacking model. Use it to confirm the labels in your installed version, since menus and controls can change. If moving a source temporarily helps isolate an obstruction, do that in a test scene or note its original position first; moving sources in a live production can alter the layout viewers see.
A simple isolation test is to duplicate the scene, then temporarily hide everything except the suspected video source and any required background. Run a short test and see whether the gap remains in preview. This is not a permanent scene design: it is a way to reduce the number of moving parts. If the simplified scene behaves differently, restore sources one at a time and observe which change correlates with the black interval.
Also check transforms and canvas placement if the source appears to be present but not where expected. A source can be cropped, resized, or positioned outside the visible canvas. Those conditions are different from a black frame inside the video itself, so distinguish an uncovered canvas from a source that is actively outputting black content.
Inspect video source playback and transitions
First identify the source type. An individual file added as a Media Source, a VLC playlist, a display capture, a window capture, and a game capture do not share the same playback controls. The OBS sources guide describes these categories. Follow the controls for the source actually used rather than searching for a setting that belongs to another source type.
For an OBS Media Source, open its properties and inspect Loop and Show nothing when playback ends. Loop controls whether the file repeats when it reaches its end. Show nothing when playback ends can make the source disappear after playback finishes, which may leave the scene’s background or another source visible. Neither setting is universally correct: looping suits a clip meant to repeat, while a playlist or scene change may be more appropriate when you intend to move on to another segment.
Check Close file when inactive as well. OBS documents that this option unloads an inactive or hidden file to free memory, and that switching back to a scene using that source can leave it temporarily not showing while it reloads. If your black interval follows a scene switch, compare a controlled test with this option enabled and disabled. Do not assume that every delay is caused by this setting; record what changes and restore the intended configuration after testing. The Media Sources documentation describes these controls and their effects.
If the source is VLC Video, inspect the playlist and its own loop and visibility behaviour controls instead of applying Media Source instructions. OBS’s documentation notes that VLC Video needs VLC installed, and that 64-bit OBS requires 64-bit VLC. If a playlist is meant to bridge several clips, check the actual order, file availability, and playlist behaviour in a test rather than treating the source as a single file. Those checks establish what OBS is asked to play; they do not establish a cause for a YouTube-only black interval.
Transitions deserve a separate check. If the scene changes when one clip ends, observe whether the transition reveals a scene with no visible video source, or whether the transition itself is simply showing the underlying background. Temporarily use a straightforward cut in a test scene and keep the same clips and source order. If the gap changes, you have learned that the scene-change path matters; if it does not, restore the normal transition and continue with source playback checks. This test narrows the investigation rather than proving a general transition fault.
A holding image or a deliberate transition to another scene can be more appropriate than exposing an empty canvas. Decide what viewers should see at a natural clip boundary: the next clip, a static holding card, or a clearly intentional pause. Then configure the source and scene around that outcome. If you are designing a continuous prerecorded playlist, the guide to looping podcast video in OBS covers a related workflow, while the guide to keeping a live stream running after its first video ends addresses continuity beyond a single file.
Compare OBS preview with the YouTube stream
Run a private or otherwise suitable short test if that fits your channel and audience. Compare the same moment in OBS and in YouTube playback, allowing for the fact that the viewer-facing stream may not show the exact same instant as the local preview. Do not use a brief timing difference as proof that the images disagree; match the event by its content, a visible time cue, or a distinctive frame.
If both views show black at the clip boundary, return to the scene and source checks. Confirm whether the clip has ended, whether another source is covering it, and whether a scene switch or reload happens at that time. Change one setting at a time and repeat the test. If you change several controls together, you may remove the symptom without learning what mattered, making a recurrence harder to diagnose.
If only YouTube shows black, preserve that distinction in your notes. Check that you are comparing the intended live output and not a delayed or stale playback view, and ask another viewer to report what they see if possible. The evidence available for this article does not identify a particular YouTube setting or fault as the cause, so it would be misleading to promise that changing OBS’s Loop or end-of-playback settings will fix this case.
Check the stream’s status and any warnings shown in the interfaces you are using, but do not infer a cause from a status label alone. If the local preview is sound and the viewer-facing output differs, keep a timestamped record and consult current official guidance for the relevant part of your setup. The YouTube Help centre is the primary place to check current platform guidance; the exact next step depends on what the stream and account interfaces report.
For a 24/7 channel, avoid experimenting on the only live scene while an important broadcast is running. A duplicate scene or an off-air test reduces the risk of disrupting the programme. If a change has to be made live, make one reversible adjustment, note the time, and watch both OBS and the viewer-facing stream before making another.
Use timestamps and a short controlled test
Intermittent faults become much easier to compare when you can point to a boundary. Note the time a clip should finish, the time the next clip should begin, when black first appears, and when the intended image returns. Record whether audio continues, whether the OBS preview is affected, and whether a scene switch or source reload occurs. These observations are more useful than a general note that the stream went black overnight.
Create a short test with the same source type and relevant settings, but keep the scene simple. Use two clips if the failure occurs between clips, and observe at least one boundary. Preserve the original scene and settings, then change just one candidate at a time: for example, the end-of-playback behaviour or Close file when inactive. A test that does not reproduce the issue is still informative, but it does not rule out a problem that depends on a longer schedule or another source.
You can also compare a run with a static holding source against a run without it. If a visible holding image replaces the black in OBS, that shows the scene can display another source at the boundary; it does not establish why the original video was absent. Keep the purpose of each test narrow and write down the result before changing the next setting.
If you need to test a lengthy playlist or continuous channel, plan the test so a failed experiment does not leave viewers with an unintended blank scene. The guide to setting up a home streaming studio may help you think through a separate test setup. For channels built around a long-running file rotation, the prerecorded YouTube Live playlist guide describes a different workflow; it is useful context, not a diagnosis of an OBS preview gap.
Keep a small change log: test time, the single setting changed, preview result, YouTube result, and whether the change was reverted. This prevents a common troubleshooting trap: several settings get altered, the symptom disappears for one run, and nobody knows which adjustment to retain. If a change appears helpful, repeat the same test before treating it as a reliable fix.
Match checks to the capture source
If the black content is supposed to come from a game, use Game Capture troubleshooting rather than Media Source playback advice. OBS recommends checking that the source is set up correctly, considering software conflicts, and looking at multi-GPU configuration. If the captured source has the wrong size or a stuck transform, OBS documents Reset Transform and Fit to Screen as relevant checks. These are scoped to game capture and do not explain a gap between ordinary local video files.
Display and window capture have their own boundaries: the selected display or application must still be available, and the capture source must be visible in the active scene. Test those sources directly in OBS before changing media-file playback properties. If the source is a camera or capture device, check whether its own image is present in preview; a black device image is a different path from an ended video file.
Rendering performance is a secondary possibility only when other signs support it. OBS uses GPU resources to compose the scene, so a complex scene or resource-heavy sources can contribute to performance problems. If the preview is also dropping frames, stuttering, or showing other rendering strain, simplify the scene and test again. The OBS encoding performance troubleshooting guide gives further checks. Performance should not be treated as the default explanation for every clean black interval between clips.
When to gather logs or seek further diagnosis
Escalate when a controlled test does not explain the result, especially if OBS preview and YouTube playback disagree. Collect the OBS log from a session that includes the issue, along with the timestamp, OBS version, source type, scene name, and a concise account of what changed. Include whether audio continued and whether the local preview was black. Remove stream keys and other account credentials from anything you share; these are private access details, not troubleshooting evidence for a public post.
Before asking for help, make a copy of the scene or settings you are testing and describe the reproduction steps plainly: which source plays, what event precedes the gap, and whether changing one setting altered the result. Avoid saying that a particular setting “fixed YouTube” if the only observed change was in OBS preview. Keep observations separate from conclusions so someone else can reproduce the same path.
Use current OBS documentation or a suitable support channel for an OBS-side issue, and current YouTube Help for an issue visible only in the YouTube playback path. When neither side is established, say so. A clear unresolved report with timestamps and matching local and viewer-facing observations is more useful than a confident but unsupported diagnosis.
For an always-on channel, you may also decide that the laptop should not have to remain powered and logged into OBS overnight. StreamNeo removes that specific operational burden by letting you upload a video, provide your YouTube stream key, and leave the broadcast running with your computer off; it does not determine the cause of an OBS black interval or replace checking the stream itself.
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 OBS show a black screen between videos?
There is no confirmed single cause for this exact symptom. Start by checking whether the preview is also black, then inspect source visibility, layer order, and the playback behaviour for the source type in use.
Should I turn on Loop in Media Source?
Only if you want that file to repeat after it finishes. If the intended behaviour is to move to another clip or scene, inspect the playlist or scene transition instead; Loop is not a universal fix for a gap.
What if OBS preview looks normal but YouTube is black?
That difference does not establish a YouTube fault or show that Media Source settings will fix it. Record timestamps, compare the same content in both views, check current official guidance, and seek diagnosis for the part of the stream path that remains unclear.
Can performance overload cause the black interval?
It is worth considering if OBS also drops frames, stutters, or shows other signs of rendering strain. A clean gap exactly at a clip boundary points you first towards source and scene behaviour, but the observation alone does not prove a cause.