For a 4K 60fps YouTube Live playlist with subtitles burned in, use OBS to play the files and compose the picture, then put rendered subtitle text or graphics above the video in the scene. A VLC subtitle-track control is not documented as a guarantee that subtitle text becomes part of the outgoing pixels, so check the composed result in preview or a test stream before relying on it.
“Burned in” means the words are visibly part of the picture, rather than a selectable caption track that viewers can turn on or off. You can make that distinction clear in your workflow: build the playlist, place the subtitle image or text over it, set the encoder and YouTube ingest targets, and inspect the result before going live.
What “burned in” means in a live scene
A subtitle track and a subtitle overlay can look similar on your computer, but they are different ways to deliver words. A caption track is separate from the video image. Where supported, viewers may be able to select or hide it. Burned-in text is rendered into the visible picture itself, so it remains there as part of the video output.
For a live playlist, the reliable editorial requirement is that the outgoing composition visibly contains the subtitles at the right times. This can be done by preparing video that already has text rendered into its picture, or by composing a rendered text or graphic source above the video in OBS. OBS documents scene sources and their order: sources higher in the list appear above sources lower in it. Treat using that layer order for subtitles as a composition workflow, not a claim that OBS will automatically convert every subtitle file into an overlay.
OBS’s VLC Video source offers subtitle-track controls for media that has a usable subtitle track. Those controls are worth testing if you want to use them, but the official OBS guidance reviewed for this workflow does not explicitly say that enabling a VLC subtitle track permanently rasterises subtitles into outgoing pixels. Do not treat a track being selected, or text appearing in one preview, as proof that the final broadcast includes it in the way you intend. Check the OBS Sources Guide and Media Sources guide for the documented controls, then verify the actual composite.
YouTube also supports live caption workflows, including embedded 608/708 captions and captions sent through supported software. Those are caption-delivery features, not a substitute for subtitles that must always remain visible in the picture. YouTube’s live caption requirements describe the supported routes. In its embedded 608/708 workflow, YouTube says it currently supports one caption track, although the standard supports more. That limit concerns that caption workflow, not the number of visual text elements you can compose into an OBS scene.
Prepare the playlist and subtitle assets
Start with the media, not the encoder. Put the files in their intended order and check each one from beginning to end, including its audio and any subtitle language or track you expect to use. Confirm that the source picture and frame rate make sense for the output you plan to send. Upscaling a smaller clip to a 4K canvas does not create new detail, and mixing files with different frame rates or encodings can make transitions less predictable. The official sources do not prescribe a particular playlist file format or guarantee seamless changes between differently encoded clips.
Make a short checklist for each file: opening and ending, audio level and language, subtitle timing, and any visual changes that could affect readability. This catches problems that a still image will not reveal. A devotional playlist, for example, might have a title card before the song begins; a local news loop might have a lower-third that conflicts with a subtitle overlay. The point is to find those collisions before the channel is live.
Decide how the subtitle image will be made and updated. The source material reviewed here does not specify a verified recipe for converting timed subtitle files into OBS text or graphics sources. If you use a separate tool or prepare graphics, test its output rather than assuming a particular format, timing convention, or font setup will work. Keep the visual treatment consistent, leave enough margin from the picture edges, and inspect it at the full canvas size as well as in a smaller preview. A line that looks readable on a large editing monitor may be difficult to read when viewed on a phone.
If the clips already contain permanently rendered words, inspect their edges, contrast and timing on the actual 4K canvas. If you plan a separate overlay, ensure its timing covers the appropriate clips and that it does not continue over a transition or a file with different dialogue. For a practical example of structuring an OBS loop, see the guide to running a 24/7 Hindi bhajan stream with OBS Studio. For a playlist-specific comparison, the guide to streaming a Telugu video playlist continuously is also relevant.
Add and loop files with an OBS VLC Video source
In OBS, add a VLC Video source to the scene that will carry the playlist. VLC must be installed for this source to work; OBS specifies that 64-bit OBS requires 64-bit VLC. Add the media items in playback order, then enable Loop Playlist so the sequence repeats. The OBS Media Sources guide describes the VLC playlist and looping controls. If you only need to repeat a single file, the OBS Media Source has its own single-file loop control; it is not the same as looping a multi-item playlist.
Give the source a name that will still make sense when you return to the scene later, such as “Main playlist”. Check that the source fits the canvas and that its audio is routed as intended. Start playback and let it reach a file boundary. Confirm that the next item appears in the right order, audio continues as expected, and the list eventually returns to the first item. Do not infer reliable transitions from a quick check of the first file alone.
The playlist can contain files whose dimensions, frame rates, audio tracks, or encodings differ. OBS and YouTube settings do not remove the need to test those differences. A source that fills the scene for one file might leave bars or crop the next; a change in audio level can be just as noticeable. Make a representative test that includes the files and transitions most likely to expose problems. If you are comparing approaches for an always-on channel, OBS and FFmpeg for an always-on ASMR stream covers a related choice, but for this workflow the key question is whether your chosen playback and composition behave as tested.
If you enable a VLC subtitle track, do so only when the source file contains a suitable track and you have checked the result. It may be useful as a playback control, but the documented toggle alone is not evidence that the track has been burned into the outgoing picture. Keep the visual overlay approach separate in your scene: its purpose is to put visibly rendered words above the video, using source order, and its timing needs its own inspection.
Layer rendered subtitles into the scene
Place the subtitle text or graphic source above the video source in OBS’s Sources list. OBS documents that the order controls which sources appear on top. For subtitle use, this means the overlay must be visible over the video and positioned within the canvas. This is an application of the documented layering behaviour; it is not a claim that OBS has automatically converted a timed subtitle track into a set of perfectly synchronised text sources.
Check the overlay against a moving picture, not only against a blank scene. Look for contrast over light and dark backgrounds, enough space around the letters, and placement that does not obscure faces, lyrics or other essential information. Keep the treatment legible in a reduced preview. If text changes during the playlist, test the changes around file boundaries and the points where timing is most likely to drift. Decide what should happen during a title card, a silent interval or a clip with no subtitles; an overlay left on screen past its intended segment can be as confusing as a missing line.
There are two practical ways to meet the visible-text requirement. You can render the subtitles into the source video before it enters OBS, which keeps the text tied to that file but means each prepared file carries its own visible lettering. Or you can keep the video and overlay as separate scene sources, which offers more control over the composition but requires you to maintain their timing together. Neither approach makes the text selectable as a caption track. Neither removes the need to watch a representative test.
Keep the choice of captions separate from the choice of visible subtitles. If your audience needs selectable captions, investigate YouTube’s documented caption options and configure the appropriate encoder workflow. If every viewer should see the same words as part of the picture, verify that the scene output actually includes those words. One can coexist with the other, but do not assume that selecting a language or subtitle track also satisfies the burned-in requirement.
Set 4K60 output and YouTube ingest settings
For a 4K60 feed, configure the encoder output to 3840×2160 at 60 frames per second, and choose a codec and protocol supported by both the encoder and YouTube’s ingest path. YouTube’s live encoder settings page lists RTMP/RTMPS and H.264, H.265/HEVC and AV1, up to 60 fps. Those are supported settings, not a promise that a particular computer can encode them or that every viewer will receive a 4K60 playback stream.
Match bitrate guidance to the codec you actually select. YouTube’s 4K60 table lists a 10 Mbps minimum and 40 Mbps maximum for AV1/HEVC, and a recommended 35 Mbps for H.264. Do not carry the H.264 recommendation over to AV1 or HEVC as if it were the same column. YouTube also recommends constant bitrate encoding and a two-second keyframe interval, and says not to exceed four seconds. Use its current encoder page when configuring a stream, since the platform’s guidance is the reference for the ingest settings.
| Setting | YouTube guidance for 4K60 | What to check |
|---|---|---|
| Output size and frame rate | 3840×2160 at 60 fps | Confirm the encoder is actually set to the intended output, not just the OBS canvas. |
| AV1 or HEVC bitrate | 10 Mbps minimum; 40 Mbps maximum | These figures apply to the AV1/HEVC columns on YouTube’s table. |
| H.264 bitrate | 35 Mbps recommended | This recommendation belongs to the H.264 column. |
| Rate control and keyframes | Constant bitrate; two-second keyframe interval recommended, no more than four seconds | Check the encoder’s actual output settings. |
| Ingest protocol | RTMP/RTMPS listed | Use a protocol supported by your encoder and the stream setup. |
The table is encoder guidance, not a network guarantee. Run an upload speed test and a representative stream test that includes the image complexity and motion in your playlist. If your connection or machine cannot sustain the target settings without instability, reduce the demand or choose a workflow that you have tested; a nominal 4K60 configuration is not useful if frames or audio are repeatedly interrupted. YouTube’s encoder setup also explains creating a live stream with an encoder, including use of the stream URL and key. Treat the key as a credential: do not put it in a visible overlay, shared screenshot or public note.
Hardware and software encoders are both possible routes, but the relevant choice depends on tested 4K60 encoding capability, codec and protocol support, and the stability of your network. YouTube identifies standalone hardware encoders as an option; that does not validate a particular model. If you are considering a 4K60 hardware encoder, check its own published capabilities against the codec and settings you intend to use, then test it with your full scene rather than buying on a resolution label alone.
Verify the composite before going live
Use the OBS preview to inspect the assembled scene, then make a short recording or test stream where possible. Confirm that the video is moving, each subtitle appears when expected, the overlay remains readable, and the words are visibly in the composition. If you are relying on a VLC subtitle track, compare what you see in OBS with the actual outgoing preview or recording: the control being enabled does not establish that the stream contains permanently rendered words.
Check more than the first frame. Watch a file transition, a subtitle change, a darker or brighter scene, and a passage with audio. Listen for silence, clipping, a level jump or audio that belongs to the wrong file. Check the canvas framing for every representative source. YouTube advises testing before starting and recommends checking representative movement and audio; its live streaming tips are useful for the broader setup and monitoring checks.
Once the encoder is connected, review the stream preview in YouTube Live Control Room before making the broadcast public. Look at the received picture and audio rather than assuming the local preview is the entire story. Confirm the incoming resolution and frame rate shown by the platform, while remembering that ingest values do not guarantee what a viewer’s device or connection will play back. If there is a mismatch, stop and correct the encoder or composition instead of treating a successful connection as proof that the full target is being delivered.
During a long-running channel, keep an eye on stream health and the audio-video result, particularly after any change to the playlist, overlay, encoder or connection. If you do not want your own computer to stay switched on for the broadcast, StreamNeo removes that specific operating burden: upload the file once, provide the YouTube stream key, and the stream runs from the cloud with monitoring and automatic restart if it drops. It is YouTube-only, and it does not remove the need to prepare the media or verify the subtitle composition.
For the stream key workflow, see how to create a reusable stream key in YouTube Studio. Keep the key private whether you use OBS on your own computer or another way of sending the stream. Re-check the channel’s ingest preview and health after changing keys or settings.
YouTube says streams under 12 hours can be automatically archived, automatically archives 1440p and 2160p streams, and warns that streams longer than 12 hours may not be captured at all. It recommends keeping a local archive backup. A continuous playlist is not the same thing as a dependable recording strategy, so make a separate plan if you need a complete copy of the programme.
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
Does enabling subtitles in VLC guarantee burned-in subtitles?
No. OBS documents subtitle-track controls for a VLC Video source, but the reviewed documentation does not explicitly state that enabling the track burns its text into outgoing pixels. If the words must always appear in the picture, use rendered text or graphics in the composition, or render them into the video, and inspect the actual output.
Can viewers turn off subtitles that are burned into the picture?
Not as a separate caption track: burned-in text is part of the visible image. Viewers can only avoid seeing it by changing or hiding the video itself. Selectable captions are a separate delivery route and need their own supported setup.
Does setting OBS to 4K60 guarantee YouTube viewers get 4K60?
No. The setting describes the encoder output target, not a guarantee of ingest stability, processing, availability or playback quality for each viewer. Check the received stream in Live Control Room and monitor stream health during the broadcast.
Should I use H.264, HEVC or AV1?
Choose a codec supported by both your encoder and YouTube ingest, and use the bitrate guidance for that codec’s column. YouTube lists 35 Mbps recommended for H.264 at 4K60 and a 10–40 Mbps range for AV1/HEVC; test the chosen configuration with your actual computer and network before relying on it.