To stream a pre-recorded playlist with subtitles on YouTube Live, you can use OBS Studio’s VLC Video Source to play local files and show an embedded subtitle track in the picture. If viewers need captions they can switch on or off in YouTube, you must send captions through YouTube’s supported live-caption workflow as well; OBS-rendered subtitles do not automatically become that track.
The distinction matters because these are two different outputs. One is part of the video image you send to YouTube, like text burned into a picture. The other is a caption feed delivered separately to YouTube so the player can offer captions. Decide which outcome you need before building the playlist.
Choose between visible subtitles and live captions
Visible subtitles are text shown within the video frame. They can be embedded as a subtitle track in a media file and rendered by the playback software into the outgoing picture. Viewers see them wherever they watch the stream, but cannot turn that rendered text off using YouTube’s captions control. They also cannot select a language through that control based on the rendered track.
Selectable live captions are a separate delivery path. YouTube’s guidance says you need to send captions to YouTube, using an accepted method such as captions embedded in the encoder output or a supported caption-software workflow. See YouTube’s live caption requirements before choosing a method, since the available settings and supported tools can change.
| What viewers get | How it reaches YouTube | Can the viewer switch it off in the player? | What to plan |
|---|---|---|---|
| Text rendered into the video | The encoder sends a picture containing the subtitle text | No, not as a separate caption track | An embedded subtitle track and playback software that displays it |
| Selectable live captions | A supported live-caption feed is sent separately or embedded in the encoder output | Yes, through the player’s captions controls when available | A supported caption workflow configured for the live stream |
You can use both approaches, but one does not substitute for the other. For a devotional programme with a fixed Hindi translation on screen, rendered subtitles may be sufficient. If viewers need to choose captions independently, including to turn them off or select the available track, plan and test a YouTube caption feed separately.
This distinction also affects production. Rendered subtitles follow the video file and playback path. A separate feed needs timing and delivery aligned with the live broadcast, and the caption software or encoder must support the workflow you choose. Do not assume a subtitle file loaded by a media player is also being transmitted as YouTube captions.
Prepare local video and embedded subtitle tracks
For the OBS/VLC route, gather the video files you want to play and make sure the required subtitles are embedded in the media files. OBS’s documentation describes selecting an embedded subtitle track for a media source. It does not establish a general method for loading a separate SRT sidecar into a VLC playlist, so do not build your plan around an assumed sidecar workflow. Check the exact media and subtitle format with the software you intend to use.
Test each file before assembling the full playlist. Open it in a player that can select its subtitle tracks, check that the intended language is present, and confirm that text appears at the right moments. A track can exist in a file and still be the wrong language, blank, or out of sync. Also check legibility against bright and busy backgrounds; a subtitle that is readable over a dark opening title may disappear over a pale daytime scene.
Keep the playback files together in a stable local folder and use clear filenames. If the sequence is important, write it down in the intended order rather than relying on memory while adding files. For example, a small business might schedule a welcome video, product demonstration and closing information in that order, then repeat the sequence. If playlist continuity is important, review the transition between the end of one file and the start of the next; an abrupt change in audio or a black frame is part of what viewers will see.
A pre-flight check should include video, audio and text, not only whether the file opens. Listen for differences in loudness between items, check that aspect ratios are acceptable, and confirm that subtitle timing stays correct after any edits or re-encoding. If you are making a long loop, the advice in how to make a seamless loop for a 24/7 YouTube music stream can help you think through the hand-off at the playlist boundary, even though this workflow is for video with subtitles.
Add the VLC Video Source in OBS
OBS’s VLC Video Source is the documented way to play a local media playlist through OBS. OBS says VLC must be installed for this source to be available. On 64-bit systems, match VLC’s architecture to OBS’s architecture; otherwise the source may not appear or may not work as expected. Follow the current OBS media sources documentation for current labels and options.
In OBS, add a VLC Video Source to the scene you plan to broadcast. In its properties, add the local media files in the order you want them to play. Leave shuffle off if the sequence matters. Turn on Loop Playlist if the list should repeat after its final item. If you want a single run rather than a repeating channel, do not enable a loop simply because the option is available.
Arrange the source in the scene and check how it fits the canvas. If it is cropped, stretched or hidden behind another source, viewers will not see the same result you saw when opening the file by itself. Check the audio mixer as well: the source should produce the intended sound, and no other scene source should unintentionally add duplicate audio.
OBS and VLC are local playback tools, so this setup depends on the computer running OBS, the media remaining accessible, and the internet connection being able to send the broadcast. A power interruption, operating-system update, local network fault or accidental source change can stop the programme. You can read how to balance bitrate and latency for a YouTube Live stream when choosing encoder output settings, but those settings do not remove the need to keep a local encoder and connection available.
Before a long run, operate the playlist for long enough to see its order, loop behaviour, audio transitions and subtitle display across different files. Do not rely on the source properties alone as proof: preview the composed OBS scene, since overlays and cropping can cover text even when the source itself is displaying it correctly.
Enable and check the subtitle display
In the VLC Video Source properties, enable subtitles and choose the intended subtitle track. The exact track names depend on the files. If the menu lists multiple tracks, select deliberately rather than assuming the first one is the right language. OBS describes embedded-track selection, so keep this check tied to the media file being played.
Then check the subtitles in the OBS preview while the playlist plays. Look at more than the first file: a track selection that works for one item may not behave as expected for another, especially if files were prepared differently. Confirm that text is large enough on a phone-sized view, stays within the visible picture and does not clash with lower thirds or other graphics.
The stream output contains the composed image. If OBS displays the subtitle text as part of that image, it reaches YouTube as visible video content. That is useful when you need consistent, always-visible translations or lyrics, but it also means viewers cannot independently hide the text and the words may be less readable to some viewers. If you need selectable captions, use the separate delivery approach described below rather than treating the OBS subtitle checkbox as a caption setting.
A rendered subtitle may also be difficult to maintain when the playlist contains different programmes or languages. For instance, a loop combining a Hindi bhajan recording and an English announcement needs a deliberate track choice for each item. If your production needs different text per item, test how the selected track behaves across the entire playlist and decide whether one playlist is practical or whether you should split it into separate streams or sequences.
Set up YouTube Live encoder delivery
In YouTube Studio, open Go Live and create a stream, or schedule one from the Manage area. YouTube’s encoder setup guide explains the process. Copy the Live server URL and stream key into OBS’s stream settings. YouTube describes entering those values in the encoder to start streaming. Treat the stream key as a credential: do not include it in screenshots, public notes or a file shared with people who do not need it.
For a scheduled event, follow the Studio flow and wait for the stream preview before selecting Go live where that is required. Labels and options can change, so use the current Studio instructions rather than an old screenshot. A successful connection from OBS is not the same as a finished viewer test: inspect the YouTube preview for image, sound, aspect ratio and the correct playlist item before making the stream public or starting the event.
Choose encoder output settings that fit your connection and the material. A stream with detailed motion and text can expose compression problems that are less obvious in a static scene. YouTube’s recommendations and the choices available in OBS can vary with the stream configuration, so check the current official instructions and monitor the health indicators in Studio. If the stream looks unstable, reduce the demand on the connection or revise the output settings and test again rather than assuming subtitles are the cause.
A local setup gives you hands-on control of playback, but it also means the computer and upload connection must remain available. For a 24/7 stream, interruptions from sleep settings, updates, power loss or internet trouble need a plan. Some creators prefer a local encoder because they can manage scenes and playback directly; others want playback to continue without their own computer running. StreamNeo is useful when the specific problem is keeping a video broadcast running after you have shut down your computer, rather than leaving OBS open overnight.
Send live captions through a supported workflow
If the goal is selectable YouTube captions, configure live captions separately from the OBS-rendered video subtitles. YouTube documents sending captions as embedded EIA 608/CEA 708 captions in the encoder, or using its captions ingestion URL with supported caption software. Its current guidance describes one caption feed per stream entry point and one embedded caption track; check YouTube’s live caption requirements for the current details before production.
The right workflow depends on how your captions are made and what your encoder or caption software supports. If a programme has a prepared script or timed text, verify that your chosen supported tool can deliver it as live captions, in sync with the actual output. The fact that a subtitle track is present in an MP4 does not demonstrate that the encoder is packaging it as a supported caption feed. Likewise, seeing text in the picture does not prove a separate caption feed is reaching YouTube.
Set up the caption path in the live event and follow the instructions for the chosen software or encoder. Confirm that the caption output corresponds to the stream entry point you are using. YouTube’s documented feed limit matters if you were expecting multiple independent caption feeds; do not plan on separate simultaneous caption feeds for every language without checking what the current platform workflow supports.
If the method, software or file format is uncertain, test it before relying on it for a public programme. The official pages explain requirements, but they do not establish that every combination of OBS, VLC, media containers and caption tools will work together. Avoid promising viewers a selectable language until you have observed that track in the actual YouTube player during a test.
Test what viewers can see and select
Run a private or otherwise appropriate test using the same files, scene, caption method and event settings you expect to use. Watch the YouTube player, not just the OBS preview. Check the opening, a representative subtitle line, a transition between playlist items and the loop boundary. Confirm picture and sound continue, the intended text remains legible, and YouTube Studio reports a healthy incoming stream.
Test the two subtitle outcomes separately. First, watch with the player’s captions control off: text rendered into the video should still be visible. Then test the captions control with the separate live-caption workflow enabled. If the player offers a selectable caption track, turn it on and confirm that its words and timing are correct. If there is no selectable track, the OBS picture may still show subtitles, but that is not evidence that live captions were delivered.
Ask a second person to check from a typical viewing device if possible. A desktop preview can hide issues that matter on a phone, such as text sitting behind player controls, low contrast or overly small type. Check in the intended language and use a realistic viewing distance. Keep the test simple enough to repeat after changing files, OBS settings or caption configuration.
YouTube recommends testing encoder settings and monitoring stream health. Its setup documentation also says streams shorter than 12 hours are automatically archived; do not treat that statement as a promise about every archive outcome or substitute for checking current YouTube guidance. Decide how you will inspect the live watch page and any resulting archive, particularly if captions and rendered subtitles need to remain useful in both contexts.
If a test fails, isolate one layer at a time. Confirm the subtitle track in the local file, then confirm VLC playback in OBS, then inspect the YouTube stream preview, and finally verify the separate caption path in the player. This sequence helps distinguish a media-track issue from scene composition, encoder delivery or caption ingestion. For a broader planning view on how recurring broadcasts fit together, see how to build a live streaming strategy for YouTube.
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
Do OBS subtitles become selectable YouTube captions?
No. Subtitles rendered into the OBS picture are part of the video image and do not automatically become a selectable caption track. To offer live captions through YouTube’s player, send them using a supported YouTube caption workflow and test the result in the player.
Can I use a separate SRT file with an OBS VLC playlist?
The documented OBS VLC source guidance covers selecting an embedded subtitle track, not a general procedure for loading a separate SRT sidecar into its playlist. If your subtitles are separate, verify a supported method with the current OBS and media-tool documentation before depending on it. Do not assume that a sidecar is transmitted as live captions.
Does the playlist keep playing if I close OBS?
With local OBS and VLC playback, the computer running the broadcast has to remain on with the encoder and connection available. Closing OBS stops that local playback and delivery. If you need the broadcast to continue with your computer switched off, choose an operating approach designed for that requirement and test it before relying on it.
How do I know viewers can select the live captions?
Check the YouTube watch page during a test and use the player’s captions control. Confirm that a track is offered, that it can be enabled, and that its text is in sync. Seeing subtitle text in the video alone confirms only the rendered-on-picture outcome.