If you want to repeat one recorded sermon on YouTube, OBS Studio is the practical free starting point. Its Media Source can play a local video repeatedly, while its VLC Video Source can rotate several recordings in a playlist.
The important limitation is that this is a local setup. OBS, the computer running it, and the internet connection all need to remain available, so a looped sermon file is not the same thing as guaranteed 24/7 availability.
Choose the playback job first
Start by deciding whether the channel needs one file repeated or a sequence of files played in order. The choice affects which OBS source you add and how much preparation the playlist needs.
If you have one complete sermon recording and want it to begin again when it ends, use Media Source. This is the simpler arrangement: select the file, enable Loop, and send the resulting scene to YouTube.
If you have several sermons, introductions, readings, or worship recordings, use VLC Video Source. It is designed for a playlist rather than a single item. You can put the files in the intended order and enable playlist looping so the sequence starts again after the last item.
| Job | OBS source | Additional software | Main trade-off |
|---|---|---|---|
| Repeat one sermon | Media Source | None beyond OBS | Simple, but the same recording repeats |
| Rotate several recordings | VLC Video Source | VLC installed in the matching bitness | More varied programming, with more setup to check |
| Run the channel without a local computer | Hosted streaming service | Depends on the provider | Avoids leaving a computer on, but current pricing and limits must be checked separately |
OBS itself is free and open source. The OBS Project says it is free for any use under GPLv2, with no watermark or usage limitation, and YouTube lists OBS among software options for encoder streaming. You can confirm those points in the OBS Project FAQ and YouTube's verified encoder software guidance.
That does not mean every part of the channel is free. You still need a computer capable of running the scene, a stable connection, electricity, the sermon files, and a YouTube channel that is ready to livestream. If this is a church or community channel, also check the rights for the sermon recording, music, images, and any other material inside the file.
Use OBS Media Source for one sermon
For a single recording, Media Source keeps the arrangement easy to understand. Open OBS Studio, create or select a scene, and add a Media Source. Give the source a recognisable name such as Sunday sermon, then choose the local video file.
In the source properties, enable Loop. OBS will return to the beginning of that file when playback reaches its end. The source can use common video formats including MP4, MOV, MKV, AVI, and WebM, as documented in the OBS Media Sources guide.
You can also decide whether the source should restart when the scene becomes active. That is useful if the sermon scene is stopped and later selected again. Keep the scene straightforward at first: a video source, perhaps a simple church logo or text layer, and no unnecessary browser sources that could introduce another point of failure.
A practical first arrangement might contain:
- one scene called
Live sermon; - one Media Source containing the recording;
- Loop enabled;
- the correct audio device selected in the source properties or mixer;
- a modest overlay only if it adds useful information, such as the service name.
Do not mistake the end of the file for a connection test. A recording can loop correctly inside OBS while the YouTube feed is dropping frames, losing audio, or failing to connect. Test both behaviours separately: first confirm that the local file returns to its beginning, then confirm that YouTube continues receiving the encoder feed.
Media Source is usually preferable when the same full sermon should be available repeatedly. It avoids the extra VLC dependency and makes it easier to identify which recording is on air. Its limitation is editorial rather than technical: viewers will encounter the same opening, pauses, and closing each time the file starts again.
If you are preparing a wider channel rather than a single service, the guide to streaming a Punjabi music radio channel on YouTube has a useful reminder that a recurring channel needs an intentional sequence of media, not just a working encoder.
Use VLC Video Source for a playlist
Use VLC Video Source when the channel should move through multiple local files. In OBS, add the source to a scene and use its playlist controls to add the sermons in the order you want them played. You can normally remove and reorder entries without rebuilding the whole scene.
Enable the source's playlist loop behaviour. The documented VLC source settings include Loop Playlist, which returns playback to the first item after the final item. This is different from placing several independent Media Sources in a scene. The VLC source handles the sequence as one playlist, whereas separate sources require you to manage their visibility and transitions yourself.
The playlist order is part of the broadcast plan. For example, you might arrange:
- a short welcome or title card;
- the first sermon;
- a reading or permitted musical interlude;
- the second sermon;
- a closing message.
After the final item, the playlist starts again if looping is enabled. Listen to the transition between every pair of files. Different recordings may have different volume levels, aspect ratios, frame rates, or silent sections at the start and end. VLC can play the files, but it does not make those editorial differences disappear.
A playlist also makes content review more important. Write down the filenames and order before adding them. If a file is replaced later, check that the new version still has the same name or update the source accordingly. Avoid moving the media folder after the setup works unless you are prepared to repair the file paths.
The VLC source requires VLC to be installed. It is not a self-contained OBS feature that works independently of VLC. OBS also documents a matching-bitness requirement: 64-bit OBS requires 64-bit VLC. If VLC is installed but the source is missing or does not behave as expected, check whether the OBS and VLC installations are both 64-bit or both 32-bit before troubleshooting anything more complicated.
This arrangement is a good fit when variety matters and you are willing to maintain a playlist. It is less attractive when one recording is all you need, because installing and updating another application adds another dependency to the local computer.
Install the compatible VLC version
Download VLC from the official VideoLAN site, then install the version that matches your OBS installation. Do not select a version only because it is the newest download shown on another page. First check whether your OBS installation is 64-bit or 32-bit, then install VLC with the same architecture.
On a typical current Windows installation, OBS may be 64-bit, but you should verify your own installation rather than assume. The matching-bitness point is the part that matters for the VLC Video Source. If the source does not appear after installing VLC, close OBS completely and reopen it. If that does not help, recheck the architecture and the installation location.
Keep VLC available on the same computer that runs OBS. Installing VLC on a different laptop or on the computer used to prepare the sermons does not satisfy the source requirement. OBS needs to access the local VLC installation while the scene is running.
Do not make changes immediately before going live without a test. An operating-system update, OBS update, VLC update, or file-folder change can affect a local setup even when the playlist itself has not changed. Record the working versions and save a copy of the scene collection and media list.
There is no need to install VLC if you are looping one file with Media Source. Keeping the simpler source for the simpler job reduces the number of things that can go wrong during an overnight broadcast.
Connect OBS to YouTube Live
Create or schedule the broadcast in YouTube Live Control Room. YouTube provides an encoder stream URL and a stream key for the connection. In OBS, open Settings, choose Stream, select the appropriate YouTube service or custom server option shown by your version, and enter the details supplied by YouTube.
Treat the stream key like a credential. Do not place it in a public screenshot, shared document, or chat message. If you think it has been exposed, use YouTube's controls to reset or replace it, then update OBS.
The basic order is:
- prepare the sermon scene or VLC playlist in OBS;
- create the broadcast in YouTube Live Control Room;
- copy the server information and stream key into OBS;
- start streaming in OBS;
- check the YouTube preview and stream health;
- start or confirm the broadcast in YouTube as required by the selected workflow.
YouTube says first-time live-stream activation can take up to 24 hours, according to its encoder guidance accessed in October 2026. Treat that as preparation time, not as a normal measured waiting period. A new channel should activate live streaming well before the first service rather than discovering the requirement at the planned start time.
YouTube's recommended encoder settings can change, so check the current official guidance for your chosen resolution and connection. The OBS bitrate settings guide can help you think through stability, but YouTube's current instructions should take precedence over any fixed value copied from an older article.
When OBS shows that it is streaming, do not rely only on the green indicator inside the application. Open the YouTube watch page or Live Control Room and confirm that the preview is moving and that audio is present. The step-by-step check for whether YouTube is receiving your RTMP stream is useful when OBS appears connected but the public feed is not behaving as expected.
Test the playlist and loop behaviour
Run a complete test before leaving the channel unattended. For one Media Source, watch the file reach its end and confirm that it begins again. For a VLC playlist, wait for the last item to finish and confirm that the first item returns. Do not assume a test of the first transition proves that the final transition works.
Check each file for four things:
- picture appears from the beginning rather than starting part-way through;
- audio is audible and does not disappear after a transition;
- the aspect ratio does not create an unexpected crop or black area;
- the next file starts in the intended order.
If the recordings have different loudness, use the OBS mixer to set a sensible level and listen on the YouTube feed, not just through local speakers. A local audio preview can differ from what viewers receive when the encoder is overloaded or a source is routed incorrectly.
Keep an eye on OBS's dropped-frame and connection indicators during the test. These are signals about the path to YouTube, not proof that the sermon file is valid. If the local video is smooth but the connection is unstable, investigate the network separately. If the connection is healthy but one file freezes or has no audio, inspect that file and its source settings.
Use the YouTube preview to check the final composition. Look for text hidden behind the player controls, a logo covering a face, or an overlay that becomes unreadable on a phone. A simple layout is often easier to monitor overnight than one with several animated elements.
Make a written recovery note for whoever may need to intervene. It should say which computer runs OBS, where the media folder is stored, how to open the scene collection, where the YouTube stream controls are, and how to stop the broadcast safely. Do not include the stream key in that note.
YouTube says streams under 12 hours are automatically archived, according to YouTube Help accessed in October 2026. Do not infer from that statement that a 24-hour broadcast will become one complete, automatically available archive. If preserving each sermon matters, keep the original files and decide separately how the channel should publish or organise them.
Plan for local computer and connection uptime
A local OBS stream makes the computer part of the broadcast system. The media files, OBS process, operating system, power supply, and internet connection all matter. If the computer sleeps, restarts for an update, loses power, or loses its network path, the YouTube stream can stop even though the playlist itself is configured correctly.
Before an overnight or all-day run, configure the computer so it does not enter sleep mode during the planned broadcast. Review automatic restart settings and avoid starting the stream immediately before a scheduled operating-system update. Keep the computer ventilated and connected to reliable power. These are operating precautions, not a guarantee that the stream will remain available.
A church may already have a suitable desktop or laptop. If it does not, a dedicated mini PC or desktop can be used as a local OBS host, but no particular model should be assumed to work without checking its own capability and condition. Buying hardware is optional, not a requirement of OBS or VLC.
The internet connection needs enough upload capacity for the selected stream settings and enough consistency to avoid repeated interruptions. If other people share the connection, large uploads, cloud backups, video calls, or software updates can compete with the live encoder. Schedule those activities away from the broadcast or use a separate connection where that is practical.
Monitor the first full playlist cycle rather than stopping after the initial connection. Keep a phone or another device open to the public YouTube page so you can see whether viewers receive video and sound. You can also check the Live Control Room for warnings and stream health.
If the stream disconnects, first establish whether OBS stopped, the computer lost internet access, or YouTube rejected or interrupted the feed. The practical guide to OBS disconnecting from YouTube helps separate those causes. Do not repeatedly restart everything without noting what changed, because that can hide the original fault.
There is a separate rights question as well. YouTube says live streams are scanned for matches to third-party content. If identified material remains in the stream, YouTube may interrupt or terminate it. A church setting does not automatically clear music or other third-party material, and a licence may not prevent an interruption if the rights holder has not allowlisted the channel through Content ID. Review YouTube's copyright guidance for live streams and confirm the current position before broadcasting.
For readers who do not want a computer left on, a hosted option changes where the encoder runs. It may remove the need to maintain a local Windows or macOS machine, but it is not automatically free, and current prices, limits, and supported workflows must be checked on the provider's own site. YouTube's encoder list includes several services, but a listing does not establish that a service offers free, unattended sermon looping.
StreamNeo removes the need to leave your local computer running by taking an uploaded video and sending it to YouTube after you provide the channel's stream key, with monitoring and automatic restart for interruptions. It is YouTube-only, so it is relevant when the specific problem is maintaining a YouTube broadcast rather than producing a show.
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 OBS repeat one sermon without VLC?
Yes. Add the recording as an OBS Media Source and enable its Loop property. VLC is needed for the VLC Video Source playlist workflow, not for repeating one file through Media Source.
Why is VLC installed but missing from OBS?
Check that VLC is installed on the same computer as OBS and that both applications use the same bitness. In particular, 64-bit OBS requires 64-bit VLC, then OBS may need to be closed and reopened before the source appears.
Does a looped sermon mean the YouTube channel is guaranteed to stay live?
No. The file can loop correctly while the computer sleeps, OBS stops, power fails, or the internet connection drops. A local setup needs operational checks and monitoring, and none of those precautions guarantees uninterrupted availability.
Will YouTube save a complete 24-hour sermon broadcast?
Do not assume it will. YouTube's guidance accessed in October 2026 says streams under 12 hours are automatically archived, so a longer broadcast should be treated separately from the original sermon files and checked against the current official guidance.