A continuous YouTube stream from a church’s prerecorded videos can be built in OBS Studio: use a Media Source for one looping file or a VLC Video source for a playlist. Treat the subtitle file as a separate test, though; OBS’s documented controls do not confirm that it will automatically detect and attach an .srt sidecar.
First decide whether the words must appear in the picture for everyone or arrive as a selectable live caption track. Those are different outcomes, and a successful OBS preview of visible text does not establish that YouTube is receiving captions.
What “SRT subtitle videos” can mean
An SRT file is a text file containing subtitle cues and timings. It may sit beside a video as a sidecar, or the subtitles may already have been rendered into the video image. People often call both arrangements “a video with SRT subtitles”, but they behave differently in a streaming workflow.
Start by identifying what you have. Play each video on the same computer you plan to use for OBS, with the intended audio and subtitle file. Note whether subtitles appear without choosing a track, whether a player has a subtitle menu, and whether the church has another version with text permanently visible in the picture. Match each SRT file to its video rather than relying on filenames alone.
Check a few points across the programme: near the opening, somewhere in the middle, and near the end. Look for missing lines, drift between speech and text, unexpected language, or a final cue that remains on screen too long. This is a local asset check, not proof that OBS will behave the same way.
Write down the desired result before configuring the stream. If every viewer should see lyrics or a prayer, open captions rendered into the picture are the clearest route. If viewers should be able to turn captions on or off, you need a supported live caption-delivery path in addition to ordinary video playback.
Add a local video with OBS Media Source
For one church video, open a scene in OBS and add a Media Source. Select the local file, then confirm the source is visible in the preview and that its audio reaches the OBS mixer. The OBS Media Sources guide documents local media playback and a Loop option for a Media Source.
Enable Loop if the file is meant to repeat. Check what happens at the end: whether playback returns cleanly to the beginning, whether there is a pause or flash, and whether the first frame is appropriate to show repeatedly. A video that ends on a black frame may produce a noticeable gap even when looping is configured correctly.
Keep the scene straightforward at first. Fit the source to the canvas, inspect the edges for cropping, and make sure any lower thirds or church branding do not cover the subtitles. If you resize the canvas or change the source position later, recheck the subtitle area; text that was legible in a desktop player can sit too close to the edge in the stream.
OBS’s media controls are about playing the selected media source. They do not, by themselves, answer whether a separate SRT file is loaded. Do not infer sidecar support from a working video or from an on-screen subtitle seen in another player. Test the exact pair of files in the installed setup, as described below.
Loop one video or build a VLC playlist
A single repeated video is easier to inspect and troubleshoot. If the service is built around one sermon, devotional recording, or prayer video, begin with a Media Source and its Loop setting. Confirm that the repeat point is acceptable, particularly if spoken introductions, music, or a title card make the seam obvious.
For several files in a planned order, OBS’s VLC Video source can use a playlist and has a Loop Playlist option. The same OBS source documentation describes the playlist controls. VLC must be installed for this source, and OBS notes that 64-bit OBS needs 64-bit VLC. If the source is missing, check that requirement before rebuilding the scene.
Add clips in the intended sequence and keep Shuffle disabled if order matters. A church might place an opening hymn, a service recording, and a closing reflection in a set order; random playback could put the closing item first. Check each transition, because different encodings, aspect ratios, audio levels, or end frames can make an otherwise sound playlist feel abrupt.
| Approach | Useful when | What to verify |
|---|---|---|
| Media Source with Loop | One file should repeat | Repeat seam, audio, framing, and subtitle appearance |
| VLC Video playlist with Loop Playlist | Several files should play in a known order | VLC installation, sequence, transitions, subtitle controls, and exact sidecar behaviour |
| Subtitles rendered into the picture | Words must be visible to every viewer | Timing, spelling, contrast, safe margins, and legibility at stream size |
| Supported live caption delivery | Viewers need a selectable caption track | Encoder or software compatibility and captions received by YouTube |
A playlist is not a substitute for an overnight test. Let it pass through the transitions you expect to repeat, and listen for gaps as well as watching the picture. For further planning around repeated playlists, see how to avoid showing the same video twice on YouTube Live. That is a separate sequencing question from whether a subtitle sidecar is supported.
Check VLC subtitle controls and track selection
The VLC Video source interface exposes a Subtitles Enabled checkbox and a Subtitle Track selector. If the media exposes subtitle tracks, these controls let you enable subtitles and choose a track. Check the displayed language or track identity rather than assuming the first selection is the one the congregation needs.
This interface is a reason to test, not a guarantee about every file arrangement. The OBS documentation identifies subtitle controls but does not establish automatic detection or attachment of a separate .srt sidecar. A subtitle track contained within a media file and a separate file beside it are not interchangeable assumptions.
Use a small test scene and the exact video and SRT file. Try the available track controls, restart the source, and observe whether the intended cues appear at the right moments. Repeat with another video if the channel will rotate multiple files; success with one file does not establish behaviour for all the assets, formats, or naming patterns.
If the separate SRT does not appear, do not spend the night relying on an undocumented setting. Check the files in a desktop player to confirm the subtitle file itself is usable, then choose a dependable presentation route: prepare a video with captions rendered into the picture, or investigate a caption-delivery workflow that explicitly supports YouTube Live. Retest any converted file from its beginning through a representative section and the end.
A useful troubleshooting note records the video filename, its matching subtitle filename, the track selected, and what was visible in OBS. This makes it easier for another volunteer to reproduce the result and helps distinguish a bad subtitle asset from a source configuration issue.
Keep visible subtitles separate from live captions
Subtitles burned into the picture are part of the video image. Every viewer sees them as they watch, but they cannot be switched off as a separate caption track, and they are not the same thing as live closed captions. This is often a practical choice for lyrics, translated prayers, or a fixed-language service where consistent visibility matters more than viewer control.
YouTube’s live caption requirements say captions must be sent to YouTube. The documented options include embedded EIA 608/CEA 708 captions or supported caption software that sends captions over HTTP POST. The guide says YouTube currently supports one caption track. A plain SRT sidecar playing locally in OBS is not established by that guidance as a direct YouTube Live caption feed.
For selectable captions, confirm the full delivery chain rather than only checking a local preview. Establish that the encoder or caption software supports the required route, then confirm in a private or unlisted YouTube test that YouTube receives the track and that it behaves as expected on the watch page. Keep this separate from the video image: a viewer seeing words on screen is not evidence of a separate caption track.
If you are choosing between the two approaches, open and closed captions explained can help frame the accessibility and control trade-offs. For open captions, check contrast against bright scenes and keep the text large enough to read on a phone. For a selectable track, test the actual supported delivery path and do not promise a viewer control you have not observed.
Verify the sidecar before relying on it
Treat SRT handling as an unresolved property until you have tested the exact installed OBS and VLC setup with the exact files. The critical question is not whether OBS can play the video, or whether VLC can use subtitle files in some circumstances; it is whether this workflow loads this sidecar, stays in sync, and continues doing so after a restart and across the whole playlist.
Make a copy of the working scene and test one asset first. Start playback from the beginning, verify a cue early on, seek or wait to a middle cue, and check a cue near the end. Then stop and restart the source. If you are testing a playlist, check a second file and its subtitle pairing. Look for subtitles disappearing at transitions or continuing from the previous clip.
If the setup offers a subtitle track selector, note what choices it presents and whether the chosen track actually corresponds to the intended SRT. If no cue appears, distinguish among a missing sidecar, mismatched filename, unsupported arrangement, disabled control, and an SRT timing problem. Do not solve uncertainty by telling volunteers that OBS “should find it”; document only what the test demonstrated.
For a service that cannot risk missing words, render subtitles into a prepared copy of the video and inspect that copy before going live. This makes the words part of the picture and removes dependence on sidecar detection during playback, though it also means viewers cannot toggle them independently. Preserve the original assets, and keep a note of which prepared version is approved for streaming.
There is a separate operational choice about where playback runs. OBS requires a computer and a stable local playback setup; other approaches may suit unattended schedules differently. If you are weighing a dedicated computer against a hosted workflow, the practical considerations in cloud streaming versus a PC in India can help you assess power, connectivity, and who will monitor the stream. This does not remove the need to verify subtitle behaviour in the chosen workflow.
Connect YouTube and preview before going live
Before configuring an encoder, confirm that the channel is eligible to stream. YouTube’s live-streaming eligibility guidance says the channel must be verified and must not have live-streaming restrictions in the previous 90 days. Check the current official page for the channel’s status rather than assuming an older stream proves present eligibility.
In YouTube Live Control Room, create or schedule the event and use the encoder workflow to obtain the stream details. Enter the stream URL and key in OBS, keeping the key private. YouTube recommends RTMPS where available in its encoder settings guidance. Use the settings appropriate to your connection and video; do not treat a working local preview as confirmation that YouTube is receiving a healthy stream.
Run a private or unlisted test before a public service. YouTube’s live streaming tips recommend testing and monitoring. Check the YouTube preview and watch page, not just the OBS canvas: confirm picture, audio, subtitles, clip transitions, and whether the archive or replay behaves as intended. Ask someone to watch on a phone or another ordinary viewer device if that is how the congregation will join.
Let the test run through the parts most likely to fail: the opening, at least one transition, and a loop back or playlist repeat. Watch the stream health messages and listen for audio changes. If the stream is meant to continue unattended, plan who will notice a drop, who has access to the channel, and what the recovery steps are. A continuous programme still needs an accountable person and a tested restart plan.
A private YouTube stream test checklist is useful when you want to record these checks before changing the event to public. Keep the test private while you correct framing, missing audio, subtitle timing, or ingest problems. Do not infer caption-track delivery from visible text in the preview; confirm each separately.
Choose the least fragile playback plan
For many churches, the least complicated reliable plan is a single prepared video with open captions, looped in OBS and tested privately. A multi-video service can use a VLC playlist when order matters, but each file and transition needs checking. If selectable captions are essential, keep that requirement explicit and choose a compatible caption-delivery path rather than treating the SRT file as a plug-in caption feed.
An appliance may suit a team that needs scheduled prerecorded output without leaving a general-purpose computer running. YouTube’s encoder list includes the AJA HELO Plus and describes its PlayToStream functionality for scheduling prerecorded media to YouTube Live without a computer. It is a specialised option, not a prerequisite for an OBS setup; check current product details and availability before buying, and verify that its caption handling matches your needs.
Whichever route you use, keep the source files, prepared videos, OBS scene, stream key handling, and volunteer instructions organised. Record what was actually tested: which subtitle version was used, whether text appeared in the picture, and whether a separate live caption track was confirmed. Avoid wording such as “captions are working” when only one of those results has been checked.
For a no-computer-on-site workflow where the goal is to keep an uploaded video broadcasting, StreamNeo removes the specific burden of leaving the church’s playback computer running: you upload the file once and the stream runs from the cloud. It is YouTube-only, and it does not change the need to prepare and verify the subtitle presentation before use.
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 play an SRT subtitle file with a video?
OBS’s VLC Video source provides subtitle controls, but the reviewed OBS documentation does not confirm that a separate SRT sidecar is automatically detected or attached. Test the exact video, sidecar, and installed setup before relying on it. If every viewer must see the words, use a prepared video with subtitles rendered into the picture.
Can I use an SRT file as YouTube Live captions?
Do not assume that a local SRT sidecar becomes a YouTube live caption track. YouTube documents embedded EIA 608/CEA 708 captions and supported caption software sending captions over HTTP POST. Confirm the delivery route and track in a test stream.
How do I keep one church video repeating?
Add the local file as an OBS Media Source and enable Loop, then check the return to the opening frame and audio. For a fixed rotation of several files, use a VLC Video playlist with Loop Playlist and keep Shuffle off if order matters. Test the transitions before the public stream.
Do viewers see subtitles in the same way as captions?
Words rendered into the video picture are visible to viewers but are not a separate selectable caption track. Live captions are delivered separately through a supported caption workflow. Test and describe these outcomes independently.