YouTube’s repeat controls affect what an individual viewer watches; they do not change the sermon video your live encoder sends. To rotate recordings in a church’s 24/7 live stream, set the playback behaviour in OBS: loop one file with a Media Source, or play several files from a VLC Video playlist.
Before configuring either source, check that your channel can livestream and make sure the recordings, connection and playback order are ready. Then connect OBS to YouTube, preview the incoming feed and test the playlist boundary rather than assuming a loop will work cleanly in every setup.
Why viewer repeat buttons do not rotate a live feed
A live stream is a continuing broadcast feed, not a YouTube playlist that the channel is handing to each viewer one video at a time. OBS or another encoder sends its current audio and video to YouTube. A viewer’s repeat control governs that viewer’s playback experience; it cannot tell the encoder to select the next sermon or alter the feed being sent to everyone else.
That distinction matters when a church watches its own live page to check whether the sermon is repeating. A repeat button visible in YouTube’s player is not the control to use for scheduling the next recording. If OBS is sending the same file continuously, changing a viewer-side setting will not change that source. The adjustment belongs in OBS, where the video files are played before their output reaches YouTube.
This is different from arranging ordinary uploads in a YouTube playlist that plays in order. An upload playlist contains separate videos for on-demand viewing; a live encoder turns selected media into one outgoing broadcast. For the live feed, decide whether you need a single sermon to repeat or several sermons to cycle, then choose the corresponding OBS source.
There is a practical trade-off. Repeating one file is straightforward, but it will keep returning to the same sermon until you change the source. A playlist can rotate several recordings in a chosen order, but introduces more files and transitions to check. Neither approach makes the broadcast independent of the computer, files, power or internet connection running OBS.
Check channel livestream eligibility
Confirm livestream access before spending time building a playlist. YouTube says a channel must be verified and must not have had livestreaming restrictions within the preceding 90 days. Its encoder guidance also notes that first-time enablement can take up to 24 hours, so do not leave activation until the intended launch window. Check YouTube’s current live streaming eligibility guidance and encoder setup instructions for the channel’s status and current steps.
Verification and eligibility are checks, not a promise that a particular planned stream will start without a problem. If livestream access is not available, resolve that with YouTube before preparing the public broadcast. Avoid treating a successful local OBS preview as proof that YouTube has accepted the stream: local playback checks the scene, while YouTube’s Live Control Room checks the incoming encoder feed.
Next, gather the sermon files on the computer that will run OBS. Use recordings the church is entitled to broadcast and confirm that the files open and have sound. Give files useful names and keep them in a stable location; moving or renaming a file after loading it can leave a source pointing to a missing path. For a playlist, settle the intended order in advance and distinguish any opening, closing or special-service recording from the regular rotation.
If a saved YouTube replay matters, plan the broadcast session with the archive rule in mind. YouTube says encoder streams under 12 hours are automatically archived; it does not promise archiving for streams longer than that. See the current YouTube live stream archive guidance. A church that needs a replay should plan sessions to end before the threshold and restart as needed, rather than assuming an indefinitely running broadcast will leave a complete recording.
Loop one sermon with an OBS Media Source
For a single sermon recording, add a Media Source to the OBS scene that will be broadcast. Choose the local video file and enable the source’s Loop option. OBS documents Media Sources and their playback controls in its Media Sources reference. The intended result is that OBS reaches the end of that file and starts it again as part of the outgoing live picture.
Check the source in the scene before streaming. Confirm that the picture is visible in the intended frame, that the audio meter responds when the sermon speaks, and that the audio is not muted in the source or scene. If the scene also contains a church logo, scripture text or a camera view, verify that those elements sit where intended and do not cover important content. A loop setting cannot correct a bad crop, silent file or source hidden behind another scene element.
A Media Source is the simpler choice when the church wants one recording to repeat and has no need to rotate other sermons. It also makes the source easy to understand later: one file, one loop setting. Its limitation is exactly that simplicity. Unless you replace the file or build another playback arrangement, the audience will hear and see the same sermon every cycle.
If you plan to alternate a live camera scene with the recording, decide how the switch should work and test it in OBS. The article on scheduling different OBS playlists during a 24/7 stream covers a broader scheduling problem; for a simple sermon loop, keep the scene arrangement modest and make sure the source actually used by the live scene is the one you tested.
Rotate sermons with a VLC Video playlist
If the aim is to rotate multiple sermon recordings, use an OBS VLC Video source. VLC must be installed for this source to work. Load the sermon files into the source’s playlist in the desired sequence and enable Loop Playlist. If order matters, leave shuffle off. OBS’s documentation describes the setting as restarting the source when it runs out of media files, but it does not promise that every file boundary will be seamless.
Check compatibility as well as the playlist. OBS notes that 64-bit OBS requires 64-bit VLC. If the source is unavailable or does not play, confirm that the VLC installation matches the OBS version before rebuilding the scene. Keep the media files accessible in their original locations, and test each one in VLC or OBS before putting the playlist on air.
A fixed order is useful when the church wants a particular sequence, for example a morning service, a teaching sermon and then an evening message. Write down that sequence and check it against the playlist visible in OBS. If the church wants a less predictable rotation, shuffle may be relevant, but it makes it harder to know what viewers will hear next and to verify a specific order. Do not enable it by accident.
A playlist involves more checks than a single Media Source: every file needs to load, its audio level should be usable alongside the others, and the playlist must reach its last item and return as intended. For background on other loop arrangements, see this guide to setting up a 24/7 YouTube radio channel. Its subject is different, but the need to configure playback at the encoder layer is the same.
Connect OBS to YouTube with the stream URL and key
When the scene is ready, open YouTube Studio’s Live Control Room and create or schedule an encoder stream. Copy the stream URL and stream key shown for that stream into OBS’s streaming settings. YouTube’s encoder streaming instructions describe this connection. The URL tells OBS where to send the feed; the key identifies the stream destination. Treat the key like a credential: do not publish it in a screenshot or share it with people who do not need to configure the encoder.
After entering the details, start streaming from OBS and wait for the Live Control Room to show the incoming feed. A source playing correctly in OBS is not yet the same as a stream visible to YouTube. Use YouTube’s preview to check what the platform is receiving before making the broadcast public or relying on it for a service.
Keep the operating arrangement in view. With OBS running locally, the computer must remain on and able to access the files; the network connection and power also need to remain available. YouTube recommends testing, previewing and monitoring audio and video, and notes that network disruption can break a stream. Its live encoder settings and troubleshooting guidance is a useful reference for connection and feed checks. A looping source does not remove those operating requirements.
If keeping a computer running is the part of this workflow you need to remove, StreamNeo turns an uploaded file into a YouTube live stream after you provide the stream key, without leaving your computer on for playback. That addresses the local-computer burden, not channel eligibility, sermon permissions or the need to check the live result on YouTube.
Preview the scene and verify stream health
Use two views for the preflight: OBS’s own preview and YouTube’s Live Control Room preview. In OBS, check that the intended source is visible, the picture fits, and the audio meter responds. In YouTube, check that the incoming feed appears and listen to the actual stream if possible. A meter moving in OBS does not prove that viewers can hear the feed, and an image in the scene does not prove that YouTube is receiving it.
Check the network arrangement at the place and time the stream will run. YouTube recommends leaving upload bandwidth headroom and testing the stream; do not assume that a connection which works for browsing will behave the same under a continuing upload. If the church’s connection is shared, account for other use during the service. Watch for warnings or interruptions in the Live Control Room and take note of what the preview shows before starting the public broadcast.
For ongoing operation, decide who can check the computer, OBS and YouTube feed, especially overnight. A 24/7 stream depends on more than the repeat setting: OBS must remain open, the source files must remain available, and the computer, power and internet must continue working. If the connection drops, the feed may be interrupted. Do not describe a loop configuration as uninterrupted playback; monitoring and a recovery plan are still needed.
If you are investigating interruptions rather than repetition, use a separate checklist such as this guide to repeated buffering on an always-on stream. Buffering and a source restarting are different problems. Identify whether the issue is in the playback source, OBS output or network before changing settings, so a change intended to fix one does not obscure another.
Test the playlist transition before going live
A playlist that starts correctly has not yet proved that its transitions work for your actual files. Play through each sermon and observe what happens when one ends and the next begins. Pay particular attention to the last-to-first transition when Loop Playlist is enabled. Check both the picture and the sound: note whether there is a pause, an abrupt change in level or an unexpected blank frame, and decide whether that is acceptable for the church’s use.
This is a preflight test, not a claim that OBS always inserts a gap or that one setting will fix every boundary. OBS documents looping behaviour, not guaranteed seamless transitions. Different files may have different formats, audio levels or endings, so test the playlist with the recordings and scene you intend to broadcast. If a transition is unsuitable, investigate the relevant file, playlist order or source configuration and repeat the check before going live.
Run a short private or otherwise non-public test where that suits the channel’s setup. Verify that the YouTube preview follows the playlist, not only the OBS canvas, and keep the stream key private throughout. If the church needs an audience-facing continuous service, complete the checks before announcing the stream. A successful opening minute is not evidence that every later change of file, or the overnight connection, will behave the same way.
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 YouTube’s repeat button stop my live sermon from repeating?
No. A viewer-side repeat control affects that person’s YouTube playback, not the feed OBS sends to YouTube. Configure the playback source in OBS to loop one file or play a playlist.
Which OBS source should I use for several sermons?
Use a VLC Video source, load the recordings in the intended order and enable Loop Playlist. VLC must be installed, and OBS notes that 64-bit OBS requires 64-bit VLC. Test the full sequence, including its return from the last file to the first.
Does Loop Playlist guarantee a seamless transition?
No. OBS documents the loop behaviour, but it does not promise gapless transitions. Check the actual recordings in your scene and decide whether their boundaries are suitable before relying on the playlist.
Will a 24/7 stream always be archived by YouTube?
YouTube says encoder streams under 12 hours are automatically archived, but does not promise archiving for streams longer than that. If a saved replay matters, plan sessions to finish before that threshold and check YouTube’s current archive guidance.