OBS plays and repeats the sermon file on your Windows PC, then sends its encoded feed to a YouTube Live event. YouTube does not loop a file from your computer for you: the repeat is set up in OBS, and you should wait for YouTube Studio’s incoming preview before you click Go live.
The handoff matters. Prepare the channel and PC in advance, connect OBS to the correct Studio event, check the picture and sound in its preview, and only then publish the stream.
Prepare the Windows PC and sermon file
First confirm that you can use the channel’s live-streaming features. YouTube says the channel must be verified and must not have had a live-streaming restriction in the previous 90 days. Initial live-streaming activation can take up to 24 hours, so enable it well before the service rather than discovering a delay at the last minute. Check the current YouTube live-streaming eligibility and setup guidance for the channel’s status and any current requirements.
Install OBS Studio from its official download page, choosing the Windows version that matches the PC. OBS lists Windows 10 and Windows 11 as supported and gives a DirectX 10.1-compatible GPU as a basic requirement. Meeting that baseline does not guarantee that an older computer can encode the resolution, frame rate and scene you choose. Run OBS’s Auto Configuration Wizard, then test the actual machine and internet connection with the sermon file you intend to use.
Keep the recording in a local folder that will remain available while OBS is running. Avoid moving, renaming or disconnecting it after you have added it as a source; OBS needs to find that file for playback. MP4 is among the formats OBS supports as a Media Source. If the file does not open or its audio is missing, resolve that before connecting to YouTube rather than trying to troubleshoot the file while the event is waiting.
Also check the content, not just the file. A church may have a recording without holding every right needed to stream it. Confirm permissions for the sermon, music bed, photographs, slides and other third-party material with the relevant rights holder or the church’s licensing administrator. The applicable answer depends on the particular content and licence; a copy on the church computer does not settle it.
A spare PC is still a computer that needs to stay awake. Review Windows’ power and sleep settings, including what happens if the machine is a laptop and its lid is closed. Labels differ by Windows version and device, so check the settings on the actual machine. Preventing sleep avoids one avoidable interruption, but does not guarantee that the PC, network or broadcast will stay up.
Create an OBS scene
Open OBS and create a scene for the sermon broadcast. A scene is the layout OBS sends to the encoder; for a single-file loop, it can be deliberately simple. Give it a recognisable name such as “Sunday sermon loop” so you can distinguish it from any camera, test or previous-service scenes in the list.
You can add a still image or a church title card if it is useful, but keep the first test uncomplicated. A title card with a service name or a small logo is a different visual element from the sermon file, and it is worth checking that it does not obscure subtitles or important text in the recording. If the job is simply to repeat one sermon, a single Media Source is enough.
Look at OBS’s canvas and preview before adding the source. The source can be resized to fit the canvas, and you can use the preview to check the composition. Do not assume that a source fitting the OBS window means every viewer’s screen will show the intended framing; test the actual output and check for cropped text or black bars. OBS’s Media Sources guide explains the available source controls.
If you are building a playlist rather than repeating one sermon, that is a different setup. OBS’s VLC Video source can use a playlist and loop the playlist, but it adds a VLC installation dependency; 64-bit OBS needs 64-bit VLC. For one file, the regular Media Source has fewer moving parts. For a longer service rotation, see how to prepare a YouTube playlist for a continuous live stream and decide whether the playlist workflow is actually needed.
Add the sermon as a Media Source
In the selected scene, open Sources, choose the plus button, and select Media Source. Create a new source, give it a useful name, and browse to the local sermon recording. Make sure the file path shown is the intended recording, especially if the PC has copies with similar names such as a final export and an earlier edit.
Once the source is added, OBS should show the video in its preview. Check that the opening image is the right one and that the picture is not unexpectedly stretched or cropped. Listen through OBS’s audio mixer or another monitoring route at a sensible level: a visible meter confirms that audio is present at the source, but it does not tell you whether the recording sounds clear to a viewer.
A sermon recording can include quiet speech, a loud music introduction, or a long pause. Listen to representative sections rather than only the first few seconds. If the source appears silent, check that the correct audio track is selected in the Media Source properties and that OBS has not muted the source. Do not treat a moving meter as proof that the YouTube audience will hear the intended mix; verify the YouTube preview as well.
If OBS cannot play the recording reliably, pause here. Check that it plays locally, that its format is supported, and that the source points to the right file. Converting a video can solve some format problems, but use a suitable export and inspect the result before substituting it. For one specific older-format case, the guide to converting FLV videos for a YouTube 24/7 stream covers why format compatibility should be checked before a broadcast.
Enable Loop and check the preview
Open the Media Source properties and enable Loop. OBS describes the setting as repeating the file after playback has completed. This is the part that makes a single local recording begin again when it reaches its end; YouTube is not fetching or repeating the file itself. Keep the source and scene in place while the broadcast runs, because OBS is supplying both the playback and the encoder feed.
Check how the transition looks. Watch the end of the recording and its return to the opening, if time permits. A file that ends on a blank frame, an abrupt audio cut or a long pause will repeat those characteristics too. Looping does not edit the recording or remove silence. If the sermon is intended for a public channel, decide whether a visible transition or title card would help viewers understand that the recording has restarted.
For a practical test, play the source in OBS and let it run long enough to confirm picture and sound. Do not infer full-stream readiness from a few seconds of playback: encoding load, network behaviour and Windows power settings still need to be checked. YouTube advises testing with comparable content and monitoring stream health. A static sermon file may be less demanding than a multi-camera scene, but the spare PC and connection are the deciding factors.
The video should be framed as intended in the OBS preview, and the audio should be neither muted nor unexpectedly loud. If you need a target output, choose it after testing rather than selecting the highest available option. YouTube’s encoder guidance recommends a constant bitrate (CBR) for H.264 over RTMP or RTMPS and a two-second keyframe interval, not exceeding four seconds. Its table lists 5 Mbps as the recommended H.264 video bitrate for 1080p at 30 frames per second. Those are YouTube’s published reference settings, not evidence that this particular PC or upload connection can sustain them. See YouTube’s encoder settings guidance and test a lower resolution or bitrate if the feed struggles.
Copy the stream URL and key from Studio
In YouTube Studio, open Create, then Go live. Create a new stream or select the event you have already scheduled. Check its title, visibility, audience settings and schedule before connecting the encoder; it is easy to prepare the correct file for the wrong event when a channel has several scheduled broadcasts.
In the Live Control Room, find the encoder connection details and copy the stream server URL and stream key into OBS’s stream settings. YouTube’s encoder workflow instructions describe entering these details in the encoder. Use the URL and key for the event you intend to run, and avoid sharing them in screenshots or messages. Treat the key like a password: someone who has it may be able to send a feed to the channel. If it is exposed, reset it in Live Control Room using YouTube’s current instructions.
The channel and event must be ready for a live encoder before the service begins. If this is the first time the channel is going live, or live streaming has not been enabled, sort that out early. A verification prompt or activation delay is not something OBS can resolve. If the channel is stuck at phone verification, the guide to YouTube Live activation and phone-number verification may help you identify which step remains.
For an ordinary sermon loop, follow the RTMP or RTMPS encoder workflow in Studio. YouTube’s encoder guidance recommends RTMPS for encrypted ingestion where available. HLS has different supported workflows and higher latency, and is not needed for the basic one-PC setup described here. Keep the selected protocol and OBS connection details aligned with the instructions shown in the event.
Start OBS and verify the incoming preview
With the correct scene active and the Media Source ready, start streaming in OBS. This starts the encoder feed; it does not, by itself, mean the YouTube event is public. Return to YouTube Studio and wait for the incoming preview to appear in the Live Control Room. The handoff is not complete until Studio is receiving the feed you expect.
Inspect the preview for the sermon image, framing and sound. Confirm that the event title and visibility are correct, and check the stream-health indicators. If the preview is black, still loading or showing the wrong scene, do not click Go live yet. Return to OBS to check the active scene, source visibility, file playback and connection settings. If OBS says it is streaming but Studio does not receive a usable feed, check the server URL and key against the selected event.
A preview that looks correct at the start is useful, not a promise about the rest of the broadcast. Keep the PC awake, avoid launching unnecessary applications, and watch the event after it begins. A wired connection can be worth testing if the PC and network support it and Wi-Fi is the source of dropouts; a cable by itself does not guarantee a reliable connection. For a connection-specific troubleshooting reference, see what to check when a YouTube stream buffers on JioFiber. Test the connection you will actually use for the service.
This is where an always-on arrangement differs from a one-off local test. A spare Windows PC and OBS can send the loop while they are running, but the church remains responsible for power, sleep settings, network and the encoder process. If the computer needs to be switched off or is hard to supervise overnight, StreamNeo removes the need to leave that PC running by turning an uploaded video into a YouTube live stream; the remaining decisions about the event and the content still belong to the channel operator.
Click Go live when ready
Click Go live in YouTube Studio only after the incoming preview appears and you have checked the image, audio, event details and stream health. OBS supplies the repeated file and encoder feed; YouTube Studio is where you make the event live. Keeping those actions distinct prevents a common mistake: assuming that pressing Start Streaming in OBS has published the event.
Once live, check the public viewing experience as well as the control room where practical. Confirm that the correct sermon is playing and that the sound reaches the audience. Continue to monitor the stream and the PC during the service. YouTube recommends monitoring audio and video during a live broadcast, and the same principle applies to a prerecorded file: a source can stop, a computer can sleep, or a connection can fail even when the file itself was prepared correctly.
At the end, end the event in YouTube Studio and stop the OBS encoder. Do not leave the event running because the file has looped back to its beginning. YouTube says streams under 12 hours are automatically archived; check the current official guidance if the recording is longer or if the archive matters to your church. Ending the event and stopping OBS are separate actions, so confirm both are finished.
Before relying on the setup for a service, rehearse the full handoff: open the event, connect OBS, wait for preview, check it, Go live, and end the event cleanly. Use an unlisted or private test where suitable, and confirm the visibility and audience settings before the actual service. That rehearsal catches problems with access, scene selection, audio and the button sequence without asking viewers to wait while you troubleshoot.
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 loop a sermon file from my PC?
No. OBS plays the local file and sends its encoded output to YouTube. Enable Loop on the OBS Media Source if you want playback to repeat; YouTube Studio receives the feed rather than repeating the computer’s file.
Do I click Start Streaming in OBS or Go live in YouTube first?
Start the encoder in OBS, then wait for the incoming preview in YouTube Studio. Check that the preview is correct and click Go live in Studio when you are ready to publish the event.
Can I use an older spare Windows PC?
Possibly, but OBS’s basic system requirements do not guarantee that a particular machine can stream at a chosen quality. Run the Auto Configuration Wizard and test the actual sermon, scene and connection before depending on that PC for a service.
What should I check if Studio does not show the preview?
Make sure OBS is streaming the intended scene and that the Media Source is visible and playing. Compare the stream URL and key in OBS with the event open in YouTube Studio, then check the PC’s connection and the current Studio stream-health information. Don’t click Go live until the expected preview arrives.