“YouTube Live disconnecting when streaming a video playlist” can mean that the live event ended, that YouTube stopped receiving the encoder, or simply that the video source stopped playing. Check the live event and the encoder together before changing playlist settings.
If OBS remains connected while the picture freezes, goes blank or starts again, investigate the source and its playback settings. If YouTube reports an ingest problem or the event ends, look instead at encoder output, network conditions, stream configuration and any account or copyright notices. Looping fixes media that reaches its end; it does not repair a failed connection.
First establish what actually stopped
At the next interruption, note the time and check the YouTube Live Control Room and OBS at the same moment. Ask three separate questions: did the live event end, did YouTube report a stream-health problem, or did only the playlist image or sound stop while OBS still appeared to be live? Those observations determine which part of the setup to investigate.
A source ending at its final file may leave the broadcast open with a still, blank or otherwise unchanged picture. A source that restarts may show its first item again even though the live event never ended. By contrast, an encoder crash can stop sending video while the YouTube event is waiting for data, and a weak outbound connection can interrupt delivery even if local playback appears normal.
If several viewers report the same break at the same time, it is less likely to be a problem on one viewer’s device. Compare their reports with the control room and encoder log rather than asking each person to troubleshoot local playback. Keep a short incident note: time, visible symptom, OBS state, YouTube health message and whether the source resumed by itself.
This distinction also matters for a long devotional, study or ambience channel. A playlist that reaches the end is a content-continuity problem. A live event that ends is a broadcast-continuity problem. They can happen together, but one observation does not prove the other caused it.
Read stream health in Live Control Room
While the broadcast is active, open YouTube Live Control Room and inspect its stream-health messages around the interruption. The status and any error text provide evidence about whether YouTube is receiving a usable feed. YouTube advises streamers to watch stream health and test their encoder and settings before an event; see YouTube’s live encoder settings guidance.
A warning about bitrate, missing frames or unstable ingestion points towards the delivery path or encoder configuration, not whether OBS has Loop Playlist selected. If the control room says the stream is healthy while OBS’s source has stopped on the last frame, the source branch deserves attention first. The status is useful evidence, not a complete diagnosis: compare it with the local preview and logs.
Check whether the event is still live, whether a preview is receiving data, and whether the stream-health message changes when the picture disappears. Write down the exact wording rather than relying on memory. A brief ingest warning near the same timestamp as a source restart can indicate two overlapping symptoms, so preserve both pieces of evidence.
If the encoder cannot start or YouTube reports a key or server configuration problem, verify the current stream URL and key in Live Control Room. YouTube’s live stream troubleshooting steps include checking encoder output, the upload connection and stream-key configuration. If you replace or reset a key, update the encoder with the current one and keep it private. Changing a key is a recovery step for a configuration problem, not a fix for a playlist that simply ran out of files.
Also look for notices in YouTube Studio or Live Control Room. YouTube scans live streams for third-party content; a match can lead to a placeholder, interruption or termination. Its guidance on copyright issues with live streams explains that licensed content may still be interrupted if the rights owner has not allowlisted the channel. A copyright notice calls for checking the rights and account status, not changing bitrate or enabling a loop.
Compare OBS preview and logs
Look at OBS’s program output and the preview, not just the status label that says it is connected. If the preview itself goes blank, freezes or returns to the opening frame, the problem is visible before YouTube ingest enters the picture. Check the OBS log around the time of the event for source errors, reconnects, encoder warnings or other messages that line up with what you saw.
If OBS preview and sound remain normal but YouTube’s health changes, do not conclude that the connection is fine. The preview represents the local composition; it does not prove the outbound signal is reaching YouTube steadily. Conversely, if both local preview and the archive show the same freeze or damaged picture, investigate the source or encoding path as well as the network.
Check the computer’s load while the stream is running. High CPU use, an encoder error or competing work can affect the output even when the media files are sound. If OBS has saved a local recording, review the section around the failure: it can show whether the picture or audio problem existed before upload. YouTube’s troubleshooting guidance similarly recommends checking encoder software, output quality, CPU load and a local archive when available.
Update OBS to a current release before relying on it for an extended broadcast, but do not assume that an update alone will resolve a recurring interruption. Save the log from the affected session and make one change at a time during testing. Otherwise, a changed source, encoder setting and network path can obscure which adjustment made a difference.
For settings such as codec, resolution, frame rate, keyframe interval and bitrate, compare the actual encoder output with YouTube’s current recommendations for that configuration. Do not raise bitrate reflexively. A higher setting that exceeds a stable upload connection can make delivery less reliable; choose a quality your connection can sustain and check health during a test.
Check the active scene and playlist source
In OBS, confirm that the scene currently on air contains the intended source. A playlist configured correctly in a scene that is no longer active will not keep the program output moving. Check the source’s visibility and whether switching scenes or hiding it changes playback; some source behaviours can stop or restart playback when a source becomes hidden and visible again.
For multiple local files, OBS documents the VLC Video source as the playlist-capable source. The source may not appear if VLC is not installed on the computer. See the OBS guide to media sources for its VLC Video and Media Source controls. If your scene uses a different source type or a browser-based player, its controls may not match the VLC playlist steps below.
Select the source and inspect its properties rather than assuming the visible item is the one playing. Verify that the intended files are listed, and confirm that the source is not obscured by another layer in the scene. Check audio routing too: a moving image with no sound may be a source or mixer issue rather than a dropped YouTube event.
If the source is visible in OBS but the program output is not showing it, inspect the scene layout and source order. If it vanishes only after a scene transition, reproduce that transition during an offline or private test. For a walkthrough of the broader workflow, the guide to creating a 24/7 stream from prerecorded devotional videos can help you review how local content fits into a continuous channel.
Verify files, order and playback
Open the playlist properties and check each entry, its order and whether it is still reachable at the path OBS expects. A moved, renamed or unavailable file can prevent playback even though the source remains in the scene. Test each representative item locally before treating the playlist as a dependable overnight loop.
Watch the transition between two files and the transition from the final file back to the first. Look and listen for a blank interval, an unexpected restart, a silent item or a file that does not begin. A playlist can appear fine at the opening and fail only when it reaches one damaged or unsupported item later. Reordering or replacing one file may isolate the trigger, but record the original order first so the change is reversible.
Visibility and playback are related but distinct. If a source is hidden during a scene change, its playback may pause or restart depending on the source behaviour and OBS settings. Test the same scene change that occurs on air, then watch the source after it becomes visible again. Do not infer that a YouTube disconnect occurred merely because the playlist returned to its first item.
If you use this kind of setup for rain or mountain ambience, compare it with the Himalayan ambience streaming guide, which focuses on preparing a prerecorded visual for a long-running channel. The useful lesson for troubleshooting is to test the actual file and transition pattern you plan to run, rather than a short sample that never reaches the problematic point.
Choose the right loop control
OBS has separate controls for a single media file and a multiple-file playlist. A single local video in Media Source has a Loop option. A VLC Video source containing several files has Loop Playlist, which starts the list again after it reaches the end. Use the control that matches the source type; a similarly named checkbox elsewhere may not affect the source that is actually on air.
| What you are playing | OBS source to check | Relevant control | What it addresses |
|---|---|---|---|
| One local video | Media Source | Loop | Repeats that file after playback ends |
| Several local videos | VLC Video | Loop Playlist | Restarts the list after its final item |
| Feed appears healthy locally, but YouTube reports ingestion trouble | Encoder and outbound path | No playlist loop setting | Investigate output, configuration and connection |
| Stream is interrupted with a copyright notice | YouTube Studio or Live Control Room | No playback setting | Review the notice, rights and channel status |
Enable the appropriate loop only if the content is meant to repeat. Then test the end of the file or list, not just the first few seconds. OBS’s documentation describes the source options; it does not establish that a particular user’s live interruption was caused by looping. A loop can prevent a playlist from staying at its final item, but it cannot keep OBS running after a crash, restore an unstable internet path, resolve a bad stream key or remove a YouTube restriction.
If this is a one-file stream, do not add it to a VLC playlist just to reach a loop setting. If it is a list of files, check the list’s own Loop Playlist control rather than relying on a Media Source option. The source type determines the right control. For a software-based continuous channel, the FFmpeg encoder settings guide is relevant to encoder configuration, but it is a different branch from correcting an OBS source loop.
Retest one layer at a time
Run a test long enough to reach the file or playlist transition where the problem appeared. Watch the OBS program output, sound, logs and YouTube stream health together. A short preview that ends before the last playlist item can confirm startup but cannot show whether the list loops as intended.
If the source stops locally, change the source, file or loop setting and test that change before touching stream settings. If OBS output remains healthy but YouTube health reports trouble, test the outbound connection and review encoder configuration. YouTube recommends a reliable connection for the chosen stream quality; test upload stability at the same encoder settings you plan to use. A wired Ethernet comparison can help isolate Wi-Fi instability where practical, but it is a diagnostic, not a guaranteed repair.
If preview, logs and the local recording all point to a healthy encoder while YouTube reports an ingest problem, focus on the outbound path and the current server URL and key. If preview and recording are both bad, focus on the source, encoder, computer load or routing. If the platform shows a copyright or restriction notice, follow that account and rights branch instead of repeating technical changes.
Change one variable at a time and keep a note of the result. Retest the same transition after a playlist change and the same encoder conditions after an output change. If the interruption remains, the comparison gives you useful evidence for YouTube or your internet provider; “it disconnects sometimes” does not identify whether playback, encoding or delivery failed.
For a channel that needs to continue while your computer is switched off, StreamNeo can remove the need to leave a local OBS machine running, while the content, stream key and YouTube-side status still need attention. A cloud-hosted broadcast does not make playlist rights issues disappear or guarantee that YouTube will accept every stream.
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
Does enabling Loop Playlist stop YouTube Live from disconnecting?
It can keep a VLC Video playlist moving after its last item, but it does not repair encoder, network, stream-key or YouTube-side interruptions. First check whether OBS source playback stopped or YouTube stopped receiving the live feed. Use Loop Playlist only when the playlist ending is the symptom.
Why does OBS show a picture when YouTube says the stream is unstable?
OBS preview shows the local composition, not proof that YouTube is receiving it steadily. Check Live Control Room stream health, OBS logs and the outbound connection at the time of the warning. A healthy-looking preview does not rule out an ingest problem.
What should I check if the stream restarts at the first video?
See whether the live event stayed active while the playlist returned to its opening item. In OBS, inspect the active scene, source visibility, file order and the relevant loop control, then test the transition at the end of the list. If YouTube also reports an interruption, investigate that separately.
Can copyright matching interrupt a playlist stream?
Yes. YouTube says live streams are scanned for third-party content, and a match can lead to a placeholder, interruption or termination. Check Studio and Live Control Room notices and review the rights for each item; licensed material may require the rights owner to allowlist your channel.