To stream a playlist of videos from a Linux desktop to YouTube Live, add the local media files to OBS Studio’s VLC Video source, then send OBS’s output to a YouTube event using its stream URL and key. This is a playlist of files played by OBS; a YouTube playlist URL does not become an OBS encoder input through this setup.
The VLC Video source depends on VLC being installed, and the files must be accessible on the computer running OBS. YouTube handles the event and its live audience; OBS handles the playback and encoder connection. Test the exact files and audio before scheduling viewers to join.
Check YouTube Live access before setting up OBS
First check that your channel can go live. YouTube says a channel must be verified and must not have a live-streaming restriction in the previous 90 days. If live streaming has not been enabled before, activation can take up to 24 hours, so do not leave this until the day of a planned broadcast. See YouTube’s encoder setup instructions for the current steps and requirements.
In YouTube Studio, open the Live Control Room and either create a stream or schedule one. Scheduling lets you prepare the event details in advance and promote it; people may be able to set reminders for a scheduled stream. A start-now stream is simpler if you are testing privately or do not need to advertise a start time. In either case, set the title, visibility and other event details in Studio rather than expecting OBS to manage the YouTube page.
Before choosing public visibility, consider the rights to every video and audio track in the playlist. A video being publicly viewable does not mean you can rebroadcast it. YouTube can terminate live streams for copyright or Community Guidelines issues, so use material you own or have permission to broadcast, including music embedded in a video. If a stream is stopped, check Studio for notices or strikes rather than assuming the encoder connection is at fault.
Install OBS and VLC on Linux
Install OBS using the OBS Project’s instructions for your Linux distribution. Distribution packages and installation procedures can differ, so follow the project’s current Linux installation guide rather than copying commands intended for another release. Install VLC as well. OBS’s media source documentation describes VLC Video as a multi-file playlist source and notes that VLC is required for it.
A common reason for not seeing VLC Video in OBS is that VLC is absent or not compatible with the OBS installation. The OBS documentation cautions that 64-bit OBS needs 64-bit VLC. If you installed OBS through a particular package format, check that VLC is available to that installation; having a VLC player application somewhere on the system is not by itself proof that OBS can use the needed libraries.
Open OBS after installing both applications. Create a scene for the broadcast, or select the scene you intend to use. A scene is the layout sent to the stream, so it can contain the playlist source alone or include additional items such as a logo or a text label. Keep the first test simple: one playlist source makes it easier to establish whether video, audio and the YouTube connection all work before adding overlays.
This workflow needs local media files, OBS, VLC, an internet connection and a YouTube account with live access. It does not require a camera or capture card when the content is already in files. If your aim is a continuous channel but you do not want to leave a Linux desktop running, a cloud-based workflow such as StreamNeo removes the need to keep this computer on to carry the broadcast; it still requires that your content and YouTube event are ready.
Add a VLC Video source
In the selected OBS scene, use the Sources panel to add a VLC Video source. If the option is missing, stop here and check the VLC installation and architecture match before trying to compensate with a different source. A Media Source is useful for a single file, but VLC Video is the documented OBS choice when you need multiple media items in a playlist.
Give the source a clear name, such as “Main playlist”, so it is easy to identify later. Add the files in the order you want them to play. You can change their order in the source’s playlist controls; do not assume the file manager’s sort order is the broadcast order. If you plan to add or remove files later, reopen the source properties and verify the full sequence rather than relying on a remembered arrangement.
Size and position the source in the scene. If the video does not fill the canvas, decide whether to preserve its original proportions with empty margins or crop it to fit. Cropping can remove important material near the edges; stretching can distort faces, text or artwork. Check the result in the OBS preview at the same canvas shape you intend to send to YouTube.
Build and test a local media playlist
Add local files using paths the Linux user account running OBS can read. Files on an external drive or mounted network location may be available during setup and missing after a reboot or disconnection. For a dependable broadcast, keep the media in a stable local location, check that the mount is present, and avoid moving or renaming files after you add them to the source.
Use the source’s controls to choose whether the list loops or shuffles. For a fixed sequence such as a set of devotional recordings or a news bulletin followed by a public notice, leave shuffle off and verify the ordering. For a collection intended to vary, shuffle may suit better. The OBS documentation lists loop as on and shuffle as off by default; inspect the actual properties in your installed version instead of relying on defaults.
Visibility behaviour matters when a source is hidden and shown again. Depending on the source settings, playback can stop and restart, pause and resume, or continue while hidden. That can affect a scene transition or an operator switching to a holding slide. Test the intended behaviour before the broadcast, especially if the playlist should continue beneath another scene.
Play the complete sequence once in OBS before going live. Check that each file opens, appears in the expected order, and has audible sound at a consistent level. File extensions alone do not prove that the installed media components can decode a particular file. The official guidance does not promise support for every Linux distribution, codec, online playlist or protected media source, so test the exact material rather than assuming compatibility.
A local playlist can be a simple way to run a repeating selection, but it is not a substitute for a maintained schedule. If a file is replaced, update the source and repeat the test. For a terminal-based alternative that joins files before streaming, the FFmpeg concat playlist approach has different setup and operational trade-offs. OBS’s VLC Video route keeps playlist playback in the scene, but it still depends on the desktop remaining awake and connected.
Configure the YouTube encoder connection
In YouTube Studio, open the event in the Live Control Room and find the encoder connection details. YouTube provides a stream URL and stream key for the event. In OBS, open Settings, then Stream. Select YouTube if it is available as a service and enter the key in the stream key field; if the connection setup calls for manual server details, use the stream URL shown for that event. The precise labels can vary by OBS version, so use the event’s current values rather than a saved key from a different broadcast.
Treat the stream key like a password. Someone who has it may be able to send a signal to your event. Do not put it in a public document, screenshot or chat. If you think it has been exposed, use YouTube Studio’s reset option and replace the stored key in OBS. YouTube explains the event setup and key workflow in its live stream encoder guide.
For ordinary encoder streaming, YouTube recommends RTMPS. In OBS, choose the appropriate YouTube service or ingest option shown for your setup, then check the protocol and server details against YouTube’s current encoder settings guidance. You do not need to switch to HLS for this local playlist workflow; HLS has different ingestion requirements and is not the routine path described here.
Video resolution, frame rate and bitrate should be chosen together and against your actual upload capacity. YouTube publishes bitrate guidance by resolution and frame rate, rather than one setting that suits every connection. Use its current table, leave headroom for other network use, and test from the same connection you will use during the event. A setting that appears to work in a short local preview can still produce dropped frames or stream-health warnings when the upload link is busy.
Preview, start and end the stream carefully
Before an important broadcast, prepare the encoder well in advance. YouTube advises setting up the encoder at least two hours before a scheduled stream and starting it at least 15 minutes before the event. These are YouTube’s published recommendations, not guarantees that a particular connection will be ready. Use the time to confirm the OBS preview appears in the Live Control Room, the event has the right visibility, and video and sound are both present.
For a scheduled event, starting OBS sends the encoder signal but does not necessarily make the event public. Wait for the preview in YouTube Studio, check stream health, and use the Go live control in the Live Control Room when you are ready. This distinction prevents the common mistake of assuming that pressing Start Streaming in OBS alone has started the scheduled YouTube event. For a private or unlisted test, confirm the event’s visibility and who can access it before sharing a link.
Watch representative movement and audio, not only a static opening frame. Make sure the playlist is advancing, sound is reaching the stream, and no source has been muted in the OBS mixer. YouTube recommends testing and monitoring stream health; continue checking the Live Control Room during the broadcast if you can. A viewer-side check from a separate device or account can also reveal issues that are not obvious in the OBS preview.
When finishing, stop the encoder output in OBS and end the event in Studio as appropriate. Then verify the event status and replay in YouTube Studio. YouTube says streams under 12 hours are automatically archived, but check the resulting archive rather than assuming the recording is complete or visible as intended. If the stream is part of a recurring schedule, update the next event separately; an archived replay is not itself a new live event.
For other causes of a stream dropping or ending, the unexpected live stream troubleshooting guide can help distinguish an encoder or network interruption from a YouTube notice. For long-running channels, keep the scope of a desktop playlist in mind: a power failure, sleep setting, software update or network outage can stop the source even if the playlist itself is correct.
Troubleshoot missing media or playback
If VLC Video is absent from the source list, confirm VLC is installed and that its architecture matches OBS. Restart OBS after installing VLC so it can detect the available components. If you installed OBS in a sandboxed package, check its distribution-specific documentation for media access rather than assuming the system VLC install is visible inside it.
If the source exists but shows a blank frame, test one file at a time and verify the path from the account that runs OBS. A file may open in a different desktop player yet fail through the source because the media components available to OBS differ. Check file permissions, removable-drive mounts and filenames. Avoid moving the files once the playlist is configured; if you must move them, edit the source and play them through again.
If video works but audio does not, inspect the source’s audio routing and the OBS mixer. Confirm the meter moves during playback, the relevant output is not muted, and the scene is sending that audio to the stream. Then listen to the YouTube preview or an unlisted test on another device. Local monitoring alone does not prove that the stream includes the same audio.
If the playlist order or transitions are wrong, inspect the source properties and test loop, shuffle and hidden-source behaviour. A shuffle setting can make a sequence appear inconsistent; a hidden source may pause or continue depending on its configuration. If playback stops at a particular file, remove and test that file separately, then check the codec and file integrity before changing YouTube encoder settings.
If OBS appears to send video but YouTube has no preview, check that the correct event is open and that the URL and key belong to that event. Confirm network connectivity and OBS’s stream status, then read the Live Control Room’s stream-health messages. Do not publish the key while asking for help. For recurring OBS overload or frame-drop symptoms, see the OBS encoder overload diagnosis, which addresses a different class of problem from missing playlist files.
Choose the workflow that fits the job
The choice between OBS Media Source and VLC Video is mainly about the media arrangement. Media Source handles a single file and basic looping; VLC Video supports a list of files with playlist order, loop and shuffle controls, but requires VLC. The YouTube event choice is separate: scheduling is useful when you want advance promotion, while creating a stream in the Stream tab suits a broadcast you are preparing to start without advance notice.
| Choice | Useful when | What to check |
|---|---|---|
| OBS Media Source | You are playing one file or looping it | Confirm the file path and loop behaviour |
| OBS VLC Video | You need several local files in a defined playlist | Install compatible VLC and test order, audio and visibility behaviour |
| Scheduled YouTube event | You want to share an event page ahead of time | Start the encoder early, wait for preview, then use Go live in Studio |
| Start-now YouTube event | You are testing or do not need advance promotion | Confirm visibility and the correct event before sharing it |
This setup is for sending locally available media from OBS to YouTube. It is not an instruction for importing a YouTube-hosted playlist, and it does not establish permission to rebroadcast a video found online. If you want a sequence of episodes with a different tooling approach, compare that workflow with the multiple-file YouTube stream setup guide; choose based on how you need to manage playback and the event, not on the word “playlist” alone.
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 OBS stream a YouTube playlist URL as its video source?
Not through the VLC Video playlist workflow described here. VLC Video plays media items available to OBS as local files; it does not convert a YouTube playlist URL into an encoder input. Add files you can access and have rights to broadcast, then connect OBS to the YouTube event separately.
Why is VLC Video missing in OBS on Linux?
The VLC Video source requires VLC, and OBS’s documentation cautions that 64-bit OBS needs 64-bit VLC. Install a compatible version, restart OBS and check any packaging-specific media access requirements. If the source remains unavailable, consult the OBS instructions for your Linux distribution and installation method.
Does starting OBS make a scheduled YouTube stream public?
Not necessarily. OBS sends the encoder feed, and YouTube Studio may show a preview before the scheduled event is live. Check the preview and event details, then use the Live Control Room’s Go live control when you intend to begin.
Can I leave a Linux desktop running this playlist all day?
You can use OBS for a long-running broadcast, but the desktop, power, network and media paths all need to remain available. Disable sleep only if appropriate for the machine, keep the files in stable locations, and monitor playback and stream health. Test the full arrangement before depending on it unattended.