If viewers only need to read subtitles in the picture, you can display a supported subtitle track in OBS and send the resulting scene to YouTube. If they need to switch captions on or off, or choose a language in the YouTube player, you need a separate live-caption delivery path; an OBS subtitle track alone does not provide that.
Start by deciding how viewers should access the words, then prepare and test the matching workflow. A sidecar SRT file can be useful for preparing text and timing, but it does not by itself send captions to a YouTube live stream.
Choose visible subtitles or selectable captions
There are two different things that can look similar while you watch your own preview. Subtitles composited into the scene are pixels in the video image. Captions delivered separately are timed text data supplied to YouTube, where the viewer can use the player’s caption controls if the delivery path supports it.
For a devotional loop, a guided meditation, a local announcement, or a language lesson, always-visible text may be exactly what you want. The audience sees the words whether or not they enable captions, but cannot hide them or select another track through YouTube’s caption menu. If you put a Hindi translation into the OBS image, for example, it remains part of the image for every viewer, even if a viewer prefers English or no text.
Selectable captions are a better fit when viewers need control over whether text appears, or when a particular audience needs a caption language distinct from the visible video. YouTube documents live captions delivered as embedded EIA-608/CEA-708 data from a compatible encoder, or through supported caption software that sends captions over HTTP. This is not a property that every encoder, video file, or subtitle format automatically has. YouTube’s live caption requirements describe the delivery paths to check.
There is also a third workflow for a replay or uploaded video: add subtitles in YouTube Studio after upload. That gives viewers caption controls on that video, but it does not send captions during the live broadcast that produced it. YouTube’s supported subtitle formats and instructions for adding subtitles apply to the uploaded-video workflow.
| Option | What viewers get | Useful when | What it does not do |
|---|---|---|---|
| Track displayed by OBS in the scene | Words are visible in the video image | Text should always be on screen with prerecorded playback | It does not give viewers YouTube caption toggles or language selection |
| Captions delivered to YouTube Live | Caption controls in the player, when delivery works | Viewers should be able to control live captions | A sidecar file or OBS display setting alone does not deliver the caption data |
| Captions added in YouTube Studio to an upload | Caption controls on the uploaded video | You are preparing a replay or VOD | It does not caption the earlier live broadcast |
Choose based on the viewer’s need, not only on which file you already have. If your existing video has an SRT file and your priority is readable text in a continuous broadcast, test whether OBS can display it. If the requirement is selectable live captions, first confirm that your encoder or supported caption software can send data by a documented route, then test the YouTube player itself.
For a continuous channel, that decision affects the whole content workflow. A prerecorded rosary stream might benefit from a fixed on-screen translation, while a spoken English lesson stream may need viewers to control captions independently. Do not assume one approach serves both audiences equally well.
Check subtitle tracks in the source file
Before changing OBS settings, find out what text is available and whether it matches the video. A video may contain one embedded subtitle track, several language tracks, or no subtitles at all. A separate file beside the video is a sidecar; it may have the same base name, such as lesson.mp4 and lesson.srt, but the filename does not prove that the timing and content match.
Open the source in a player that can show track and language information. Note the exact video version, track language, and whether the subtitle is embedded or separate. Then play portions near the beginning, middle, and end. Check that dialogue and text align, that the intended language appears, and that no recent edit has shifted later cues out of time. A shortened intro or an inserted announcement can make an otherwise good subtitle file drift.
For a basic sidecar, SubRip (.srt) or SubViewer (.sbv) are straightforward formats in YouTube’s guidance. An SRT file is plain text with cue numbers, timecodes and text. For example:
1
00:00:00,600 --> 00:00:04,160
Welcome to the stream.
2
00:00:04,160 --> 00:00:06,770
Today we are preparing subtitle tracks.
When preparing SRT for YouTube’s uploaded-video workflow, save it as plain UTF-8. Do not depend on styling markup: YouTube’s supported-format guidance says style markup is not recognised. OBS/VLC playback compatibility is a separate question, so test the actual file in the source you plan to use rather than assuming that a format accepted for upload will behave identically in VLC Video.
Check spelling, punctuation, names and speaker labels against the final audio. Add meaningful non-speech cues where they help a viewer understand the programme, such as a relevant sound or a change of speaker; avoid filling every musical bar with text that does not help. For a bhajan or ambient stream, decide whether lyrics are intended to be read throughout or only at selected points, and check that the language and transliteration are consistent.
If your work is primarily ambient, the Himalayan singing bowl stream guide offers a related planning context: text should serve the viewing experience rather than obscure the image. Likewise, when a loop has transitions or a gap between files, the church stream loop guidance is relevant to planning the playback sequence, though it does not replace subtitle checks.
Add the file to an OBS VLC Video source
OBS has more than one source type for video playback. Its Media Sources documentation lists Media Source support for containers including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM. For the subtitle enable control and track selector described in that documentation, use a VLC Video source. OBS states that VLC must be installed for this source to be available.
In OBS, add a VLC Video source and point it to the video file or playlist you intend to play. If you are preparing a single clip, start with just that item so you can isolate subtitle behaviour from playlist or looping behaviour. Confirm that the video itself plays in the source before troubleshooting the subtitles. If the source is not available in OBS, check whether VLC is installed and whether the current OBS setup recognises it.
A container name alone cannot confirm subtitle support. A file may play its picture and sound while a particular embedded subtitle codec or track does not render as expected in the installed OBS/VLC combination. Keep a copy of the original and test the exact file on the computer and versions that will run the stream. If you later replace the video with an edited export, repeat the check: the new file may have a different track order, missing subtitles, or changed timings.
Use a short representative section first. Include a moment when subtitles appear, a moment when they should disappear, and any language or speaker change that matters. This is more useful than simply seeing that the video has a subtitle track in another player. The goal is to verify the route from source file, through VLC Video, to the OBS scene.
Enable and select the subtitle track
OBS documents a “Subtitles Enabled” setting and a “Subtitle Track” selector for VLC Video; subtitles are off by default. Open the source properties, enable subtitles, and choose the intended track. If the file has multiple tracks, use the track information you recorded earlier rather than guessing from track order. Track labels may be absent or unclear, so confirm the displayed language by watching actual dialogue or lyrics.
Do not confuse this control with a YouTube caption setting. Enabling a subtitle track in VLC Video tells OBS to show its text as part of the scene output. Once encoded into the picture, it is not a separate caption stream. Viewers cannot use the YouTube caption control to turn that composited text off or choose a different track.
If the selector is unavailable, the track does not appear, or the preview stays blank, check the simple things first: the source type is VLC Video, VLC is installed, subtitles are enabled, and the selected track is the one that contains text. Then test another section of the file. The subtitle may have no cue at the current playback time. Compatibility can also vary with the file’s container, subtitle format, and current software versions; the OBS documentation does not promise that every combination works.
If the embedded track remains unreliable, a practical fallback for visible text is to create a version with subtitles rendered into the image in a suitable editor. That removes track selection from playback, but it also makes the text permanent in the picture. Review the exported version from beginning to end and keep it distinct from the original so you can return to the uncaptioned file or make a corrected export later.
For a long-running playlist, make a small test playlist with the same source configuration and transitions as the planned broadcast. Confirm that the correct language remains selected when a new item starts. This is especially important where several videos use different track orders or one has no subtitle track; a setting that works for the first clip does not prove that every item in a sequence behaves the same way.
Understand YouTube Live caption requirements
YouTube’s live-caption guidance is about captions being sent to YouTube, not merely displayed in your scene. In its words, “To add captions to your live stream, you need to send captions to YouTube.” The page describes embedded EIA-608/CEA-708 captions from a compatible encoder and supported software that sends captions over HTTP. For the embedded path, YouTube’s setup instructions refer to enabling closed captions in the live setup, selecting Embedded 608/708, and configuring the encoder to provide the relevant caption data.
That is a separate delivery path from selecting a VLC subtitle track in OBS. The fact that OBS displays a subtitle correctly does not establish that the stream encoder is sending selectable caption data. Check the documentation for the exact encoder or caption software you intend to use, and confirm that it supports the method in YouTube’s current instructions. If you cannot verify the path, describe the planned result as visible on-screen subtitles, not selectable live captions.
YouTube notes that the EIA-608/CEA-708 standards allow multiple language tracks but says it currently supports one embedded caption track. Treat this as platform guidance that may change, not as a reason to assume your setup is compatible. If multiple selectable languages matter, check current YouTube requirements and the actual caption software’s capabilities before building the programme around that expectation.
YouTube also documents live caption ingestion through a signed HTTP URL for a supported workflow and advises accurate system time. Follow the current Studio instructions for the event and caption service you are using; do not copy a URL or configuration from an old stream without checking it. A caption workflow must continue to deliver timed data during the broadcast, and timing errors can make correct words appear at the wrong moment.
Automatic live captions are another, separate feature. YouTube’s current help describes restrictions and availability conditions, and says live automatic captions do not remain on the video after the stream. It describes English-only support in its current guidance, alongside channel, latency, audio and language limitations. Availability can change and may depend on the channel, so check the live settings and current automatic captioning guidance rather than planning on it as a guaranteed substitute for prepared captions.
Uploaded-video captions remain useful for the replay even if live delivery is not in place. After a stream, you can work through YouTube Studio’s subtitle workflow for the video, choose a language and upload a timed file or use another supported method. That creates a separate task after the broadcast; it does not retroactively make the live output captioned.
Test readability and timing in the output
The OBS preview is necessary but not sufficient. It shows what OBS is composing, while viewers see the encoded stream after YouTube receives and processes it. First check the preview at the size and aspect ratio your audience will see. A subtitle that is readable on a desktop monitor may be too small on a phone, especially if the video already contains lyrics, a logo, or other text near the bottom edge.
Check contrast against the brightest and darkest parts of the image. If the subtitle blends into the background, revise the video or subtitle treatment before relying on it. Keep lines clear of important faces, instruments, translated lyrics, and any information the viewer needs elsewhere on screen. Avoid placing text so low that the player’s controls or device layout may cover it. These are visual checks, not a promise that the same layout will work on every device.
Watch the first cue, a few cues during playback, and the last cue against the final video. Confirm that each line appears when the speech or lyric begins, remains long enough to read, and clears before the next line creates a clash. Check transitions between clips, too: an old cue should not continue over a new scene, and the next clip should not begin with text from the previous one. For a loop, inspect the join where playback returns to the start.
If you need selectable captions, test with a private or unlisted stream where your channel workflow permits it. View the stream on YouTube, not only through OBS, and verify that the caption control is present and that the expected words appear at the correct times. If you need visible subtitles, check the YouTube output and make sure the text is present in the image. These are different tests: a successful visible subtitle test does not validate live caption delivery.
Make corrections against the final asset, not an earlier cut. If you replace an intro, trim silence, change playback speed, or add a new announcement, revisit cue timing. Keep the source video, subtitle file, language note, and final export together with clear names. That makes it easier to identify which caption track belongs to which version if you revisit the stream weeks later.
For a 24/7 channel, also plan what happens after a playback interruption or restart. Confirm that the selected source and track recover as intended, and check a fresh YouTube output rather than assuming the OBS preview has resumed correctly. A continuous relaxation stream workflow can help with broader playback planning, but subtitle integrity still needs its own test for each file and language.
If keeping a computer running just to play prerecorded content is the part that makes the workflow difficult, StreamNeo can remove that specific burden by running an uploaded video as a YouTube live stream with your computer off. It does not change the distinction here: visible text needs to be part of the video output, while selectable captions require a compatible caption delivery path.
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 viewers switch off subtitles selected in OBS?
No. When OBS displays a VLC subtitle track in the scene, the text is composited into the video image. Viewers cannot turn it off or select another language using YouTube’s caption control.
Does an SRT file beside my video add captions to a YouTube live stream?
No. A sidecar SRT file is not, by itself, a documented live-caption delivery method. Use it for a visible-subtitle workflow only after testing it in OBS, or prepare it for an uploaded video; selectable live captions need a compatible encoder or supported caption software that sends data to YouTube.
Can OBS show subtitles from every video file?
You should not assume so. OBS documents subtitle controls for VLC Video, but compatibility depends on the actual file, track and software combination. Test the exact source and current setup, and use a rendered-subtitle export if you need dependable visible text and the track cannot be displayed reliably.
Will YouTube automatic captions stay on the replay?
YouTube’s current guidance says live automatic captions do not remain on the video after the stream. Check current channel and stream eligibility before relying on automatic captions, and add captions to the replay separately if viewers need them there.