If you want text to stay visible in the picture, burn it into the video or add a timed overlay in OBS. If you want viewers to switch captions on and off in the YouTube player, you need a supported live-caption feed; an ordinary subtitle file uploaded to a video does not provide that feed.
For a prerecorded loop, the simplest dependable route is usually visible text prepared in advance. Use live captions when player-toggleable captions are a requirement, and first confirm that your encoder or caption provider can deliver them to YouTube in a supported format.
Choose between visible subtitles and live captions
These approaches solve different problems. Burned-in subtitles are part of the picture: every viewer sees them, and they remain visible in a recording of the broadcast. Live closed captions are a separate track in the YouTube player, where playback controls let viewers turn them on or off when available.
| Approach | What viewers see | What you need to prepare | Main trade-off |
|---|---|---|---|
| Burned-in subtitles | Text permanently composed over the video | An edited and exported video | Predictable appearance, but a text or language change means editing the file again |
| OBS text overlay | Text composed over the broadcast while the source is live | An OBS text or graphics source and a tested timing method | Appearance is adjustable, but keeping it in sync over repeated loops takes care |
| OBS/VLC subtitle display | A supported media subtitle track shown in the programme picture | VLC installed and a media source with a supported subtitle track | This is visible text, not by itself proof of YouTube-compatible live captions |
| Live closed captions | A player-toggleable caption track | Embedded EIA 608/CEA 708 captions or supported caption software delivering captions over HTTP POSTs | Requires a verified caption output path and a timing test |
For a devotional channel looping a recorded bhajan, burned-in lyrics can be straightforward if all viewers should see the same language and styling. For a local news loop where viewers need control over captions, investigate live caption delivery instead. If you are deciding whether your whole playback chain should run on a local computer or elsewhere, the practical trade-offs in running an always-on playlist stream from an Azure VM may help; it does not change YouTube’s caption requirements.
YouTube’s live caption requirements say captions must be sent to the live stream. YouTube documents embedded 608/708 captions and supported software that sends captions through HTTP POSTs. The exact method depends on your encoder or caption provider, not simply on whether the video file contains an SRT or another subtitle file.
Burn subtitles into the prerecorded video
Burning subtitles means rendering the text into the video image before you stream it. The resulting picture contains the words as pixels; the player cannot independently hide them, select a language track, or restyle them. This is usually the least ambiguous workflow when the text should look the same in OBS, the live player, and the eventual archive.
Prepare the complete loop, including the first and last frames, before exporting. Check that each line is on screen long enough to read, that it does not cover a face, instrument, logo, or other important detail, and that it remains clear against both dark and bright scenes. A subtle solid or translucent background behind text can help when the footage changes in brightness. Check on a phone-sized screen as well as a desktop preview; text that looks generous in an editing window can become small in the player.
The main cost is inflexibility. Correcting a spelling error, changing a lyric, or offering another language means exporting a revised video. If a programme has several clips, make sure their caption styling and placement are consistent, and watch the joins as carefully as the words. A fade to black can make white text disappear unless it has an outline or background.
An ordinary YouTube video can have a subtitle track added through YouTube Studio. That is useful for viewers watching that uploaded video, but it is not a live-caption delivery method for an encoder stream. YouTube’s instructions for adding subtitles to an uploaded video describe that separate workflow. Do not assume that attaching a subtitle file to the source upload will make its captions available on a live event.
Add a timed text overlay in OBS
An OBS overlay keeps words separate from the video image while still placing them in the broadcast picture. You can use a text source for a short title or a graphics source for styled lyrics, translations, or a lower-third. Viewers still cannot toggle this text in the YouTube player: it is part of the composed programme output.
The challenge is synchronisation. A static OBS text source does not know which line of a prerecorded song is playing. You need an operator to update it at the right time, a presentation method you have tested with the clip, or another workflow that coordinates the text with playback. Do not assume that putting a sidecar SRT next to the clip will automatically advance an OBS text source in step with each loop.
OBS documents that its Media Source can loop a local video. Its VLC Video source supports a looped playlist and a subtitle-track display option, with VLC installed. The latter can show a media subtitle track in the composed picture, but that does not establish that OBS is outputting a YouTube-compatible closed-caption track. See the OBS VLC Video Source guide for the available source controls. Treat media subtitle display as visible subtitles unless you have separately verified a supported live-caption output.
For a timed overlay, test the exact scene rather than judging from a still image. Start playback from the beginning, compare each line with the spoken or sung words, then allow the clip to finish and restart. Text left on screen during a transition can be as distracting as text arriving late. If you are adding clips to an existing scene, this guide to adding a product demo to an OBS loop without restarting offers useful context about changing loop content while a stream is running; caption timing still needs its own test.
Set up the loop and YouTube encoder stream
For one local video, add an OBS Media Source, select the file, and enable Loop. OBS restarts the source when playback reaches its end. For a playlist, the VLC Video source has loop-playlist controls; it requires VLC to be installed. Choose the source that matches your material, then confirm the picture and audio both restart as intended before connecting a public event.
In YouTube Live Control Room, create or select the live stream and obtain the encoder settings. In OBS, open the streaming settings and enter the stream URL and stream key supplied by YouTube. The key functions like a password for the encoder connection, so do not show it in a screen recording or share it in a public support request. YouTube explains encoder setup and stream keys in its set up your encoder for live streaming guidance.
Start OBS and inspect the incoming preview in Live Control Room before making the event public. Check that the video is not cropped, the subtitles are legible, the audio is present, and the preview has settled into the expected scene. YouTube recommends testing ahead of time and monitoring stream quality. A practical bitrate check before going 24/7 can help you catch encoding or connection problems, but it cannot validate subtitle timing for you.
A basic OBS workflow needs no special scheduled-playback hardware. If you specifically need prerecorded media to be scheduled and sent to YouTube Live without leaving a computer running, AJA lists the HELO Plus with its optional PlayToStream functionality for that use. That is a distinct appliance-style route, not a requirement for looping a video in OBS. Compare the equipment and operating responsibility with your actual need before purchasing anything.
Configure YouTube's live caption delivery path
For viewer-toggleable captions, confirm the delivery path before building the rest of the show around it. YouTube says live captions must be sent to the stream, either embedded as EIA 608/CEA 708 or by supported caption software sending captions over HTTP POSTs. A subtitle track that OBS can display visually is not automatically either of those outputs.
If your encoder provides embedded 608/708 captions, choose the embedded 608/708 option in the stream’s Closed captions setup and configure the encoder to output the matching format. YouTube’s embedded-caption guidance currently supports one caption track. The standard may allow more, but do not plan on multiple embedded language tracks in YouTube based on the broader standard alone; check YouTube’s current live caption requirements for the current platform instructions.
If you use caption software over HTTP POSTs, follow the provider’s specific YouTube-compatible setup instructions. YouTube names supported software and directs vendors to contact it for caption-ingestion information. Do not invent an ingestion address, assume that every caption tool is compatible, or paste a regular SRT file into an encoder field that expects a live feed. Ask the provider how its output reaches YouTube and what format it sends, then verify the captions in a private or otherwise controlled test.
A prerecorded clip introduces a further question: can the chosen caption source follow the audio precisely each time the file restarts? A caption tool that listens to live speech may behave differently from a timed caption track tied to a fixed recording. Confirm that the encoder/provider supports your use case and test a full clip restart. If it cannot deliver a verified YouTube live-caption format, use visible subtitles rather than treating a media subtitle display as equivalent.
Check the first caption and the loop boundary
The start of a live stream deserves a separate check. Captions can be configured correctly yet miss the opening words if the caption feed starts late, while a title card may cover the opening scene. Begin a test from the same slate or opening frame you intend to use publicly. Watch the Live Control Room preview, then view the stream in the YouTube player and check the captions there; a preview of the composed image alone cannot confirm a toggleable caption track.
At the other end, look for leftover text after the last spoken line, an abrupt cut, or a delay as the first frame returns. A loop that is seamless visually may not be seamless in caption timing. For burned-in text, check the final caption against the cut and the opening caption against the new pass. For live captions, observe whether the track clears and resumes in step with the clip, and whether any caption provider needs to be restarted or reset at the boundary.
Keep the test representative: same file, scene, audio path, encoder settings, and caption method as the intended broadcast. YouTube recommends setting up ahead of time and monitoring stream quality while live. If the image is smooth but the stream warns of connection trouble, this guide to diagnosing a poor connection warning on a cloud-hosted YouTube stream may help separate delivery issues from subtitle problems. Record what you see at the start and restart so a later edit can be checked against the same points.
Troubleshoot timing and readability
When text is early or late, first identify which layer is wrong. Burned-in subtitles are fixed in the exported file, so correct the source timing and export again. An OBS overlay can drift because a person or presentation workflow has advanced independently of playback. A live caption feed may be out of sync because the caption source, encoder, or delivery provider has a timing issue. Changing the OBS scene does not necessarily fix the latter.
| Symptom | Likely area to inspect | Useful next check |
|---|---|---|
| Words are visible to everyone but cannot be toggled | Text is composed into the picture | This is expected for burned-in subtitles or a scene overlay; confirm whether visible text meets the need |
| No toggleable captions appear | Live caption output or YouTube setup | Verify the encoder/provider sends one of YouTube’s documented live methods and inspect the player, not only the video preview |
| Captions match at first but drift later | Timing source or overlay workflow | Compare a known line near the beginning and another near the end; test whether the timing source follows playback |
| Text is readable on a monitor but not a phone | Size, contrast, or safe placement | Test at player size and move text away from controls and important picture details |
| The first line is missing after a restart | Caption feed or overlay reset at loop boundary | Test the transition repeatedly and ask the provider or encoder vendor about restart behaviour |
For a study or ambience station, consider whether words are needed continuously. If the clip contains spoken guidance, captions may be important; if only a short title is needed, a restrained visible overlay may be clearer than leaving lyrics or labels over the whole image. Where viewers use different languages, remember that burned-in text exposes one fixed language, while the documented embedded live-caption route has a platform limit of one track. Check current YouTube guidance before choosing a workflow around language support.
If the source contains an existing subtitle track, test it in the selected OBS/VLC source and inspect the programme output. That proves only that the text appears on screen. It does not prove that YouTube receives captions as a separate track. For a toggleable result, verify the documented live delivery method with the encoder or software provider and confirm it in YouTube playback controls.
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 I upload an SRT file for a YouTube Live stream?
Do not assume that uploading a subtitle file to an ordinary YouTube video adds captions to a live stream. That upload workflow is for the video’s subtitle track. For a live caption track, send captions to YouTube using a documented live method, such as embedded 608/708 output or supported caption software using HTTP POSTs.
Will OBS show captions if I loop a video?
OBS can show visible subtitles through a supported media source, including the documented VLC Video subtitle display option when VLC is installed. That makes text part of the programme picture; it does not on its own show that OBS is delivering YouTube-toggleable captions. Test a complete loop and verify any separate caption output in the player.
Can viewers turn burned-in subtitles off?
No. Burned-in subtitles are part of the image, so every viewer sees them whenever those frames are shown. If viewer control matters, use a verified live-caption delivery path instead of relying on text composited into the video.
What should I check before making the loop public?
Check legibility and timing in the YouTube preview, then inspect the actual player experience. Watch the opening, the last caption, and the return to the first frame; for toggleable captions, confirm that the caption control and track work in playback. A test stream is more useful than assuming an uploaded subtitle file or OBS preview proves live caption delivery.