If you want to send pre-recorded video to YouTube Live, start with OBS’s built-in playback sources; a third-party plugin is only useful when it fills a control gap you actually have. For a playlist with a changing on-screen title, OBS can play the items, but it does not automatically sync each playlist change to a text file or styled overlay: you need a separate way to supply and update each title.
There are three distinct jobs: playing the video, starting or controlling OBS, and creating the live event in YouTube Studio. Keeping them separate makes it easier to choose a simple setup and to find the right place to check when something stops working.
Create a local playlist
For a single local file, OBS’s Media Source is usually the first thing to try. It supports common video formats, including MP4, MOV, MKV, AVI and WebM. Its playback properties include looping and what to show when playback ends. For one continuous devotional recording or a long ambience video, that may be all the playback control you need. The OBS Media Sources guide documents the source types and their properties.
For several files in sequence, add a VLC Video source and build the playlist in that source’s properties. OBS documents options to loop or shuffle the playlist. The source depends on VLC being installed; OBS also specifies that 64-bit OBS needs 64-bit VLC. Check this requirement before building a scene around the source, particularly if you have just installed OBS on a new computer.
A playlist is a list of media items for playback, not a broadcast schedule. If you put three bhajans in it, the VLC source can move through them, but this alone does not create a YouTube event for each item or give each item its own YouTube title. Decide whether you want one continuous live event with several files or separate live events before you set up the playlist. YouTube scheduling is handled in Studio, not by the OBS playlist.
| Need | OBS source or control | Main trade-off |
|---|---|---|
| Play one local recording | Media Source | Simple playback controls; no playlist |
| Play a sequence of local files | VLC Video source | Playlist controls, but VLC is a dependency |
| Start OBS streaming at a set time | Launch parameter or an external scheduled task | Starts OBS streaming; does not configure the YouTube event for you |
| Change scenes or sources from another tool | OBS WebSocket or a script | More control, with extra setup and security considerations |
Keep media files in a stable folder and avoid renaming or moving them after you have added them to the playlist. On a Windows PC, for example, a folder such as D:\\Live\\Playlist is easier to check than a mixture of files spread across Downloads and a removable drive. If you do reorganise files, reopen OBS and confirm that every item still loads. This simple check catches a blank source before the scheduled event.
Add an OBS Text source
A title overlay can be a text source placed above the video in the scene. In OBS, select the scene, add a Text source, and position it where it will remain legible without covering the main subject. A title might read “Morning bhajans” or “River ambience”; it does not need to imitate the YouTube event title. The text source is part of the picture sent by OBS, while the event title is managed separately in YouTube Studio.
It helps to set up the scene in layers. Put the video source at the bottom, then any background panel or logo, then the title text. This ordering keeps the text visible over the video. If you use multiple scenes, make sure the scene that will actually be live contains the intended sources; an attractive overlay in a scene that is not on air will not appear in the broadcast.
The useful distinction is between where the title is drawn and where its words come from. OBS’s text source controls the visible text and its appearance. It does not infer the current item in a VLC playlist and choose a matching title. A playlist can advance while the text remains unchanged, so listeners may see the previous item’s name unless you deliberately update the text.
This is a workable setup even if you do not use a plugin: keep the title in a text file, point the OBS Text source at that file, and change the file when the playlist item changes. The file provides the words; the source displays them. That division is particularly useful for an overnight playlist where you want a clear, modest title rather than an elaborate animated overlay.
Load title text from a file
In the OBS Text source properties, enable the option to read from a file and select a plain text file. Put a short title in that file, save it, and check the preview. For example, the file might contain Evening aarti on one line. If the text source does not show the updated wording after you edit the file, use the source’s reload control or toggle the file setting off and on, then confirm the preview before streaming.
Store the title file in a folder that remains available for the whole session. Use a straightforward filename such as current-title.txt, and avoid keeping several similarly named copies in different folders. When a source points to the wrong copy, edits appear to do nothing even though the text file itself looks correct. Confirm the full path in the source properties if an update seems stuck.
A text file is not an automation system by itself. Someone, a script, or another control process must write the next title into it, and the source must refresh its contents. That could mean a person updating the file between items, or a carefully tested local routine that writes the next title. Do not assume that adding a text file and playlist creates a link between the two.
There is a practical trade-off here. Manual editing is transparent and easy to diagnose, but it asks someone to be present at transitions. A script can reduce that work, but it introduces its own questions: how does it know which file is playing, what happens if playback skips or pauses, and does OBS refresh the text as expected? If your playlist needs dependable item-by-item titles without anyone watching it, test the whole chain rather than relying on a plugin description or a successful preview of one title.
Update the title for each item
For a short sequence, the lowest-complexity method may be to prepare a small list of titles and update the text file as each item begins. Keep the title list in the same order as the VLC playlist and make the words distinctive enough that you can see an incorrect match. Before starting, test the first transition, not just the opening title. If the playlist is shuffled, a fixed title order will no longer match the media order.
For more automation, first define the control you need. A local script could update a text file or an OBS text source, and OBS’s scripting support can be used for custom logic. Alternatively, an external control client can interact with OBS through WebSocket. These are different approaches, not a single “playlist title” feature. You still need a reliable signal for which item is current and a mapping from that item to the correct words.
OBS includes WebSocket integration by default from OBS Studio version 28 onwards, according to its Remote Control Guide. The guide describes external control of scenes and sources and recommends protecting WebSocket access with authentication. OBS names tools such as Macro Deck, Touch Portal, Streamer.bot, Deckboard, OBS Blade, Aitum, Kruiz Control and Bitfocus Companion Module as clients. That is a compatibility pointer, not a ranking, and it does not establish that any one client will automatically map VLC playlist changes to titles.
| Control method | Best fit | What you still need to handle |
|---|---|---|
| OBS launch parameter | Starting OBS streaming from a scheduled task or routine | The live event, scene choice and end behaviour still need checking |
| WebSocket client | External scene or source control | Client configuration, authentication and the logic for selecting a title |
| OBS script | Custom behaviour that does not fit a simple control action | Script setup, error handling and testing against actual playback |
OBS launch parameters include --startstreaming, which can be used with an external scheduled task or launch routine. The launch parameters documentation also explains options for selecting a scene, profile or scene collection. This can help with starting OBS at a planned time, but it is not the same as creating a YouTube Live event or proving that the right playlist title is displayed. If you use a scheduled task, OBS advises setting its working directory to the folder containing the OBS executable.
Only add a control tool when you can state what it must do. “Change the title when VLC moves to the next item” is a specific requirement; “automate the stream” is not. For a small channel, updating one text file between a few long recordings may be more manageable than writing custom logic. For a station that changes items frequently, automation may justify the extra setup, but test skipped items, restarts and playlist edits as well as the normal transition.
Style the overlay for the picture
The text should be readable against the actual footage, not only against a blank OBS canvas. Preview it over both a bright scene and a dark one. A subtle solid or semi-transparent panel behind the wording can help with contrast, and a restrained type size is easier to read on a phone than small decorative text. Keep the overlay clear of important imagery and any existing captions.
Use a title that adds information. “Now playing” followed by the item name can orient viewers; repeating the channel name in a large banner may take space without helping someone identify the current recording. If a title is long, decide whether to shorten it or wrap it to a second line. Test a long example deliberately, because a short sample can hide clipping at the edge of the canvas.
Do not mistake styling for data. A polished OBS text source still shows only the text you supplied. Likewise, a background panel, animated browser overlay or custom font does not discover the current playlist item. Treat the wording mechanism and the visual design as separate parts of the scene, and verify both in the preview and in a recording or private test where possible.
If you are comparing PC-based playback with a cloud-based approach, the cloud playout setup guide discusses the different operating model. The point is not that one is always better: a local OBS setup gives you direct control of the scene, while a cloud workflow can remove the need to leave your own computer running. Choose based on who will maintain the playlist and what happens if that person or machine is unavailable.
Consider a Browser Source alternative
A Browser Source can be useful when you need a designed overlay made with web styling, such as a title panel with precise spacing or a consistent layout across scenes. It displays a web page or local web content inside OBS. That gives you more freedom over layout than a plain text source, but it does not supply the current title on its own. The page still needs a mechanism that provides the title, such as a text file, a locally served data file, or a control process that updates the page.
Keep the data path simple enough to troubleshoot. If a local page reads a title from a file, test what happens when the file is missing, empty or changed during playback. If an external page supplies the wording, test whether it remains available during the whole stream and whether it shows stale text after a restart. A styled overlay can make a correct title easier to read; it cannot make an incorrect or missing title correct.
Browser content also adds another moving part. A page can load differently after an OBS restart, and font or layout choices can behave differently from your desktop browser. Before using it for an unattended channel, restart OBS and check that the overlay returns in the expected state. If your need is simply a single line of text, an OBS Text source backed by a file is often easier to inspect.
Keep YouTube scheduling separate
Create and schedule the event in YouTube Studio’s Live Control Room, then connect OBS as the encoder. YouTube’s encoder guide walks through creating or scheduling a stream and connecting an encoder. The event’s title and schedule belong to YouTube; the in-picture title belongs to the OBS scene. Updating one does not automatically update the other.
Before relying on an unattended start, open the intended event in the current Studio interface and check its settings. Auto-start and Auto-stop behaviour can affect whether the event starts when the encoder connects and what happens when it disconnects. OBS’s older YouTube streaming guide discusses these controls, but interfaces and event behaviour can change, so use the current YouTube Studio screen as the authority for the event you are scheduling.
An OBS automation control can start streaming, select a scene or change a source. It does not necessarily select the correct scheduled event, set its audience details, or confirm that YouTube is receiving the intended stream. Check the event and encoder connection separately. If the stream drops, OBS automation may help restart or restore a scene, but no configuration removes the need to verify that the broadcast is back and that the YouTube event is behaving as intended.
If a broadcast ends as soon as a video finishes, distinguish the source ending from the live event ending. The guide to preventing a PRISM Live Studio stream from ending when a video finishes covers that related distinction in another playback setup. For OBS, check the source’s playback-end behaviour and the YouTube event’s stop settings rather than assuming one setting controls both.
Test title changes during playback
Run a local rehearsal with the same scene, source and playlist you intend to use. Watch the preview as the first item begins, then observe the transition to the next item. Confirm that the new image and audio appear as expected and that the text changes only when you update its supplying file or control. This is the test that reveals the key limitation: playlist movement and title movement are separate unless you have deliberately connected them.
A useful preflight is to check one ordinary transition and one exception. Pause or skip an item and see whether your title process still identifies the right recording. Restart OBS and confirm that the playlist starts where you expect and the title file is still loaded. If you use a script or WebSocket client, check authentication and confirm that it controls only the intended scene or source. Keep a person available to observe the first live start if the channel matters to viewers that evening.
Check audio independently of the picture. A source can display video and title correctly while its audio is muted, routed unexpectedly or absent from the live mix. The YouTube stream audio troubleshooting guide is about a different service, but its diagnostic distinction between source audio and stream output is useful when isolating where sound disappears.
For a channel that runs overnight, consider what a local-computer workflow asks of you: OBS, the media files and any title-updating process must all remain available. If your computer sleeps, loses power or restarts, the local workflow may stop or need intervention. The guide to keeping a sleep-music stream playing when OBS restarts addresses a related recovery problem. Whatever approach you choose, test restart behaviour before you depend on it, and do not treat a successful daytime preview as proof of unattended reliability.
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 OBS need a plugin to play prerecorded YouTube Live video?
No. Media Source can play a single local video, and VLC Video can handle a playlist when VLC is installed. Add a plugin, script or control client only when you need a specific action that the built-in sources and controls do not provide.
Will a VLC playlist update my OBS title automatically?
No. OBS does not automatically synchronise playlist changes with a text file or title overlay. A person, script or other control mechanism must supply the next title, and you should test how it behaves when playback is paused, skipped or restarted.
Does a Browser Source know which playlist item is playing?
Not by itself. Browser Source can display a carefully styled page, but the page still needs a title-supplying mechanism such as a file or control process. Verify the source of the text as well as the appearance of the overlay.
Does starting OBS automatically schedule the YouTube event?
No. OBS launch controls can start streaming or select a scene, while the event is created and scheduled in YouTube Studio. Check the intended event, encoder connection and current Auto-start and Auto-stop settings in Studio before relying on an unattended start.