OBS Media Source can replay a local sermon video, while OBS separately encodes the scene and sends it to YouTube Live. Enabling Loop handles playback only; it does not connect OBS to YouTube or ensure that a broadcast stays live.
For one file, add a Media Source to the scene, choose the video and enable Loop. Then configure OBS’s streaming connection with a YouTube stream URL and key, test the complete path, and check the broadcast in YouTube Live Control Room before relying on it for a service.
How OBS playback and YouTube streaming fit together
Think of this as two jobs. The Media Source reads and repeats a file on your computer. OBS then captures the scene, encodes its picture and sound, and sends that output to YouTube using the encoder connection. A file repeating correctly in the OBS preview says nothing by itself about whether YouTube is receiving a stream.
This distinction is useful when diagnosing a failure. If the sermon stops in the OBS preview, check the file and Media Source settings. If it continues in OBS but YouTube reports no video or a weak connection, investigate the encoder connection, output settings and upload connection instead. The OBS troubleshooting checklist for insufficient video data is relevant when YouTube is not receiving a usable feed.
A local-file workflow also depends on the computer and OBS remaining available for the broadcast. Looping does not make a stream independent of the machine, the internet connection or YouTube’s live-stream controls. If your requirement is to leave your computer switched off after preparing a file, that is a different operating model from running OBS locally.
Before setup, make sure the sermon file is stored somewhere easy to find and plays normally on the computer. Check that the church has the necessary rights for any sermon, music, slides or other material it plans to rebroadcast. This workflow does not settle those rights questions; they depend on the specific material and circumstances.
Create or choose an OBS scene
A scene is the composition OBS sends: it may contain the sermon video alone, or combine it with elements such as a church logo, a title card or other visuals. Open OBS and select an existing scene if it is already arranged for the service. Otherwise, create a new scene and give it a clear name, such as “Sermon loop”, so it is easy to identify during a later test.
For the simplest setup, start with an empty scene and add the sermon as its only visual source. This makes it easier to see whether the file itself fills the output. Add decorative elements only after confirming playback; multiple sources can obscure the video or make troubleshooting harder. If the church wants devotional images to change between segments rather than a full sermon video, see how to rotate devotional images during a YouTube mantra livestream.
Check the scene preview after adding sources. OBS displays the composed scene, which is not the same as YouTube’s viewer-side playback. If the picture is too small or cropped, adjust its placement in OBS before moving on. Keep in mind that the stream’s final size and quality also depend on the encoder settings selected later.
Add the sermon as a Media Source
In the Sources area for the chosen scene, add a Media Source. Give it a recognisable name, then browse to the local sermon video. OBS’s Media Sources guidance lists common formats such as MP4, MOV, MKV, AVI and WebM. If a file will not open, verify that it is intact and in a supported format rather than assuming a YouTube setting is responsible.
In the source properties, point OBS to the correct file. Confirm the file path carefully: moving or renaming the video later can leave OBS looking for a location that no longer exists. Keep the video in a stable folder, particularly if the scene will be reused. OBS also offers options such as restarting playback when the source becomes active; these affect source behaviour and are separate from the streaming connection.
Once the source is added, check the scene preview for both picture and sound. If the video is visible but its audio is absent, inspect the OBS audio mixer and the source’s audio behaviour before the stream begins. A sermon with a static image but no audible speech can look normal in a quick visual glance, so listen to the preview rather than relying on the picture alone.
The built-in Media Source is the straightforward choice for a single sermon file. You do not need a playlist merely to repeat one video. For a different route involving prerecorded files and another streaming method, the guide to streaming recorded Assamese Gospel sermons all day provides useful context, but the steps here keep playback inside OBS.
Enable Loop for one file
Open the Media Source properties and enable Loop. OBS describes this control as replaying the file after playback completes; it is off by default. Start playback and watch the end of the sermon. The file should begin again in the OBS scene once it reaches its end.
Do not confuse this with a live encoder connection. Loop determines what the source does when the media file finishes. It does not start a YouTube broadcast, create a stream key, or reconnect OBS if the encoder feed is interrupted. You still need to configure and start the stream separately.
Check whether the ending is suitable for repetition. A video with a long black tail, a closing announcement or silence will repeat those moments each time. If the file is meant to play continuously, consider preparing an edited version with a deliberate ending and beginning, while preserving the sermon’s meaning. Do not cut or alter material in a way that misrepresents it.
Let playback reach the end during a test rather than merely checking that the first minute plays. Confirm that the opening returns, audio resumes and the picture remains in the intended scene. For a long sermon, you may plan this check ahead of the event; do not assume a loop works solely because the checkbox appears selected.
Use a playlist for a sequence of clips
If the church wants several clips in a deliberate order, OBS offers a VLC Video source. Add the required files to its playlist and enable Loop Playlist so the sequence repeats. This is different from using one Media Source with Loop: the playlist handles a sequence of items, while a single-file source repeats one item.
The VLC Video source requires VLC to be installed. OBS notes that a 64-bit OBS installation requires 64-bit VLC. If the source is missing or does not work, check the installed VLC version and its compatibility before rebuilding the scene. The playlist route also adds a dependency that a single local Media Source does not need.
| Need | OBS source and setting | What repeats | Consideration |
|---|---|---|---|
| One sermon video | Media Source with Loop enabled | The selected file | Simpler setup; check the end and restart in preview |
| Several clips in order | VLC Video with a playlist and Loop Playlist | The playlist sequence | VLC must be installed, with matching 64-bit compatibility for 64-bit OBS |
Neither choice sends anything to YouTube on its own. In both cases, OBS must still encode the scene and transmit it through a configured encoder stream. The content played back can change while the transmission remains the separate job of OBS. This is the same distinction to keep in mind when looking at other continuous-stream approaches, such as using FFmpeg to stream prerecorded video.
Connect OBS to a YouTube encoder stream
In YouTube Studio, open Go Live and create or select an encoder stream. YouTube’s live-stream settings help page explains the controls for the stream, including its visibility. For a rehearsal, choose a visibility setting suitable for testing, such as unlisted or private, and verify it rather than assuming the default matches your intention. YouTube’s default visibility can differ according to the user’s age.
Copy the stream URL and stream key shown for the encoder stream into OBS’s streaming connection settings. Treat the key like a password: do not put it in a public document or share it in a screenshot. YouTube says a compromised key can be reset in Live Control Room. If you suspect it has been exposed, reset it there and update the OBS connection before the next broadcast.
Before starting, choose output settings the internet connection can sustain. YouTube’s encoder settings guide covers supported video codecs, bitrate guidance, frame rates and keyframe intervals for encoder streams. As a specific example rather than a universal rule, YouTube’s guidance lists 5 Mbps as a recommended H.264 bitrate for 1080p at 30 fps. The right choice depends on the resolution, frame rate and available upload capacity.
A higher resolution does not help if the connection cannot sustain its bitrate. YouTube’s live streaming tips recommend leaving 20% upload bandwidth headroom. That is a buffer against variation, not a promise that a particular connection will work. If your available upload capacity fluctuates, reduce the output demand and run a test rather than selecting settings by appearance alone.
YouTube recommends a two-second keyframe interval and says it should not exceed four seconds in its encoder guidance. Select an appropriate setting in OBS and check its output configuration. YouTube lists H.264, H.265 and AV1 video for RTMP/RTMPS encoder streams; the specific options exposed by your OBS setup may depend on the encoder available on the computer. Avoid changing several output controls at once during troubleshooting, since that makes the cause of a change harder to identify.
Preview and verify the complete loop
Run a private or unlisted test before the service. Start the OBS stream and inspect the YouTube Live Control Room preview. Confirm that YouTube receives a picture, that the sermon audio is audible, and that the stream health messages do not show a problem needing attention. A clean OBS preview is useful, but only the YouTube-side preview checks the connection end to end.
Let the file finish and confirm its restart in both OBS and the YouTube preview. Listen across the transition: a loop can have a visible image and still fail the practical test if the audio cuts out, resumes at the wrong point or is too quiet. Check the stream’s visibility, title and other event details in YouTube Studio before making it public or using it for a service.
For upload planning, compare the encoder’s bitrate demand with the connection available to the computer that runs OBS. YouTube’s suggested headroom is useful, but household or church connections can vary during the day. If the test reports instability, lower the output bitrate or resolution and repeat the test. For more on the local-computer trade-off in an always-on setup, see what it costs to run a 24/7 YouTube stream with an Apple Mac mini.
Eligibility and channel readiness are separate from configuring OBS. YouTube’s live streaming onboarding guidance describes eligibility conditions, including a minimum age of 16 and no live-stream restrictions in the past 90 days. Check the current official page for your channel rather than treating those conditions as approval guarantees.
During the service, monitor the YouTube stream and the computer running OBS. A looped file can keep replaying locally even if the broadcast connection fails, so playback alone is not evidence that viewers are receiving it. If the stream drops, diagnose the transmission path and YouTube status separately from the media source. The safest preflight is one complete test with the intended file, audio, scene, visibility and encoder settings.
For churches that do not want a local computer to remain on for the broadcast, StreamNeo removes that particular need by turning an uploaded video into a YouTube live stream that can run with your computer switched off; it is YouTube-only. That is a different workflow from the OBS setup above, so decide based on whether local control or not having the computer run is more important for your service.
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 in OBS?
Add the local video as a Media Source, open its properties and enable Loop. Play it through its ending in the OBS preview to confirm it starts again. This setting repeats the file locally; it does not connect OBS to YouTube.
How do I make a sermon video repeat on YouTube Live?
Set the repeat behaviour in OBS, then separately connect OBS to a YouTube encoder stream using the stream URL and key. Start a private or unlisted test and verify the repeated video, audio and stream health in Live Control Room. A local loop does not guarantee a continuous broadcast.
Where do I put my YouTube stream key in OBS?
Use OBS’s streaming connection settings to enter the URL and key copied from the encoder stream in YouTube Studio. Keep the key private, because anyone who obtains it may be able to use the stream connection. Reset it in Live Control Room if it is compromised.
How much upload speed do I need to stream from OBS?
It depends on the chosen codec, resolution, frame rate and bitrate, as well as how steady the connection is. YouTube recommends leaving 20% upload bandwidth headroom; test the actual setup and lower the output demand if stream health is unstable. A bitrate recommendation for one format, such as H.264 at 1080p and 30 fps, is not a universal setting.