To switch sermon videos during a YouTube Live loop, keep the OBS encoder and YouTube Live event running and change the media sent from inside OBS. You do not need to end the event and start another one for each recording.
That workflow avoids restarting the broadcast, but it does not guarantee a black-screen-free or gapless change. Test the actual files, transitions, picture and sound before the public stream, including the point where the final playlist item returns to the first.
Keep the encoder and Live event running
Think of the broadcast as two connected parts: OBS sends an encoder feed, and YouTube receives that feed as part of a Live event. The sermon video is content within the feed. To change sermons, switch or sequence that content in OBS while leaving the encoder connected; do not stop the encoder just to replace a file.
YouTube’s encoder streaming instructions describe configuring the encoder with the Live Control Room’s server URL and stream key, previewing the incoming stream, and stopping the encoder when you want to end the broadcast. That is different from changing a media source while the feed continues. Stopping and restarting the encoder can interrupt the event and create extra work, whereas changing the media in the running OBS scene keeps the same broadcast workflow in place.
Before service, confirm that OBS is connected to the intended event and that the correct scene is sending content. Keep the stream key private and use the details shown for the event you mean to run. Have someone watch the YouTube preview while you test if possible; an OBS preview alone cannot show you exactly what YouTube is receiving.
A running event does not protect you from every interruption. It cannot correct an internet outage, a stopped encoder, or a video that fails to load. The practical aim is narrower: keep the feed running while you change its source, then verify that the change behaves as intended.
For a church planning a longer unattended schedule, the choice between a computer running OBS and a hosted approach has operational consequences. Our guide to 24/7 aarti and mantra streams discusses the broader planning questions around continuous devotional programming. Here, the focus is the boundary between recordings and how to rehearse it.
Choose a Media Source or VLC playlist
For one sermon video that should repeat, use an OBS Media Source. Add the local file to the scene that is on air and set the source’s Loop control deliberately. OBS documents Loop as off by default, so do not assume that a file will repeat just because it is the only item in the scene. Also inspect the separate Show nothing when playback ends setting: if a clip is not looping as expected, the end-of-file behaviour can leave the scene with nothing from that source.
OBS documents a range of supported local video formats, including MP4, MOV, MKV, AVI and WebM, as well as formats such as TS and FLV. The relevant question is not merely whether the filename has a familiar extension. Open the file in OBS and rehearse it with the same scene, audio routing and overlays that will be used on air.
For several recordings in a planned sequence, use OBS’s VLC Video source and add the files in the order you want them played. VLC must be installed for the source to be available; OBS notes that 64-bit OBS needs 64-bit VLC. This is a dependency to check before rehearsal, not something to discover when the service is due to start.
A VLC playlist gives you ordered playback controls, but it is not a guarantee about what viewers see at the change from one file to the next. Files may have different endings, beginnings, audio levels or picture dimensions. The source may also behave differently when hidden and shown again. Read the OBS Media Sources documentation and verify the options on your own installation rather than relying on remembered defaults.
If you need a person to choose the next sermon manually, organise recordings as prepared scenes or sources and rehearse the switch in the actual scene layout. Manual control can suit a service where a speaker or operator decides when to move on; an automatic playlist is simpler when the order and timing are settled. Neither choice makes the media transition inherently seamless.
A cloud-based workflow may suit a church that needs prerecorded content to keep running with its own computer switched off. StreamNeo addresses that specific burden by letting you upload a video and keep a YouTube broadcast running without leaving a local computer on, rather than asking an operator to nurse a workstation through the night. It is YouTube-only, so first decide whether that fits your channel and operating needs.
Set the intended playlist order
Before you test transitions, make the playback plan explicit. Write down the sequence, for example: opening prayer, sermon recording, closing hymn, then back to the opening prayer. Confirm that the playlist in OBS matches that order. A correct set of files in the wrong order is still the wrong broadcast.
For a predictable sequence, leave Shuffle Playlist off. OBS documents shuffle as off by default, but check the control rather than trusting a default that might have changed. If the whole sequence should repeat, check Loop Playlist separately. OBS documents playlist looping as on by default; that does not mean it is the same control as Loop on a single Media Source.
The distinction matters when troubleshooting. A single Media Source with Loop enabled repeats one file. A VLC playlist with Loop Playlist enabled repeats the sequence. If you expect a multi-sermon playlist to return to the beginning and it stops at the end, check the playlist loop control. If the wrong sermon plays next, check the ordered list and shuffle setting before changing anything else.
Keep the files accessible to the computer running OBS for the full broadcast. A rehearsal from a folder that is later moved, renamed or disconnected does not represent the live setup. Use stable file locations and open every item in the playlist before going on air, especially if the recordings came from different people or devices.
If the channel’s plan depends on a recurring sequence rather than one service, it may help to compare the playlist workflow with other ways of keeping a feed active. The article on streaming a cloud storage video folder to YouTube Live provides a related planning reference; it should not be read as evidence that any particular file transition will be gapless.
Preview each video change
Do not test only the first item or jump directly to a live event. Play the sequence in rehearsal from the same OBS scene and with the same files, visibility settings and transition method planned for service. Watch every boundary: the last moments of one sermon, the start of the next, and the moments immediately after the change.
For an operator-controlled change, rehearse the exact action the operator will take. If it is a scene change, practise the same scene button and transition. If it is changing a source, practise selecting and starting the next media item. A switch that works only when the operator knows a hidden sequence of clicks is fragile during a service. Write the steps down or simplify the scene arrangement.
For an automatic playlist, let it run across every boundary rather than seeking through each file and assuming the next item will behave identically. Seeking may help inspect a particular passage, but it does not replace testing normal playback through the end of a file and into the next one. Include the last-to-first return if the playlist repeats.
Watch the OBS programme output, not only a file player outside OBS. Check for a blank or frozen frame, an unexpected cut, a source that remains hidden, a title overlay that covers the sermon, or a scale change that makes text difficult to read. Note where an issue occurs and repeat the same boundary after adjusting one setting at a time.
OBS documents that Close file when inactive unloads hidden media and that reloading can cause a small period when the source is not showing. VLC Video also has visibility behaviour that can stop playback while it is not visible and restart it when visible, depending on its settings. If your switching method hides a source, inspect those options and rehearse hide/show behaviour. Do not assume playback will continue invisibly or resume at the point you expect.
The point of a rehearsal is to discover how your actual files and settings behave, not to certify that all changes will be seamless. Keep a simple checklist with each file boundary and mark whether picture, sound and overlays behaved acceptably. If one boundary fails, fix or replace that transition before the audience sees it.
Test the last-to-first loop boundary
The loop point is its own transition. In a playlist of several sermons, the final file returning to the first can be easy to overlook because a short test often stops after the first few items. Run the playlist through its end in rehearsal and watch the actual return to the opening item.
Check whether the final recording ends with silence, a long fade, a spoken sign-off or an abrupt cut. Then inspect the first moments of the opening recording. A long quiet ending followed by a loud opening may feel like a pause or jump even if OBS continues sending a picture. A closing title followed by an opening slate may be intentional, but viewers should not be left looking at an accidental blank scene.
If a boundary is awkward, consider changing the order, editing the source recordings, or making a deliberate transition in OBS. Choose a change you can reproduce and rehearse. A fade, cut or other scene transition is not a universal fix: it may behave differently with your media, and the official OBS guidance does not promise a gapless result for any particular transition style.
For a single file set to loop, test its own end and beginning as carefully as a multi-file playlist boundary. Listen for an abrupt audio restart and watch whether the picture pauses, blanks or changes scale. A one-file loop removes playlist-order questions, but it does not establish that playback will be invisible at the repeat point.
When your programme contains long periods between services or different types of devotional content, decide whether a short slate is preferable to an unplanned pause. A slate can make a deliberate interval understandable, but it is still content that must be tested as part of the sequence. Our guide to adding a countdown slate between videos covers that separate use; do not add one merely to conceal a transition you have not checked.
Check picture and audio at transitions
At each boundary, check the picture and audio independently. A video may continue while its audio drops, or sound may continue while the picture is black or frozen. Watch the outgoing file’s final seconds and the incoming file’s first seconds, then listen through the point of change without turning the monitoring volume down.
For picture, look for a blank frame, freeze, unexpected crop, letterboxing, altered aspect ratio or overlay appearing in the wrong place. If sermon slides include small text, check that they remain readable in the scene layout and YouTube preview. Different files can use different dimensions or framing, so a source that fits one recording may not fit the next in the same way.
For sound, listen for a sudden level change, clipping, a missing channel, a pause, or two audio sources playing together. Confirm that the intended source is audible and that desktop audio or a microphone is not unintentionally mixed into the recording. The goal is not to make every recording identical; it is to know what the audience will hear when the source changes.
Check overlays and scene elements at the same time. A lower-third, church logo or lyric panel may remain visible over the next video, or a scene change may remove something that should stay. Decide which items belong to the whole broadcast and which belong only to a particular recording, then practise the transition with that arrangement.
If you change a setting to address a problem, repeat the affected boundary and the loop point. Keep notes of the source and setting that changed. Avoid making several unrelated adjustments at once, because that makes it difficult to identify which change helped and whether another part of the sequence was affected.
Verify the incoming feed in Live Control Room
After the OBS rehearsal, connect the encoder to the intended YouTube Live event and wait for its preview. The preview is the practical check that YouTube is receiving the feed you expect, rather than a check of what OBS appears to show locally. Confirm the scene, picture and audio there before choosing to go live.
If the incoming feed is wrong, pause the launch and check the OBS output, event selection, stream URL and stream key. Avoid ending the event as a first response to a media transition problem; first establish whether OBS is still sending the intended content. Once live, keep the encoder connected while you make the rehearsed media change inside OBS.
The preview is not a promise that the stream will remain uninterrupted after launch. It is a checkpoint for the incoming feed at that moment. Your rehearsal and monitoring still matter, particularly if the computer, network, files or scene arrangement differ from the setup you tested.
If you rely on a saved replay, check YouTube’s current guidance for the event and its archive behaviour. YouTube states that streams under 12 hours are automatically archived, but this is platform behaviour rather than a guarantee about every long-running church loop. Plan the broadcast and any replay expectation around the current official instructions rather than assuming a continuous loop will always produce one complete archive.
For a church that operates its own computer around the clock, the operating burden includes power, internet continuity, keeping files available and noticing when playback has stopped. A hosted workflow shifts some of that burden away from a local machine, but it still requires a tested playlist, correct event setup and monitoring appropriate to the channel. Choose based on who will look after the stream and what level of manual control the service needs.
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
Do I need to stop YouTube Live to change the sermon video?
No. Keep OBS connected to the same YouTube Live event and change the media being sent from the running OBS scene. YouTube’s encoder workflow describes stopping the encoder as the way to end a stream, not as a required step for each content change.
Does Loop Playlist mean there will be no black screen?
No. It means the playlist is set to repeat; it does not establish that the transition between files will be gapless or free of a blank frame. Rehearse every boundary, including the last item returning to the first, and inspect picture and sound.
Should I use Media Source or VLC Video?
Use Media Source for one file that should repeat, and VLC Video for an ordered playlist of several files. Check the relevant loop control and, for VLC, its installation and playlist order. Test the setup with the actual files and OBS scene before service.
Can I trust the OBS preview on its own?
Use it to check what OBS is composing, then also check YouTube’s Live Control Room preview to confirm the incoming feed. Neither preview guarantees uninterrupted operation after you go live. Rehearse with the service setup and monitor the broadcast as needed.