For a 24/7 YouTube playlist stream in OBS Studio on Linux, use VLC Video Source for a list of local files and keep Loop Playlist enabled. VLC must be installed in an architecture that matches OBS, and you should test every file and scene transition before relying on the stream.
A playlist source behaves differently from a single-file Media Source, especially when you hide a scene. The source’s visibility behaviour determines whether playback continues or restarts when you switch away and back, so the right choice depends on whether you want uninterrupted sequence or a fresh start each time.
Choose VLC Video Source for a playlist
In OBS, VLC Video Source is the relevant source type when you want to play a list of local media files in sequence. The OBS media sources guide describes VLC Video Source as similar to Media Source, with playlist support and additional playback support through VLC libraries. It appears only when OBS can find a compatible VLC installation; it is not available regardless of what is installed.
A playlist is useful when you have several bhajans, recorded lessons, news segments or ambience clips that should run one after another. Add the files to the source’s playlist rather than creating a separate scene for each file. This keeps the sequence in one source and makes the playlist controls the place to manage order and looping.
The extra playback support is not a promise that every file will work. A file’s container, codec and audio encoding must be supported by the playback stack installed on your Linux system. A file that plays on another computer may fail here, show a black frame, or play without sound. Test the exact files you plan to broadcast, not a sample with a similar extension.
If you are setting up a music or devotional channel from a local computer, the wider workflow in our guide to an always-on YouTube music stream from a PC in India can help you think through the operating and connection requirements around OBS. This page concentrates on the Linux-specific source and scene behaviour.
Install VLC with matching architecture
OBS needs an installed VLC playback library for VLC Video Source to be offered. Install VLC using the package method appropriate to your Linux distribution, then restart OBS if it was already open. If the source is still missing, check that the VLC installation and OBS use the same architecture. For example, 64-bit OBS needs 64-bit VLC, rather than a 32-bit installation that the application cannot use.
Package names and installation steps vary across distributions and packaging formats, so use the distribution’s current documentation for the exact command or package. Avoid copying a package command intended for a different Linux release. If OBS was installed as a sandboxed package, such as a format with restricted access to system libraries, its ability to see the host VLC installation may differ. Check the packaging documentation rather than assuming that installing VLC alone resolves that case.
After installation, open OBS and add a VLC Video Source to a test scene. If it does not appear in the source menu, close and reopen OBS, then verify the architecture and how both applications were installed. If it appears but cannot load a file, distinguish that from the missing-source issue: the plugin is present, but the file or its playback dependencies may still be unsupported.
Do not judge readiness from a single successful MP4 if your real playlist contains different formats. For a channel that alternates recorded lectures and music videos, test each format and listen for its audio. A dependable playlist is the one whose actual contents play correctly under the same OBS and VLC installation you intend to leave running.
Add playlist files and enable Loop Playlist
Create the VLC Video Source in the scene that should carry the programme. Open its properties, add the media files to the playlist, and arrange them in the order you want viewers to receive them. OBS’s interface may show an add control and a list where entries can be reordered or removed; use the property window to confirm that every intended file is present.
Enable Loop Playlist if the sequence should begin again when it reaches the last item. Without looping, the playlist reaches its end and stops rather than continuing indefinitely. Looping only governs repetition of that playlist; it does not ensure OBS remains connected to YouTube, keep a Linux computer powered on, or recover every possible playback or network failure.
Think through file paths before starting. If you move a media file, rename a directory, or mount a removable drive differently after configuring the source, OBS may no longer find it. Keep the playlist media in a stable location available to the user account that runs OBS. If you need to relocate the files, reopen the source properties and verify the paths before going live.
A playlist can contain material with different aspect ratios, audio levels and lengths. The source may play all the files, but the presentation can still vary: a vertical clip may leave empty space in a landscape canvas, or a quiet recording may sound much softer than the next item. Review the sequence visually and by ear so you can decide whether to prepare consistent media beforehand or accept the changes between clips.
For a channel built around one type of programme, such as a continuous classes playlist, the online classes playlist guide offers a useful companion perspective on organising the content itself. Whatever the subject, test the order and the transition at the end of the sequence instead of treating the Loop Playlist checkbox as the whole test.
Set source visibility behaviour
OBS sources can be visible in one scene and hidden when you move to another. VLC Video Source has a Visibility Behaviour setting that determines what happens to playback while the source is not visible. OBS documents the default as stopping playback when hidden and restarting when visible. Confirm the setting in the source’s properties, because the default may not fit a multi-scene layout.
If you want the playlist to keep advancing while viewers see a different scene, select the behaviour that continues playback when the source is not visible, where offered by your OBS version. When you return to the playlist scene, it will have advanced rather than restarting at the beginning. This is useful for a channel that briefly switches to a holding slide or announcement while preserving the programme’s place.
If you want each visit to the scene to begin the playlist again, stopping and restarting on visibility can be appropriate. It is less suitable when you expect to switch away for a short interruption and return to the point where viewers left off. The trade-off is continuity versus a predictable restart, not simply a performance setting.
Test this setting with the actual scene transitions you plan to use. Start the playlist, note the clip and approximate playback position, switch to another scene, wait long enough to see whether it advances, and switch back. Check both the picture and audio: a source that continues while hidden may still be audible even though its scene is not shown, depending on the source and audio configuration. Make sure you do not unintentionally mix hidden programme audio with a separate scene’s sound.
A hidden source can also behave differently from a muted source. Hiding relates to scene visibility; muting relates to audio output. If your holding scene should be silent, check the audio mixer and source settings rather than relying on the video being out of view. For background examples of how continuous video relates to other scene elements, see adding hymn lyrics to recorded videos for a 24/7 church stream.
Fit the source to the scene
Set the OBS canvas and output resolution for the presentation you intend to send, then size the VLC source within the scene. OBS provides transform commands such as Fit to Screen and Stretch to Screen. Fit preserves the media’s proportions, which can leave unused space if its shape differs from the canvas. Stretch fills the canvas but can distort the picture, so use it only when that result is acceptable.
For example, a landscape recording on a landscape canvas may fit cleanly. A portrait clip fitted into the same canvas can leave blank areas on the sides; stretching it to fill may make people or text appear unnaturally wide. You can instead use a designed background or crop the source if the composition supports it, but inspect the edges and any subtitles before going live.
Check the source in the preview at the intended output size. Look for accidental crops, black bars you did not expect, text near the edge, and changes when the playlist advances to a differently shaped file. A single transform may not make every item look identical. If the visual differences are distracting, standardise the files in advance or use separate sources and scenes where the content genuinely needs different treatment.
Use Media Source for one repeating file
If you have one video file that should repeat, the ordinary Media Source is usually the simpler fit. It has a Loop control for repeating that item. This differs from VLC Video Source: the latter provides a playlist of files, while Media Source is suited to an individual file and its playback options.
OBS lists common video formats such as MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM, and audio formats such as MP3, AAC, OGG and WAV in its media-source documentation. Those format names do not guarantee that every file with that extension will play on your particular Linux system. Codec support, installed playback components and the way a file was encoded all matter, so test the actual file and confirm both picture and sound.
For a single long devotional visual or a fixed ambience loop, Media Source can mean fewer playlist controls to manage. For a rotation of several clips, VLC Video Source avoids creating a chain of separate single-file sources just to advance through them. If you are unsure which applies, count the files that must rotate: one repeating item points to Media Source Loop; a sequence of different items points to VLC Video Source and Loop Playlist.
Configure YouTube output separately
The OBS source decides what media is played; the output settings decide how OBS sends the live programme to YouTube. For standard RTMP or RTMPS ingest, choose settings from YouTube’s current live encoder recommendations for the codec, resolution and frame rate you actually select. YouTube’s guidance recommends CBR and a 2-second keyframe interval, which should not exceed 4 seconds. For SDR, it lists Rec. 709, and recommends RTMPS for encrypted transport.
As examples from YouTube’s H.264 recommendations, 720p30 is listed at 4 Mbps and 720p60 at 8 Mbps; 1080p30 at 14 Mbps and 1080p60 at 17 Mbps; 1440p30 at 21 Mbps and 1440p60 at 34 Mbps. These are YouTube’s recommended ingestion values for those rows, not a guarantee that your Linux computer or internet connection can sustain them. Match the value to the codec and frame-rate row you have chosen, and leave upload capacity for normal variation rather than setting the stream at the maximum your connection sometimes reaches.
This matters particularly on a 24/7 channel: a setting that works during a quiet evening may be less reliable when another person starts using the same connection. Check upload capacity and test under conditions representative of normal use. YouTube transcodes incoming streams into multiple viewer formats, but that does not remove the need to send a stable, correctly configured source stream in the first place; see OBS’s explanation of YouTube transcoding.
Do not copy HLS-specific output requirements into an ordinary RTMP or RTMPS setup. YouTube documents HLS as a separate option with distinct requirements, including TS segments, a rolling playlist and HTTPS POST/PUT. It also has higher latency than standard RTMP-style ingest. Unless you deliberately choose HLS and configure an encoder for it, use the settings for the protocol you are actually sending.
Test playback, scenes and the live signal
Before depending on the setup overnight, make a short, deliberate test. Start the playlist in OBS and watch it advance through representative files. Confirm that the last item returns to the first when Loop Playlist is enabled. Listen to the transition between clips, check that each one has sound at an acceptable level, and verify that the image fits the scene rather than being cropped or stretched unexpectedly.
Then test the visibility behaviour. Switch away from the playlist scene and back, and check whether playback continued or restarted as intended. If you use a holding slide, an announcement scene or a second programme scene, test each transition and make sure hidden-source audio is not leaking into the output. A scene change can expose a problem that is invisible when you test only the playlist by itself.
Finally, confirm the stream at YouTube rather than relying only on the OBS preview. Open the Live Control Room and check that it receives the expected picture and sound, and pay attention to stream-health messages. YouTube’s encoder guidance says, “Make sure to test before you start your live stream.” Treat that as a practical step, not a formality: a green-looking local preview cannot tell you whether the upload is stable at the selected bitrate.
A looped source is not an end-to-end uptime plan. OBS can continue playing files while the stream connection has a problem, and a computer can sleep, lose power or lose network access. If you use a local machine, account for power settings, automatic updates, network interruptions and who will notice a failure. The guide to keeping a YouTube livestream running after closing an SSH session is relevant if your Linux setup is operated remotely, though it addresses a different failure point from playlist playback.
If the concern is leaving a personal computer on through the night and recovering a dropped broadcast, StreamNeo removes that particular burden by turning an uploaded video into a YouTube stream without keeping your computer running. It does not change what you need to test about content, stream configuration or the resulting picture and sound.
If you have confirmed the playlist, scene transitions, connection and YouTube signal, choose an operating approach that suits how you will maintain the channel.
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
Why is VLC Video Source missing in OBS on Linux?
OBS needs VLC installed for VLC Video Source to appear. Check that VLC is installed and that its architecture matches OBS; for 64-bit OBS, use 64-bit VLC. If both are installed but the source is still absent, check how OBS was packaged and whether it can access the VLC libraries.
Does Loop Playlist keep my YouTube stream live all night?
No. It repeats the playlist when it reaches the end, but it does not ensure that OBS stays connected, the computer remains powered, or the network continues working. Check YouTube’s stream health and plan how you will detect interruptions.
Should I use VLC Video Source or Media Source?
Use VLC Video Source when you need a sequence of files and want playlist controls such as Loop Playlist. Use Media Source with Loop for one file that repeats. In either case, test the exact media because installed playback support and file encoding affect whether it plays correctly.
Will the playlist restart when I return to its scene?
That depends on the source’s Visibility Behaviour setting. OBS documents stopping while hidden and restarting when visible as the default; choose and test the behaviour that matches whether you want the sequence to continue out of sight or begin again on return.