If OBS stops repeating a video during a church YouTube stream, check the OBS source type and its playback properties before blaming YouTube. A Media Source does not loop by default, while a VLC Video source has different playlist and visibility behaviour.
The symptom can also come from changing scenes, hiding a source, or losing the connection between OBS and YouTube. Work through those stages separately so you know whether the file stopped, the scene reset it, or the live output failed.
Identify the source that is playing the video
Open the Sources list in OBS and identify the exact source carrying the church video. Do not assume that every video source has the same controls. The two relevant choices here are usually Media Source and VLC Video.
A Media Source plays a file directly from the path selected in its properties. It has its own Loop setting, along with controls for what happens when playback ends and when the source becomes active. OBS documents Loop as off by default. If the file reaches its end with that setting disabled, OBS has no instruction to start the file again.
VLC Video is a separate source type that uses VLC to play a playlist. It is not simply a Media Source with a different name. OBS documents Loop Playlist as on by default for VLC Video, but also documents a visibility behaviour that stops the source while it is not visible and restarts it when it becomes visible.
That distinction matters during a service stream. You may have one scene showing a hymn video, another showing a sermon slide, and a third showing a prayer loop. If the hymn is a Media Source, its loop checkbox is the first place to look. If it is a VLC Video playlist, inspect the playlist and its visibility behaviour instead.
VLC must be installed for the VLC Video source to appear. OBS also notes that 64-bit OBS requires 64-bit VLC. If you are building a playlist rather than playing one file, the guide on adding multiple videos to an OBS 24/7 stream playlist gives useful planning context, but the source properties still determine how OBS behaves when the source is hidden or reaches its end.
Turn on Loop for a Media Source
Right-click the Media Source in the Sources list and choose Properties. Confirm that the file path points to the intended video, then check Loop. Save the change and watch the file through its end in the OBS preview rather than testing only by dragging the timeline.
Loop applies to the file completing playback. It does not repair a missing file, a media decoding problem, a frozen application, or a failed stream connection. It also does not make a scene switch harmless. Those are separate conditions that need separate tests.
Look at the other Media Source properties while you are there. Restart playback when source becomes active controls what happens when the source enters the current visible scene. If it is enabled, returning to the scene can start the file from the beginning rather than continuing from the point where you left it. That may look like a failed loop when the source has actually been restarted.
Show nothing when playback ends controls the display after the file has finished. With Loop off, this can make the source disappear at the end instead of remaining on its final frame. A black or empty area is therefore evidence that the file reached an end-of-file state, not proof that YouTube rejected the video.
Close file when inactive is another setting worth noting. It can unload the file while the source is hidden or not active, which may introduce a reload delay when the source returns. The setting does not, by itself, prove that Loop has been disabled. Treat it as part of the source's inactive-state behaviour and test the actual transition.
For a single continuous devotional video, a Media Source with Loop enabled is often easier to reason about than a playlist. For several videos, a playlist can be more convenient, but you should decide whether a scene change is meant to continue playback, restart it, or stop it. Write that choice down before changing several settings at once.
Check VLC playlist and visibility settings
If the source is VLC Video, open its properties and inspect the playlist entries first. Confirm that every intended file is present, that the paths still work, and that the order is correct. A playlist can appear to have stopped when one entry is unavailable or when the source is following a visibility rule you did not expect.
OBS documents Loop Playlist as on by default for VLC Video. That is different from saying that every VLC playlist will always remain audible and visible through every scene change. VLC Video also has Visibility Behaviour. Its documented default is Stop when not visible, restart when visible.
Suppose a prayer scene contains the VLC source and a sermon scene does not. When you switch to the sermon scene, the VLC source is no longer visible. Under the default visibility behaviour, it stops. When you return to the prayer scene, it restarts. The resulting jump to the start of a file can be mistaken for a loop failure.
If you want playback to continue while the source is hidden, review the available visibility choice and select the behaviour that matches your programme. If you want each prayer segment to begin from the start whenever the scene returns, the default may be appropriate. Neither choice is universally correct; the important point is that visibility is part of playback control.
A playlist can also be the wrong tool for a single file that must repeat in a predictable way. Use a Media Source when you want to test one file and one Loop setting. Use VLC Video when you need a playlist and are prepared to check its playlist and visibility properties together.
This is separate from YouTube's own live playlist or scheduling features. If your operating plan is a YouTube playlist rather than an OBS playlist, keep the two systems distinct while diagnosing the fault. The guide to making a YouTube Live playlist repeat continuously in India concerns the YouTube side, whereas this article is primarily about the source inside OBS.
Review what happens when you change scenes
Scene changes are a common reason that a video appears to stop. OBS can make a source inactive when it is no longer visible, and a source can have a separate instruction for what to do when it becomes active again. The change may be intentional even if the operator experiences it as an interruption.
Make a simple map of the scenes used in the church stream. For each scene, record whether the video source is present, whether it is visible, and whether it is expected to continue playing when another scene is shown. This is more reliable than repeatedly switching scenes and trying to remember what happened.
Then test one transition at a time. Start the video, switch to a scene without that source, wait briefly, and return. Note whether the source continues from its previous position, pauses, stops, reloads, or starts at the beginning. Repeat the same test with the exact source used during the live programme.
For Media Source, pay particular attention to Restart playback when source becomes active and Close file when inactive. For VLC Video, pay attention to Visibility Behaviour. A source may be working exactly as configured while the configuration does not match the service plan.
You should also check whether the source is hidden using the eye control in the Sources list. Hiding a source is not always equivalent to leaving it visible behind another source. If an operator hides the video manually during a hymn and then reveals it later, that action can trigger the same visibility behaviour as a scene switch.
If the service uses separate scenes for lyrics, camera, announcements, and pre-recorded worship videos, consider whether the video should be a source in each scene or remain in a persistent scene layout. A persistent arrangement can reduce unexpected source activation, but it may not suit every production. Choose the layout that makes the operator's intended action clear.
Test the end of the file and the reset behaviour
Before changing network settings, run a local end-of-file test. Use a short copy of the same type of video, or allow the real file to reach its end while watching the OBS preview. Record whether it repeats, stays on its final frame, becomes empty, or starts again from the beginning.
If it remains on the final frame or disappears, inspect Media Source Loop and Show nothing when playback ends. If it starts again but loses its place after a scene change, inspect the activation and visibility settings. If it repeats locally but YouTube freezes at the same time, move to the output-delivery checks rather than changing the loop option again.
Do not infer too much from a black screen alone. A black display may mean that the source has completed and is configured to show nothing, that the source is hidden, that the file is reloading, or that the scene contains another layer over it. Look at the Sources list and the preview while reproducing the event.
A useful test record has four entries: the source type, the relevant property values, the scene transition, and the result in the local preview. For example: “VLC Video, Loop Playlist on, Stop when not visible, prayer scene to sermon scene, playback restarted on return.” That gives you a cause to correct rather than a general report that OBS stopped.
If the church stream combines old sermons, worship videos, and slides, test each file type separately. A loop setting cannot correct a damaged file or a format that OBS cannot decode consistently. If only one item fails while the others continue, compare that file's path, format, and behaviour rather than resetting the entire scene collection.
Content rights are another separate question. A video repeating correctly in OBS does not determine whether it can be streamed on YouTube. For a related planning question, see whether Bollywood songs can be played 24/7 on YouTube Live without copyright claims. Check the current YouTube live streaming policies and help guidance for the platform side of the setup.
Confirm that OBS is still reaching YouTube
Once the local preview behaves correctly, compare it with the YouTube output. OBS playback and YouTube delivery are different diagnostic stages. A video can loop normally in OBS while viewers see a frozen image, dropped frames, or a disconnected stream.
YouTube's live troubleshooting guidance directs operators to check the encoder output, reported errors, CPU load, and a local archive. Make a short local recording while the source reaches its loop point. If the recording is smooth but the public stream freezes, the media source is less likely to be the cause.
Next, check the connection to the ingest service and the stream statistics in YouTube Studio. Dropped frames and disconnections point towards connection stability, ingest reachability, or a bitrate that the connection cannot sustain. OBS's stream connection troubleshooting guide recommends a wired connection because Wi-Fi may be unstable, but that remedy is for a connection problem, not for a Media Source with Loop turned off.
Watch the computer's CPU load while the video is playing and while the scene changes. If the encoder reports an error or the system becomes overloaded, the output can fail even though the source itself has reached the correct loop point. Record the error message and time rather than relying on a later recollection.
If OBS cannot start the YouTube stream, check the stream key and the Live Control Room configuration. YouTube explains that a stream key directs the encoder feed to YouTube, while auto-start and auto-stop determine whether the stream can be started or stopped from the encoder. These settings control the live feed lifecycle; they do not control whether a local Media Source repeats its file. You can review the relevant YouTube encoder settings before replacing other OBS properties.
StreamNeo removes the need to keep the church computer running for this particular uploaded-file workflow: you upload the video, provide the YouTube stream key, and the cloud-run broadcast can be monitored and restarted if it drops. It is still important to check the file, rights, scene plan, and YouTube configuration before relying on any always-on arrangement.
Retest the complete scene and playlist sequence
After correcting a property, do not test only the one moment that failed. Run the same sequence used in the service: opening scene, announcement, worship video, sermon slide, return to worship video, and the expected end-of-file transition. Use the same source visibility actions that the operator will use live.
Start with a private or otherwise controlled test where possible. Watch the OBS preview, make a local recording, and watch the YouTube output separately. Mark the time of each scene change and each loop point. If the local recording and preview agree but YouTube differs, concentrate on encoder and network evidence.
A small test table can make the result clear:
| Test point | What to observe | What it suggests |
|---|---|---|
| File reaches its end in OBS | Repeats, stays on the last frame, or disappears | Check Loop and end-of-file display settings |
| Source is hidden and shown again | Continues, pauses, stops, or restarts | Check activation and visibility behaviour |
| Local recording at the loop point | Smooth or broken video | Separates local playback from delivery |
| YouTube output at the same moment | Smooth, frozen, dropped, or disconnected | Check encoder and outbound connection if different |
| Stream start | Starts normally or reports an encoder error | Check the stream key and YouTube configuration |
Change one setting at a time and repeat the relevant test. If you enable Loop, change a visibility option, and replace the stream key together, you may fix the symptom without knowing the cause. That makes the next overnight failure harder to diagnose.
For a fuller rehearsal, the guide on testing a YouTube lofi radio stream before making it public offers a useful testing mindset even though the content is different. The same principle applies to a church channel: test the complete sequence, not just the opening screen.
If the computer must stay on for OBS, include power, sleep, updates, and operator handover in the rehearsal. If the goal is to run the channel while the computer is switched off, compare the operating choices in the 24/7 YouTube streaming complete guide, then verify that the chosen workflow supports the exact file and scene arrangement.
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
Why does OBS stop a video at the end instead of looping?
If the source is a Media Source, Loop is off by default, so the file can reach its end without repeating. Check Show nothing when playback ends as well, because that setting can make a completed source disappear rather than remain on its final frame.
Why does the video restart when I change scenes?
The source may be stopping while hidden and restarting when it becomes visible. Check Restart playback when source becomes active for a Media Source, or Visibility Behaviour for a VLC Video source.
Why does OBS play correctly while YouTube viewers see a freeze?
That points to a possible encoder or delivery problem rather than automatically to the loop setting. Compare the OBS preview, a local recording, encoder errors and CPU load with YouTube's output, then check outbound connection stability if the local result is healthy.
Does changing the stream key fix a video that will not loop?
No. A stream key directs the encoder feed to YouTube and is separate from the playback properties of an OBS source. Replace it when YouTube or the encoder reports a start or authentication problem, but check the source's Loop and visibility settings for a local repetition problem.