For a free local setup, OBS Studio is the practical choice for looping a church sermon on YouTube Live. Use Media Source when one recording should repeat, or VLC Video when you want several recordings to play in a sequence.
This workflow runs on a computer at the church, not as a hosted or unattended service. YouTube must enable live streaming for your channel, and the computer and its internet connection must remain available for the broadcast.
Why OBS suits a free local setup
OBS Studio is free, open-source streaming and recording software for Windows, macOS and Linux, according to the OBS Project. It lets you add a video file as a source, arrange the picture, set audio levels and send the resulting programme to YouTube. For a sermon that is already recorded, that is enough to build a straightforward loop without buying a separate streaming application.
The choice is less about comparing brands than about how you want the recordings to behave. A single sermon can repeat from one Media Source. A sequence of sermons can rotate through a VLC Video playlist. Both approaches use OBS; the playlist path also requires VLC to be installed on the same computer.
Be clear about what “free” means here. The software costs nothing, but the church still supplies a suitable computer, storage for the video, a reliable upload connection and someone who can check that the broadcast is behaving as expected. OBS does not keep streaming after that local setup loses power, internet access or the ability to run the software.
A local workflow is useful when a volunteer can start the stream and the church wants control over the scene, audio and broadcast settings. If your real need is a channel that continues while the church computer is off, that is a different operating requirement; it is not something OBS’s loop setting provides. The distinction matters especially when planning a long overnight or day-long broadcast.
For a sequence rather than a single recording, the playlist mechanics are different from simply setting a video to repeat. A related explanation of how rotating content is organised is available in this guide to rotating product demos in a YouTube Live stream. The subject is different, but the practical question—whether viewers see one item repeatedly or a deliberate sequence—is the same.
Check YouTube Live eligibility and activation
Before setting up OBS, confirm that the church’s YouTube channel can go live. YouTube’s encoder setup guidance says the channel must be verified and must not have live-streaming restrictions in the preceding 90 days. First-time activation can take up to 24 hours, so do not leave this check until the service is about to begin.
Sign in to the correct church channel and open YouTube Studio’s live controls. If streaming has not been enabled, follow the activation steps there and allow time for access to become available. A channel that can upload videos is not necessarily ready to broadcast live; confirm the live controls are available before building your event around them.
The channel’s eligibility is separate from rights to the material. A sermon recording may include music, photographs, slides or other material created by someone else. YouTube’s livestream terms and conditions place responsibility on the provider to have the rights needed for streamed and archived content, including applicable music rights. Check permission for the sermon recording and every included element; a loop setting does not grant any rights or make a recording eligible to use.
If a service is intended for a congregation rather than the public, decide who should be able to watch and choose the broadcast visibility accordingly. Make that decision in YouTube Studio, then test the same kind of visibility before the real service. An unlisted test can be useful for checking playback with a small group, but it is still a live broadcast and should use content the church has permission to stream.
Loop one sermon with Media Source
For one recording that should repeat, add it to the OBS scene as a Media Source. Create or select a scene, use the Sources panel to add a Media Source, and browse to the sermon video stored on the computer. Give the source a recognisable name such as “Sunday sermon”, particularly if the scene also contains a logo, title card or other elements.
In the source properties, enable Loop. The OBS guide to Media Sources describes this source as a way to play local media and documents the loop option. Once enabled, OBS starts the file again when it reaches the end. It does not turn a finite sermon into new content: viewers will see the same recording from the beginning each time it completes.
Check the picture in the OBS preview. If the video does not fill the canvas, right-click the source and use the transform options to fit it to the scene, then inspect the edges for cropping. A sermon recorded in a different shape from the scene may show blank space or lose part of the image if stretched incorrectly. Preserve the original proportions unless there is a deliberate reason to crop.
Listen through the opening and ending, not just a middle section. Confirm that speech is audible, that the computer is not also capturing an unwanted microphone or desktop sound, and that the file begins and restarts as expected. If there is silence before the speaker begins, viewers will hear that silence on every loop. If an ending includes a long pause or abrupt cut, it will recur at every restart.
A single-file loop is simple to operate but can become repetitive for viewers who join later or remain for a long period. If the church wants a service recording followed by a hymn set, announcements or another sermon, prepare and order those files as a playlist instead of trying to make several independent sources behave like one sequence.
Loop a sequence with VLC Video
For several recordings in a set order, use OBS’s VLC Video source. VLC must be installed on the same computer as OBS; the source depends on that application. Add VLC Video from the Sources panel, then use its playlist controls to add the local files in the order they should play. Check the full filenames and order before going live, since a file chosen in the wrong position can change the flow of the service.
Enable Loop Playlist in the source properties if the sequence should start over after its final file. OBS documentation notes that VLC Video supports playlists and that playlist looping is on by default, but verify the setting rather than assuming it suits your intended broadcast. A playlist is useful when one sermon should be followed by another item, but it also introduces an extra dependency: OBS and VLC must both work correctly on the machine.
The playlist route is not the same as a YouTube playlist. VLC Video feeds the selected local files into the OBS programme that is sent as one live broadcast. Viewers watch the continuous output from that broadcast; they are not choosing individual files from a YouTube playlist. If you are deciding between a continuous encoder output and a platform playlist, this guide on making a YouTube Live playlist repeat continuously in India addresses the different platform-side approach.
Before relying on a playlist, test the transition between at least two files and confirm that the picture and sound change cleanly. Check whether each recording has a different loudness level, aspect ratio or amount of black at the beginning. A sequence can technically play while still sounding uneven or showing blank margins at each transition. Adjust individual files beforehand where needed, rather than discovering the problem during a service.
| Workflow | Use it when | What you set up | Main trade-off |
|---|---|---|---|
| Media Source | One sermon repeats | Add one local file and enable Loop | Repeats only that selected recording |
| VLC Video | Several recordings rotate | Install VLC, add files in order and check Loop Playlist | Adds VLC as a dependency and requires a deliberate file order |
Connect OBS with YouTube’s URL and key
Create or schedule the live broadcast in YouTube Studio or the Live Control Room. YouTube provides a stream URL and a stream key for the encoder. In OBS, open the stream settings, select YouTube as the service if available, and enter the connection details shown in YouTube. The exact names of controls can change between software versions, so use the current YouTube and OBS instructions if a menu differs.
Treat the stream key as a password. Anyone who obtains it may be able to send a broadcast to the channel’s event, so do not put it in a public document, share it in a volunteer group chat unnecessarily or show it on screen. If it is exposed, replace it in YouTube Studio and update OBS with the new key before the next broadcast.
YouTube’s encoder guidance recommends RTMPS where supported. It also advises choosing video settings in light of available upload capacity, rather than assuming one setting suits every connection. The published guidance lists a 2–6 Mbps video bitrate range for 720p at 30 frames per second; treat that as platform guidance, not proof that the church’s connection can sustain it. A lower resolution or bitrate may be more dependable on a constrained or variable connection.
Once OBS is configured, start the encoder output and look at YouTube’s Live Control Room preview before making the event public or sharing it widely. If YouTube does not receive a signal, check that the correct event, stream URL and key are being used, that OBS is actually sending, and that the computer can reach the internet. Keep the stream key private while troubleshooting; there is no need to post it publicly to ask for help.
If you see an ingest warning or dropped connection, use the messages in YouTube’s control room to narrow down whether the problem is the incoming signal or the local setup. This guide to reading YouTube Live ingest errors can help you interpret those messages without guessing from the viewer’s picture alone.
Test the stream and monitor its health
YouTube recommends testing before a live event and monitoring stream health while it is running. Make a private or unlisted test event, start the encoder from OBS, and watch the preview on YouTube. Check that the sermon is visible, the speech is clear, the expected scene is live and the broadcast is not accidentally capturing volunteer conversation or notifications from the computer.
Do not stop at seeing a preview appear. Let the test run long enough to observe a file restart or playlist transition, and compare the audio at the start and later in the recording. Check playback from a second device or browser so that you know what a viewer receives, not just what OBS displays locally. If the service relies on captions, slides or a logo, check those elements in the viewer-facing output as well.
During the real broadcast, keep the Live Control Room available to a responsible person. Look for stream-health messages and confirm that the preview continues moving and that audio is still present. Someone watching the output can spot a frozen frame or silent source sooner than a volunteer who has only seen OBS report that it is open. If a fault appears, use the control-room status and OBS meters together to identify whether the file, audio source, encoder or connection is the likely cause.
For longer events, make a local recording if you need an archive you can control. YouTube says live streams under 12 hours are automatically archived, while streams over 12 hours may not be captured; it recommends keeping a local archive. DVR rewind features may also be limited on very long streams. See YouTube’s current archive live streams guidance before relying on the platform copy as the only record.
A separate local recording uses disk space and adds another task to test. Confirm the recording path and available storage beforehand, and check a sample file after a test. You do not want to discover after the service that OBS recorded to a disconnected drive or that the file is incomplete. If the archive matters, assign a person to check it rather than assuming the live broadcast has created a usable copy.
Understand the limits of a local computer and connection
OBS runs on the computer where it is installed. The machine must stay powered, awake and able to process the video and send it over the network for the whole broadcast. Sleep settings, operating-system updates, a restart, a full drive, an OBS crash or a power cut can interrupt a locally operated stream. A loop setting only repeats media while OBS is running and the broadcast remains connected.
The internet connection matters in the upload direction. A speed test taken once is only a snapshot; congestion and changes in service can affect a connection later. Test at the church, at the time and from the network that will carry the broadcast. Match the OBS output settings to observed capacity with room for variation, and avoid running large uploads or other demanding network activity at the same time where practical.
India is not one uniform network environment. A church in a city, a smaller town or a rural area may have different broadband, mobile coverage, power reliability and local network congestion. The official setup guidance does not establish a special India-only bitrate or a universal setting for every church. Test the actual venue rather than copying settings from another channel or assuming that a nominal plan speed guarantees stable upload.
The channel and the computer are separate points of failure. Confirm the channel’s eligibility in advance, preserve access to the account used by the church, and keep a trained person available to respond if the preview or audio fails. Some teams find it useful to document the steps for starting the correct scene and checking the key, rather than relying on one volunteer’s memory. For a broader comparison of operating approaches, including when a local machine is not the intended path, see which content creator path is right for you.
If the church needs continuous output with the local computer switched off, OBS alone does not meet that need. That is a different requirement from finding free software to run a loop on a computer at the church. Decide which trade-off matters: direct local control and a no-cost application, or an operating arrangement designed not to depend on the church computer staying on. Keep that decision separate from the question of whether the sermon and music are cleared for broadcast.
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
How do I loop a sermon video on YouTube Live?
Add the local sermon file to OBS as a Media Source and enable Loop in its properties. Connect OBS to the broadcast using the stream URL and key from YouTube Studio, then test the picture and sound before sharing the live event. The loop repeats only while the local computer and stream are running.
Can OBS loop a video or playlist on a live stream?
Yes. Media Source is the straightforward route for repeating one file. For a sequence of files, use VLC Video, install VLC, arrange the playlist and check Loop Playlist; test transitions before the service.
Does a free OBS setup run if the church computer is switched off?
No. OBS is local software, so the computer must stay on and connected for the broadcast to continue. A loop option does not make the setup hosted or unattended.
Will YouTube save the whole sermon stream automatically?
Do not rely on that for a very long broadcast. YouTube says streams under 12 hours are automatically archived and streams over 12 hours may not be captured, so keep a tested local recording if the archive matters. Check YouTube’s current archive guidance before the event.