If you want original bedtime stories to play repeatedly on YouTube Live, set the loop in the OBS media source that supplies the broadcast. Use Media Source for one compiled video, or VLC Video for a playlist of separate files; neither requires you to restart OBS each time a story finishes.
That is different from a viewer repeating a video in YouTube’s player. Player controls affect that viewer’s playback, not the live programme being sent by OBS. For the broadcast itself, the source must be configured to repeat.
Choose between one compiled file and separate stories
Start with how you want to organise the programme. If your stories are already edited into one long video, a Media Source is the direct route. If each story is a separate file and you want them to play in a chosen sequence, use VLC Video and give that source a playlist.
| Your files | OBS source | Loop control | Best fit |
|---|---|---|---|
| One compiled story video | Media Source | Loop | The stories and any pauses or transitions are already in a single file. |
| Several separate story videos | VLC Video | Loop Playlist | You want OBS to play a sequence of files; install VLC first. |
A compiled file keeps the sequence in your editing project. You can decide where one story ends and the next begins before the stream starts. The trade-off is that changing the order usually means exporting or replacing that compiled file.
Separate files make it easier to replace one story or rearrange the order without rebuilding the whole programme. They do, however, introduce a VLC installation dependency and a playlist to check. The OBS Project’s media sources guide describes Media Source and VLC Video, including their looping controls.
Do not choose based on an expectation of seamless transitions or a particular gap between files. Those outcomes can depend on the media and your setup, and the source documentation does not promise them. If a precisely timed transition matters, compile and review the programme before streaming.
For a longer comparison of ways a channel can rotate prerecorded material, see whether a YouTube 24/7 stream can play different videos automatically. This guide stays focused on configuring the loop in OBS.
Loop one compiled story file with Media Source
In OBS, open the scene that should carry the bedtime programme. Add a Media Source and select the compiled video file. In that source’s properties, enable Loop. OBS describes this option as making a local file play again after it reaches the end.
Give the source a useful name, such as “Bedtime programme”, so you can identify it later. Check that the file path points to the correct export and that the source is visible in the scene. A loop setting on a source that is hidden, covered by another source, or placed in a scene that is not active will not put that video into the outgoing picture.
The loop belongs to the media source; the broadcast encoder does not need to stop and start for the file to begin again. Keep OBS running with the intended scene active, and the source can repeat while OBS continues sending the live feed. This is a configuration capability, not a promise that every file or computer will play without interruption. Preview and monitor your own setup before relying on it overnight.
If you update the compiled video, verify that OBS is using the replacement file rather than an older export with the same name in another folder. Keep a known-good copy until you have checked the new version in preview. That small check is especially useful when the programme is meant to run unattended, because the source may still look correctly configured while pointing to the wrong media.
Build a playlist with VLC Video
For separate story files, first install VLC on the computer where OBS is running. OBS’s VLC Video source depends on VLC being installed; if VLC is absent, that source type may not be available. This is a real dependency, not an optional playback suggestion.
In the intended scene, add a VLC Video source. Use its playlist controls to add the story files in the order you want. Select files from a stable folder, rather than a temporary download location or removable drive that might not be connected later. If you move or rename a file after making the playlist, return to the source and confirm the playlist still points to the right location.
Keep the playlist limited to the files meant for this programme. A stray test clip or an unfinished narration can otherwise become part of the live sequence. Naming files with a clear order can make the playlist easier to inspect, but the order shown in the VLC Video source is what you should verify in OBS.
A playlist is useful when you expect to make small changes over time: replace one story, add a new one, or remove a file without exporting a single long video. The cost is more to check before going live: VLC must be installed, every file must be reachable, and the playlist must contain the intended items. For an overview of preparing media folders for automated playback, see how to organise a large video folder for an automated YouTube live stream.
Set story order and looping behaviour
In the VLC Video source properties, arrange the playlist in the sequence you want viewers to hear. Enable Loop Playlist to repeat the sequence. Leave shuffle off if order matters. For bedtime stories, a fixed order can be part of the experience: for example, a calm welcome story followed by quieter stories later in the sequence.
Looping the playlist means the sequence is intended to play again after it reaches its end. It does not create a new live event or require you to restart OBS at the end of each pass. It also does not let you assume that every transition will be invisible or silent. Inspect the points where one file ends and another begins in preview, and listen for abrupt changes in level or content.
If you prefer a different story order on different nights, edit the playlist before the broadcast and check the result. Do not depend on shuffle to produce a particular sequence; its purpose is variation, not a repeatable editorial order. If the order must stay consistent, use a fixed playlist and confirm the visible order before starting.
For a single compiled file, do not look for the playlist loop control: enable Loop in Media Source instead. These two source types have similar purposes but distinct settings. The OBS media sources documentation is the appropriate reference if your version presents the properties differently from a guide or screenshot you are following.
Check scene visibility, picture and sound
Before connecting to YouTube, check the OBS scene itself. Confirm the story source is visible, not hidden behind an opaque image or another video source, and that the intended scene is active. If you use an overlay, make sure it does not cover captions or other information you want visible. A source configured to loop can still be absent from the final picture if scene visibility is wrong.
Play enough of the file or playlist to confirm that the image appears and the narration is audible. Check the opening of each separate story, not only the first file. Listen for missing audio, a channel muted in OBS, or a large level change between stories. The goal is to catch problems in the outgoing programme, not simply to see that the source has a loop box ticked.
Check the stream connection in YouTube Live Control Room before making the broadcast public. YouTube’s live streaming eligibility guidance says the channel must be verified and have no live-streaming restrictions in the preceding 90 days. Eligibility and current account status are separate from the OBS loop configuration, so confirm your channel can stream before planning a scheduled overnight run.
Treat your stream key as a password. Enter the connection information in OBS as directed by YouTube, but do not share a screenshot or setup document that exposes the key. YouTube’s stream settings help explains the settings in Live Control Room. Use the preview there to verify that the encoder feed is reaching YouTube before you begin a public broadcast.
YouTube advises checking the preview and monitoring audio and video. A private or unlisted rehearsal is a sensible operational check: it lets you inspect the actual stream path without presenting a test to your usual audience. It does not guarantee a later broadcast will be trouble-free, but it can reveal a wrong scene, silent audio, or an incorrect playlist before the scheduled programme.
Test the loop before the live programme
A useful test begins with the end of the material, because that is where looping matters. For a compiled file, let the Media Source reach its end and verify that playback begins again. For a VLC playlist, observe the last item and confirm the playlist proceeds to its beginning with the loop option enabled. Do not infer correct behaviour merely from seeing a loop control selected.
Keep OBS open throughout the test. The question is whether the media source repeats while the encoder and scene remain active, not whether you can restart the application and make the file play again. If the source does not behave as expected, check the selected file, the source type, and its loop control. With VLC Video, also confirm VLC is installed and that each playlist path remains valid.
Then inspect the YouTube preview feed. You want to verify that the picture and sound arriving in Live Control Room match what OBS shows. Watch and listen across at least one story change if you are using separate files. YouTube recommends monitoring the video and audio during a live stream; a rehearsal helps you establish what to watch, but monitoring remains useful once the real programme is running.
Do not treat a successful short test as proof of uninterrupted overnight playback. This workflow explains how to configure repetition, not how to guarantee a computer, file, connection, or stream will remain healthy indefinitely. If you are troubleshooting encoder load as well as playback, the practical checks in OBS encoder overload settings for a 24/7 YouTube loop address a separate part of the setup.
For a long-running broadcast, decide what you need to preserve if the live stream ends. YouTube says it may fail to capture an archive when a stream runs longer than 12 hours, and its guidance also notes that DVR rewind may be limited or unavailable on very long streams, including those longer than 12 hours. If the recording matters, make a local archive plan and check YouTube’s current live stream archive guidance before relying on a platform archive. These archive and DVR caveats do not change how the OBS source loops; they affect what you can review afterwards.
Stream repetition is not viewer repeat
There are two different places where the word “loop” appears. OBS can repeat a media file or playlist in the feed it sends to YouTube. A viewer can also use playback controls in YouTube, where available, to repeat or otherwise control what that viewer watches. Only the first mechanism changes the programme being broadcast.
A live stream is received as a live feed. A viewer’s player controls do not reach back into OBS to restart your story source, change the playlist, or make the programme repeat for everyone. If one viewer wants to replay something in their own player, that is their local viewing choice; it does not alter the feed for another viewer.
This distinction matters when someone says they can “just turn on repeat” in YouTube. That may describe repeating playback on a viewer’s device, but it is not a substitute for setting Loop or Loop Playlist in OBS. Configure the source that supplies the broadcast, then preview that feed in Live Control Room.
There is also a practical rights check before you publish. Original stories do not automatically clear background music, illustrations, photographs, or other third-party material used alongside them. YouTube’s terms put responsibility for the necessary rights on the person providing the content, and YouTube says live streams are scanned for matches to third-party content. Its copyright guidance for live streams explains the issue; check the current official guidance for your programme, and do not assume that a track being licensed for one use means it will be allowed in a live stream.
If maintaining a computer and checking a local loop through the night is the specific pain point, StreamNeo can take an uploaded video and stream it continuously to YouTube without your computer remaining on. It is YouTube-only, and the source material and rights checks remain yours; its role is to remove the need to keep OBS running locally for that repeated programme.
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
Can I loop a playlist without restarting OBS?
Yes. In OBS, use a VLC Video source with the playlist configured and Loop Playlist enabled. Keep OBS running with the intended scene active, and test the end-to-start behaviour in preview before relying on it for a live programme.
Does OBS need VLC installed for a playlist?
Yes. VLC must be installed for OBS’s VLC Video source to be available. If you want to avoid that dependency, consider compiling your stories into one video and using Media Source with Loop enabled.
Will YouTube’s repeat control loop my live broadcast?
No. Viewer playback controls affect that viewer’s experience; they do not control the OBS encoder or change the feed sent to other viewers. Set repetition in the OBS source that supplies the stream.
Will YouTube always save a long stream archive?
Do not assume so. YouTube says it may fail to capture an archive for streams longer than 12 hours, and DVR rewind may also be limited or unavailable on very long streams. If preserving the recording matters, plan a local archive and consult YouTube’s current help guidance.