To repeat a church sermon on YouTube Live, make the repeat happen in the encoder: use OBS Studio with a looping Media Source for one file, or a VLC Video playlist for several. YouTube’s viewer-side Loop control repeats ordinary playback for an individual viewer; it does not turn a playlist into a live broadcast.
You can configure the encoder to replay files, but documented loop controls do not promise frame-perfect, gap-free transitions. Test the complete sequence and listen and watch at each boundary before you rely on it for a public or overnight stream.
What a YouTube Live loop requires
A live loop has three parts: the sermon video files, an encoder that plays them in the intended order, and a YouTube Live stream that receives the encoder’s outgoing picture and sound. In this setup OBS is the encoder. It plays a file or playlist in a scene and sends that scene to YouTube for viewers to watch live.
The repeat belongs in that outgoing feed. If you open a YouTube video and select Loop, you change playback for the person watching that page. You have not created a continuous live channel, and viewers who join a separate live broadcast will not inherit that playback setting.
Prepare the sermon material before opening the stream. Check that you have the right final exports, that their sound is present, and that any opening or closing cards are deliberate. If you intend to rotate several sermons, decide their order on paper first. A playlist that silently shuffles can be a problem when the sequence reflects a service, a teaching series, or a pastoral decision.
There is no special church-specific encoder requirement in the basic workflow. OBS documents Media Sources for adding audio and video files to a scene, and common supported formats include MP4, MOV, MKV, AVI and WebM. Check the OBS Media Sources guide for current behaviour and format details rather than assuming every export will behave identically.
If you are weighing a local encoder workflow against a continuously running playlist setup, the practical distinctions are file order, who must keep the computer on, and how you handle interruptions. The guide to streaming a YouTube playlist continuously with OBS covers the broader playlist workflow; this article focuses on the specific controls that repeat a sermon file or a VLC sequence.
Viewer Loop and encoder loop are different
YouTube’s Loop option is a playback control. A viewer can use it to repeat a video or playlist while watching on YouTube, but that action does not send a live feed to a channel. You need an encoder to create the live output, and the encoder must keep playing the source material if the broadcast is meant to continue after a sermon ends.
This difference matters when planning a channel page. A church may have a sermon uploaded as a standard video, with Loop enabled by a viewer, and also run a scheduled live stream that repeats a programme. Those are separate viewing experiences. The first depends on the viewer’s playback choice; the second depends on OBS, the source files, the network connection and YouTube Live accepting the feed.
YouTube’s Help page on live streaming with an encoder explains the encoder connection process. Its separate viewer help for watching videos and playlists covers playback features. Consult the current pages if the interface changes, but keep the conceptual distinction: the viewer’s Loop setting cannot repair a source that stops in the encoder.
Loop one sermon video in OBS
For a single sermon that should repeat, create or open an OBS scene and add a Media Source. Choose the local video file, then enable Loop in that source’s properties. OBS defines this setting as replaying the file after playback completes. The source must remain part of the scene’s visible programme output for the repeat to reach viewers.
Keep the scene simple while you test. If you add a title card, logo, lower-third or other overlay, check that it does not cover the sermon image or obscure captions. Also consider how the media source behaves when the scene is changed or becomes inactive. OBS exposes options such as restart on activation and close file when inactive; those can affect whether playback resumes at the start, continues as expected, or has to reopen the file when you return to the scene.
A useful test is to start the source, let the sermon reach its final seconds, and watch what happens as it returns to the beginning. Listen for a short silence, clipped last words, or an abrupt change in room tone. The file may itself contain an intentional pause or fade. A visible gap at the end can come from the export, the source’s restart behaviour, or the transition itself, so inspect the material before changing encoder settings.
One file is straightforward when you want the same sermon repeated without variation. It is less suitable if the congregation expects a sequence of different recordings or if repetition would make the programme feel interrupted. For a set of sermons, keep each export as its own file and use a playlist source so that you can verify their order explicitly.
Loop a playlist with VLC Video
For multiple sermons, add OBS’s VLC Video source and put the files into its playlist in the desired order. Enable Loop Playlist to repeat the sequence. OBS notes that VLC needs to be installed for the VLC Video source to appear. If the source is missing, check that prerequisite before rebuilding the scene or assuming the files are unsupported.
Turn shuffle off when the order matters. A church may want the opening reflection, sermon, and closing prayer to run in a particular order, or may have chosen recordings to match a weekly theme. Verify the playlist as displayed in the source settings and test it from the first item through the final item and back to the first. Do not rely on the filename order in a folder unless the playlist itself shows that order.
Visibility settings matter too. Configure the VLC source so it remains available in the scene arrangement you intend to use, and avoid switching to a scene that hides or deactivates it unless you have checked the resulting playback behaviour. If you alternate between a holding slide and the sermon scene, test that exact sequence. A source that works when left alone may restart or reopen differently after a scene change.
| Approach | Suitable when | What to check |
|---|---|---|
| Media Source with Loop | One sermon repeats on its own | End-to-start boundary, source visibility and activation behaviour |
| VLC Video with Loop Playlist | Several files run in a fixed sequence | VLC installation, playlist order, shuffle off and each file boundary |
| YouTube viewer-side Loop | One viewer repeats ordinary playback | It is not an encoder loop and does not create a live broadcast |
The playlist route gives you more control over which recording follows which, but it also creates more boundaries to test. If one sermon has a different aspect ratio, audio level or length of silence at the end, viewers may notice the shift even when playback continues. The playlist sizing and planning guide is useful for thinking about sequence and variety, though the right number of files depends on the programme rather than a universal rule.
Connect OBS to YouTube Live
In YouTube Studio, create or select the live stream and retrieve its stream URL and stream key from Live Control Room. Enter those in OBS’s stream settings, choosing a protocol and settings supported by both the encoder and YouTube. YouTube recommends RTMPS for secure ingest in its encoder guidance; check the current YouTube encoder setup instructions before configuring a new stream, as controls and labels can change.
Treat the stream key as a credential. Do not show it in a screen capture, send it in a public message, or leave a settings window visible in the programme scene. If you think it has been exposed, use YouTube Studio’s current controls to replace it and update the encoder. The key identifies where the feed should go; it is not a password to share with viewers.
For a scheduled stream, start the encoder and wait for the preview to appear in Live Control Room. Review the picture and sound there before selecting Go live when that is part of your workflow. YouTube creates the watch page once the encoder begins sending a feed, but the preview is where you can catch an incorrect scene, missing audio, unexpected crop or wrong sermon before the public broadcast begins.
The connection is separate from the media loop. A file can repeat correctly in OBS while the network or ingest connection fails; conversely, a healthy connection can carry an incorrectly ordered playlist. Keep the checks distinct: confirm the source and scene locally, then confirm YouTube is receiving the intended programme. For an always-on channel where keeping a computer running is itself the burden, the relevant pain is the need to leave that machine operating; StreamNeo takes an uploaded video and stream key to keep a YouTube broadcast running without your computer left on.
Test transitions across the full loop
Do a full-cycle rehearsal before announcing the stream. For one sermon, watch through the ending and the restart. For a playlist, let every file play through to the return to the first item. A short spot-check at the start cannot tell you whether the last file is missing, the sequence is wrong, or a transition causes a pause later in the cycle.
Check picture and sound independently. Look for black frames, a frozen image, unexpected cropping, a title card covering the speaker, clipped openings, or silence between recordings. Listen at a normal viewing volume, especially where one source ends and another starts. If you use captions or embedded text, make sure they remain readable through the change in image size or scene layout.
The goal is to identify what viewers will actually receive, not to assume a setting guarantees a seamless boundary. OBS documents how to loop a source or playlist; its documentation does not promise that every pair of files will switch with no perceptible gap. The encoding, file exports, source behaviour and particular scene can all affect the result. If a transition is distracting, you may need to adjust the edit itself, such as adding a deliberate fade or producing a combined file, rather than expecting a loop checkbox to fix the source material.
Test on the same computer and with the same scene arrangement you intend to use for the broadcast. If you will change slides, add a camera, or display announcements at certain times, rehearse those actions too. A loop that looks fine in an isolated test scene may be interrupted by a scene switch or a hidden source in the actual programme.
A practical record of the rehearsal helps if someone else will operate the stream. Note the file order, the scenes used, whether the audio transitions are acceptable, and any point that needs a manual check. That is more useful than a vague instruction to “make sure it loops”, especially when a volunteer takes over for a later service.
Check stream health while the loop runs
A successful preview is not a reason to stop monitoring. During the broadcast, watch Live Control Room for stream health messages and keep an eye on audio and video. YouTube’s live streaming tips recommend testing the setup, previewing and monitoring the stream. They also recommend upload bandwidth headroom of 20% beyond the total stream bitrate; this is guidance, not a promise that a connection will never be interrupted.
The connection needs to sustain the encoder’s total outgoing bitrate. Other household or church-office traffic can use upload capacity while the stream is running, and a network disruption can affect delivery even if local playback continues. Where possible, test under realistic conditions and avoid starting a large upload or other bandwidth-heavy task on the same connection during the service. For a more detailed connection discussion, see what upload speed means for live streaming.
If YouTube reports a problem, look at its message and the encoder’s own status before changing several settings at once. A frozen or interrupted live feed is not necessarily a loop problem. If the local OBS preview still advances, investigate the outgoing connection and YouTube health indicators; if the local preview has stopped at a file boundary, inspect the source and playlist instead. The dropped-frames troubleshooting guide can help separate encoder and network symptoms.
For a long-running stream, make a plan for a person to check it and know what to do if the source stops or the connection drops. YouTube documents auto-start and auto-stop controls for encoder streams, but verify how your selected stream is configured before relying on them. Likewise, check current Live Control Room behaviour and account settings before planning an archive: YouTube’s guidance describes automatic archiving for streams under 12 hours, but you should confirm the current rule rather than base an important recording plan on an old assumption.
A backup encoder is an operational choice, not a requirement for a simple sermon loop. If you choose to configure one, YouTube recommends testing failover so you know how the player behaves when the primary encoder stops or loses its network. Do not add complexity just because the channel is live; add it when the cost of a prolonged interruption justifies the extra setup and rehearsal.
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 Loop button make a live stream repeat?
No. The viewer-side Loop control repeats ordinary YouTube playback for that viewer; it does not create or control a live broadcast. To repeat sermon material during a live stream, set up the repeat in the encoder’s outgoing feed.
Can OBS guarantee that a sermon repeats without a gap?
OBS provides a Loop setting for a Media Source and a Loop Playlist setting for VLC Video, but those controls are not a guarantee of frame-perfect transitions. Test the complete cycle on the intended setup and inspect the actual picture and sound at each boundary.
Do I need VLC to repeat one sermon?
No. A single sermon can be played from an OBS Media Source with Loop enabled. VLC Video is useful for a multi-file playlist, and OBS says VLC must be installed for that source to appear.
What should I check before going live?
Confirm the correct file or playlist, its order, audio continuity, scene visibility and the YouTube preview. Then monitor stream health and audio/video during the broadcast, since a good local loop does not prevent network or ingest interruptions.