When a YouTube Live broadcast made in OBS ends as its playlist finishes, set the repeat control on the OBS source that supplies the video. Use Loop for one file in a Media Source, or Loop Playlist for a list in a VLC Video source.
If the event still ends, check three separate layers: whether the source is playing, whether OBS is still sending, and whether YouTube has ended the event. YouTube’s viewer-side playlist loop repeats playback for someone watching; it does not restart an OBS source or encoder.
Find which layer stopped
First establish what you mean by “the playlist”. If you are watching a YouTube playlist on a watch page, its repeat control affects your viewing session. YouTube Help explains how to loop a playlist on a computer in its guide to looping videos or playlists. That setting is not part of a live broadcast produced by OBS.
If OBS is reading local files and sending them as a live programme, inspect the source in OBS. A source that has reached the end of its file or list can stop producing new video while OBS itself remains open. If OBS stops transmitting, YouTube may lose the encoder feed. Separately, the YouTube event can end. Those are related possibilities, not interchangeable descriptions of one failure.
Look at OBS before changing settings. Is the media source visibly playing? Does OBS still show that it is connected and streaming? Then check the YouTube Live Control Room: is the broadcast still active, or has the event ended? The first place where the state differs from what you expect points you towards the relevant control.
This distinction matters for a channel built around repeated classes, bhajans or shop footage. For recorded lessons, the source-level approach is also central to looping recorded classes on YouTube Live. But a looping file alone cannot keep every other part of the broadcast chain running. Treat source, encoder output and event as separate checks.
Enable Loop on an OBS Media Source
For one video file, open the Media Source properties in OBS and enable Loop. OBS describes this control as replaying the file when playback completes. The setting belongs to the source that is reading the file; it is not a YouTube watch-page setting. OBS’s Media Sources documentation covers the available media source controls.
A straightforward setup is a single, prepared video in a Media Source. Open the source’s properties, confirm that the intended file is selected, tick Loop, and apply the change. Watch the preview long enough to see what happens at the end. If it returns to the beginning and plays again, the source has repeated. Do not infer from that preview alone that YouTube’s event will remain live indefinitely; you still need the encoder and event checks described below.
If you use a scene transition or switch between scenes, confirm that the looping Media Source remains active in the scene that is actually being sent. A source can be configured correctly but not be the source currently visible on the programme output. Also make sure the file remains available at the location OBS expects. A moved, renamed or disconnected file is a different problem from a missing Loop tick.
Keep the source simple while diagnosing. Temporarily avoid changing multiple media properties at once; otherwise you may not know which change addressed the behaviour. If the file ends and the preview goes blank, inspect the source’s Loop setting first. If it continues playing but the public live feed ends, move on to OBS output and YouTube event state rather than repeatedly toggling the source.
Enable Loop Playlist on a VLC Video source
For multiple local files, use OBS’s VLC Video source and enable Loop Playlist. This setting restarts the source after it runs out of media files. If the order matters—for example, an announcement followed by a programme and then a closing slate—leave Shuffle Playlist off. Confirm the file list itself is complete and in the intended order.
OBS requires VLC for this source. Its documentation specifies installing the matching 64-bit VLC when using 64-bit OBS. If the VLC Video source is missing or fails to load, check that dependency before rebuilding the playlist. The OBS Media Sources page is the primary reference for the source and its VLC requirement.
The playlist loop only has files in the list to repeat. Check each entry for a valid path and make sure every file can play. A file that opens in a desktop player is not necessarily proof that OBS’s VLC source is reading the same path or format. Test the playlist within OBS and watch the transition from its final item back to the first.
A useful comparison is what each control actually repeats:
| What you are doing | Repeat control | What it repeats |
|---|---|---|
| Sending one local file from OBS | Media Source Loop | The file in that source |
| Sending several local files from OBS | VLC Video Loop Playlist | The source playlist; leave shuffle off to preserve order |
| Watching a YouTube playlist | YouTube viewer-side Loop | Playback for the viewer |
| Embedding a YouTube playlist | IFrame Player API setLoop(true) |
Playback in that embedded player |
Google’s YouTube IFrame Player API reference says the default behaviour is that playlists do not loop. That describes the embedded player API, not an OBS source. Setting setLoop(true) for an embedded player, or using YouTube’s viewer loop, will not make OBS start sending again after its local media ends.
Confirm the source keeps playing
Once the correct repeat option is enabled, test the source at the boundary where it used to stop. A short preview that begins successfully does not test the loop. Let the current file or playlist reach its end while you can observe OBS, then check whether playback returns to the beginning. For a playlist, verify the expected first item follows the final one; for a single file, verify the same video starts again.
Watch for a gap, black frame or missing audio at the transition. The goal is not just to see that the source restarts, but to confirm that the actual programme source remains usable. If video repeats but audio does not, inspect the file and source configuration separately. Avoid assuming that a visible moving picture proves the whole media source is healthy.
Keep the operating dependency in mind. A local source depends on OBS being open and able to read its file; a VLC playlist also depends on VLC being installed and the listed files remaining available. If you run a local machine overnight, test the arrangement under the same conditions you intend to use, including the relevant scene and playback order. Advice about keeping a showroom feed running overnight is more useful when the source and operating setup are considered together.
If the repeat boundary fails, go back to the source properties rather than changing YouTube event options. Confirm you edited the source used in the active scene, that the correct file or playlist is selected, and that Loop or Loop Playlist is enabled. A second duplicate source can cause confusion if one is looping in preview while another is on the broadcast output.
Confirm OBS continues sending
A source can keep playing in the OBS preview while OBS is no longer sending a live feed. Check OBS’s streaming status after the media repeats. If the connection has dropped or streaming has stopped, the source loop cannot by itself restore the output. You need to understand whether OBS was stopped manually, disconnected, or otherwise ceased transmitting.
Check the OBS controls and status, then inspect the YouTube Live Control Room for the incoming stream. Confirm that the intended scene remains on the programme output and that the broadcast is receiving the encoder feed. If you changed scenes, keys or connection settings, verify that the correct output is active. For a refresher on the connection credential itself, see what a YouTube stream key does.
Do not treat a reconnect as proof that the underlying cause is fixed. If output stops at the same playlist boundary, return to the source test. If the source clearly keeps moving but OBS stops sending, focus on OBS’s output state and connection instead. Keeping those observations separate makes the next test informative rather than a sequence of unrelated setting changes.
Review YouTube auto-stop settings
Only after confirming the source and OBS output should you review the YouTube event’s auto-stop behaviour. A source ending, an encoder ceasing to send, and YouTube ending the event can happen in sequence, but one does not prove the others. If the broadcast event has ended, inspect its current settings in YouTube Studio and check the official guidance available there; do not assume that a source loop setting controls an event-level option.
Auto-stop can be part of a plausible chain: media ends, OBS output stops or disconnects, and the event later ends. But this is a diagnostic possibility, not a universal explanation. There is no reason to assume a particular delay from the fact that a broadcast ended, and this guide does not assign one. Check what happened in your own OBS status and Live Control Room rather than relying on a timing rule from an unrelated setup.
A viewer-side loop is not a recovery mechanism for any of these conditions. YouTube’s viewer control can repeat a playlist for someone watching, and an embedded player can be configured through the API, but neither control restarts the local media source or the OBS encoder. Keep the distinction clear when interpreting reports that “YouTube loop stopped”.
Test the playlist through a full repeat
After making the change, run a deliberate end-to-end test. Observe the source through its ending and return to the beginning. Then confirm OBS is still streaming and that the YouTube event remains active and receiving the feed. This checks the relevant boundaries without confusing a successful local repeat with a successful ongoing broadcast.
For a multi-file list, note the intended order and observe the final-to-first transition. For a single file, observe the point where playback should restart. If the programme includes a logo, callout or scene overlay, check that the overlay is still present after the loop; editing the media source may not affect a separate overlay source. A channel that uses a persistent visual identity can follow the same principle discussed in adding a logo to a continuous sermon stream: inspect each layer that contributes to the final picture.
Write down the result in plain terms: source repeated or not, OBS sending or not, YouTube event active or ended. If a later overnight run fails, those observations give you a starting point. They also help you decide whether the problem is a file/source setting, the encoder output, or the event configuration rather than making all three changes at once.
If you do not want a local computer and encoder to remain active for a continuous prerecorded broadcast, a hosted approach may remove that particular operating burden. StreamNeo is designed to keep an uploaded file going as a YouTube live stream without leaving your computer running; it does not change YouTube’s event settings or remove the need to check your channel and content. It is YouTube-only, so it is not the fit if you need to send the same feed to another platform.
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 YouTube’s playlist Loop setting restart my OBS live stream?
No. It repeats playlist playback for a viewer, not the local source feeding OBS. For a broadcast made in OBS, enable the repeat control in the Media Source or VLC Video source instead.
Which OBS option should I use for one file?
Use a Media Source and enable Loop in its properties. Test through the end of the file in OBS, then separately confirm that OBS is still sending and the YouTube event remains active.
Which option repeats several files in order?
Use a VLC Video source and enable Loop Playlist. Leave Shuffle Playlist off if the files must play in a particular order, and verify the VLC dependency and file paths.
Why did the YouTube event end even though the source was set to loop?
Looping only addresses source playback. Check whether the source actually repeated, whether OBS continued sending, and whether the YouTube event ended or its settings stopped it; each is a distinct layer to investigate.