If an OBS YouTube playlist stream stops when a video ends, first find out whether the playback stopped inside OBS, the encoder stopped sending video, or the YouTube Live event ended. Those are separate failure points, and each has a different control.
For one local file, turn on Loop in that Media Source’s properties. For several local files, check Loop Playlist on the VLC Video Source. If OBS preview keeps playing while YouTube says the broadcast has ended, leave the media repeat settings alone and inspect the encoder output and Live Control Room event instead.
Find the point where playback or broadcast stops
Watch the OBS preview and the YouTube Live Control Room preview at the moment the problem occurs. The first useful question is not simply whether viewers can see video; it is whether the source in OBS continues to play and whether OBS continues to send an encoder feed. The event on YouTube is another state to check.
If the clip ends in OBS and the preview shows a blank source or a stopped image, the failure is probably at the playback source. If OBS continues to show moving video but the YouTube event has ended, repeating the file will not restart that event. Check the encoder’s streaming status and the event’s status in Live Control Room.
Use this quick distinction before changing settings:
| What you observe | Likely place to investigate | First check |
|---|---|---|
| The file reaches its end and stops in OBS preview | Media playback source | Media Source Loop, or VLC Video Source Loop Playlist |
| OBS preview continues, but OBS output has stopped | Encoder feed | OBS stream/output status and any displayed error |
| OBS preview and output continue, but YouTube shows the event has ended | YouTube Live event | Event status and auto-stop settings in Live Control Room |
| Both previews appear active, but viewers report a problem | Feed health or delivery to YouTube | YouTube stream-health messages and the event preview |
These checks describe what to inspect, not a guarantee about the cause. A scene can contain more than one media source, and a playlist may be hidden or made inactive as scenes change. Note the source name and the exact moment the picture changes before editing settings.
For a longer-running setup, it also helps to separate the job of OBS from the job of YouTube. A remote OBS setup for a nonstop YouTube stream covers the wider operating arrangement; this page focuses on the specific point where playback or the broadcast ends.
Loop a single file in its Media Source
When one local video should repeat, select the Media Source in the OBS scene and open its properties. Enable Loop, then apply the change. OBS documents Loop as the control for whether media plays again after it reaches the end. Check the preview after applying it rather than assuming the saved property is attached to the source currently visible in the scene.
A common source of confusion is having more than one media source in a scene. The source list may include an intro clip, a background, or a second copy of the same file. Select the source that actually displays the video that ends. If the wrong source is selected, turning on Loop can appear to do nothing even though the property has changed successfully elsewhere.
Also confirm that the source points to the intended file. If the file was moved or replaced, a source may no longer be playing the media you think it is. The point of this check is not to alter the YouTube event: it is to make sure the selected OBS source has the correct file and its own end-of-file behaviour configured.
OBS’s Media Sources guide documents the source controls, including Loop and the behaviour of media playback. The setting belongs to the media source in OBS; it is not a setting in the YouTube viewer’s player.
If your use case is a sermon or devotional video on an older computer, follow the same source-level check before making wider changes to the machine. The guide to setting up OBS on an old Windows laptop for a church sermon loop in India is relevant to that broader setup, but the file’s repeat behaviour still needs to be checked on the source that plays it.
Check repeat behaviour for a playlist of files
A playlist of several local files is not the same thing as one Media Source file. OBS’s documented playlist option is the VLC Video Source. Add that source, place the intended local files in its playlist, and check Loop Playlist in its properties. If you want a fixed order, make sure Shuffle Playlist is off.
The name matters: a playlist visible in the YouTube player is not the same as a playlist of local files inside an OBS VLC Video Source. YouTube’s player has its own loop control for a video or playlist a viewer is watching. It does not tell OBS to repeat a local playlist that OBS is broadcasting. Set repetition where the files are being played.
The VLC Video Source depends on VLC being installed. OBS documentation also specifies matching architecture: if OBS is 64-bit, install the 64-bit version of VLC. If the VLC source is missing, does not load, or behaves differently from the expected source controls, verify that dependency before trying to substitute another setting.
OBS documentation describes Loop Playlist as on by default, but a default is not proof of the current state in your scene. Open the source’s properties and check the actual setting. Scenes can be copied, sources can be edited, and a playlist can be configured differently from another source in the same project.
| Your media arrangement | OBS source to check | End-of-playback control | Additional check |
|---|---|---|---|
| One local video file | Media Source | Loop | Confirm the selected source points to the intended file |
| Several local files in sequence | VLC Video Source | Loop Playlist | Confirm VLC is installed and the files are in this source’s playlist |
| Several files that must stay in a particular order | VLC Video Source | Loop Playlist | Keep Shuffle Playlist off and review the playlist order |
A playlist that stops between clips may have a different issue from a playlist that reaches its last clip and does not return to the first. Watch the transition in OBS preview. If it fails when moving from one file to the next, confirm the correct source type and that all intended files are in its playlist. If each clip plays but the final clip does not lead back to the first, inspect Loop Playlist specifically.
For a channel that depends on a long sequence, be deliberate about whether the audience should hear or see an abrupt return to the beginning. The control repeats the playlist; it does not edit the clips into a seamless transition. A black interval or a sudden change in audio can be a property of the media or the transition between files, rather than evidence that YouTube ended the event.
Do not substitute Restart playback for Loop
Restart playback when source becomes active and Loop describe different behaviour. Loop concerns what happens at the end of playback. Restart playback when source becomes active concerns playback when the source becomes active in a scene. Enabling restart does not mean that the file will automatically repeat when it reaches its end.
That distinction matters when a source is hidden and shown again, for example when switching scenes. Restart-on-activation can affect where playback begins when the source becomes active; it is not the documented end-of-file repeat control. If the source remains active until the video ends, changing this activation setting does not replace turning on Loop.
Likewise, Show nothing when playback ends does not make the source loop. It changes what OBS displays after the media finishes. If you see the source disappear at the end, check whether that behaviour is selected, then separately check Loop if the file is meant to play again.
When troubleshooting, change one relevant setting at a time. If you turn on Loop and alter activation behaviour together, it becomes harder to tell which control affected the preview. Start with the end-of-file setting documented for your source type, then test scene changes separately if they are part of the problem.
OBS source behaviour is especially worth checking if you alternate between a live camera, graphics and recorded segments. A guide to OBS source restart behaviour can help with activation during scene changes, but do not treat that behaviour as the equivalent of a file loop. For the file ending in place, the relevant control remains Loop or Loop Playlist.
If OBS preview continues, inspect the encoder and event
If OBS preview keeps showing the intended video after YouTube’s broadcast ends, the media source is not the first control to change. Check whether OBS is still streaming and whether its output is sending video. Then open YouTube Live Control Room and inspect the status of the specific event. An event ending and a source reaching the end of a file are distinct outcomes.
YouTube’s auto-start and auto-stop options concern whether an encoder can start or stop streaming in relation to a Live event. They do not repeat an OBS playlist. YouTube Help explains: “When these settings are on, you can start or stop streaming from your encoder.” Review the current YouTube Live stream settings guidance for the event controls. A setting that lets an encoder stop an event is not a way to keep local media playing.
Check the right event in Live Control Room, particularly if you have scheduled more than one broadcast. Confirm its state and review whether auto-stop is enabled. Do not assume that reopening OBS or changing a source property will restore an event that YouTube has already marked ended; follow YouTube’s current controls and the event’s displayed state.
If OBS output itself has stopped, look for a visible OBS status or error before changing the playlist. If OBS output continues but the event preview or status indicates a problem, use YouTube’s encoder guidance and stream-health messages to investigate that layer. YouTube recommends checking the preview and stream health when setting up and monitoring an encoder stream; see its encoder streaming instructions.
A useful comparison is to keep the observations separate: what OBS displays, whether OBS is sending, and what YouTube reports about the event. If OBS preview and output both continue while viewers have trouble, inspect stream-health messages and the YouTube preview rather than repeatedly toggling Loop. YouTube’s live streaming troubleshooting guidance is the appropriate reference for feed-side issues.
Test the source, scene and broadcast after a change
After changing the relevant source property, test in OBS preview first. For one file, observe whether it returns to the start after reaching the end. For a VLC playlist, observe the final item and confirm whether the playlist returns to its first item. Testing the behaviour at the boundary is more useful than watching only the beginning of a clip.
Then test scene visibility if the stream uses scene changes. Switch away and back and note whether the source resumes or restarts. This checks activation behaviour separately from end-of-file looping. If the file loops correctly while the source stays visible but behaves differently after a scene switch, investigate the activation and visibility configuration without changing the conclusion about what Loop does.
Next, confirm the encoder feed and event status using the current YouTube event. YouTube recommends testing with audio and video similar to what you will stream and checking the preview and stream-health indicators. A short controlled test can reveal whether the source repeats, OBS keeps sending, and the Live event remains active; it cannot promise that a later broadcast will never encounter a separate connection or event problem.
For a continuous channel, include the end of the last playlist item in the test plan. A short sample that never reaches an item’s end does not verify repeat behaviour. Keep notes of which source property you changed and what each preview showed. That makes it easier to undo an unrelated change and to distinguish a playback fix from an event or encoder fix.
You do not need to buy hardware to change these documented software settings. Choose the source control that matches the media arrangement, then verify the event separately. If your channel’s wider challenge is how to keep a repeating prerecorded programme understandable to viewers, the discussion of ads on a prerecorded YouTube stream that loops covers a separate viewer-facing question; it does not change the OBS repeat setting.
If managing the computer and encoder through the night is the part you need to remove, StreamNeo takes an uploaded video and runs it as a YouTube live stream without keeping your own computer on. It does not change the distinction between a source loop and a YouTube Live event: confirm that your file and channel are ready before choosing how to operate them.
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
Will OBS Media Source Loop keep my YouTube Live event open?
No. Loop controls whether the media source plays again after the file ends; the YouTube Live event has its own status and controls. Check the encoder output and Live Control Room if the event ends while OBS playback continues.
Should I use Restart playback when source becomes active instead of Loop?
No, not for repeating a file at its end. Restart playback when source becomes active relates to the source becoming active in a scene, while Loop handles end-of-playback repetition.
Does YouTube’s playlist loop button repeat my OBS files?
No. The YouTube player’s loop control applies to playback in the viewer’s YouTube player. For local files being played by OBS, configure the relevant OBS Media Source or VLC Video Source.
What should I check if OBS preview keeps running but viewers see an ended stream?
Check whether OBS is still sending its encoder feed, then check the specific event’s status and settings in YouTube Live Control Room. Use YouTube’s stream-health information to investigate feed problems; changing the media loop is not a substitute for checking the event.