To loop a playlist of local videos in mixed formats on YouTube Live, install OBS Studio and compatible VLC, add an OBS VLC Video source, and enable playlist looping. OBS plays and composes your files locally; its streaming encoder then sends a separate live output to YouTube.
That distinction matters: a file extension does not determine the codec or ingest protocol YouTube receives. VLC support also depends on your actual software and media files, so test the whole playlist before relying on it for a scheduled or overnight broadcast.
Install OBS and compatible VLC
Install OBS Studio and VLC before building the scene. OBS documents the VLC Video source as requiring VLC to be installed; if you use 64-bit OBS, install 64-bit VLC as well. Matching the architecture is a prerequisite for OBS to make that source available, not a guarantee that every file will decode correctly.
Download each application from its official source and check its installer options rather than assuming VLC is already present because another media player works. If you have an existing OBS installation, note whether it is 64-bit before choosing VLC. Restart OBS after installing VLC if the source does not appear in the source menu.
Use versions supported by your operating system, and avoid changing software immediately before a planned long stream unless you have time to rehearse again. A successful installation only establishes that OBS can access the VLC-based source; it does not test your clips, audio, network, or YouTube connection.
The OBS media sources guide explains the VLC Video source and its prerequisites. For a continuously running programme, it is also worth reviewing a practical always-on playlist workflow: a playlist that works during a short test still needs deliberate checks for longer operation.
Create a scene and add a VLC Video source
In OBS, create a scene for the programme you intend to send to YouTube. A scene is the composition OBS outputs: it can contain your playlist source and, if needed, other elements such as a logo, text, or a background. For a simple loop, keep the scene uncluttered so that a playback fault is easier to isolate.
In the Sources panel, add VLC Video. Give it a clear name such as “Main playlist”, especially if the scene will later contain a microphone, separate graphics, or other media. The VLC Video source is the OBS feature intended for a playlist; an individual Media Source is a different source with controls for one file.
Add the local video files to the source’s playlist in the order you want them to play. Confirm that OBS is pointing to the intended files, not copies from a temporary folder or removable drive that may be disconnected. If the project is moved to another computer, file paths may need to be updated.
Fit the source to the canvas and inspect the framing. Videos with different aspect ratios may leave empty space or crop differently, depending on how you transform the source. Decide whether to preserve the full picture with a background, crop to fill, or use another layout; check titles, subtitles, and important details at the edges before settling on a choice.
Do not add more sources than the scene needs. If you layer graphics above the VLC source, verify that they do not cover subtitles or key content. Keep a note of which scene is the live programme, so that you do not accidentally start streaming a blank or test scene.
Build and loop the playlist
Open the VLC Video source properties and add the clips in the desired sequence. OBS provides playlist controls including Loop Playlist and Shuffle Playlist. The documented defaults are looping on and shuffle off, but inspect the actual settings rather than relying on defaults, especially if you have inherited an old scene or copied a configuration.
For a predictable channel, leave shuffle off and arrange clips deliberately. That is useful for a devotional sequence, a study programme with a planned order, or a local information loop that should return to the beginning in a known way. If variety is more important than sequence, shuffle is available, but first consider whether viewers expect items in a particular order.
Looping means that the source starts over after it reaches the end of its playlist. It does not mean YouTube has taken a list of uploaded videos and will independently repeat them as a live broadcast. YouTube receives the single programme OBS is sending. The playlist and its looping behaviour are controlled at the playback end of your setup.
The separate guide to running a recorded playlist on YouTube Live may help if your content is primarily spoken audio or a podcast. The same basic separation applies: prepare the playback in your software, then check the resulting programme rather than assuming the platform will organise the files for you.
Use descriptive filenames and a stable folder structure. If a clip fails, a filename that identifies its subject makes it easier to find and replace than a folder full of files called “final” or “new version”. Keep an unchanged copy of the source media elsewhere before converting or editing anything for compatibility.
Separate source formats from YouTube output
Your local files are inputs to OBS. OBS and VLC decode those files, arrange them in the scene, and produce a composed programme. The outgoing stream is then encoded according to OBS’s streaming settings. YouTube receives that encoded live output, not each playlist file as a separate upload.
This is why “my videos are MP4” does not answer what codec YouTube will receive. A container or filename extension describes the local media file, while the encoder configuration governs the live video and audio output. RTMPS or HLS, in turn, describes an ingest route or protocol, not the format of every item in your source playlist.
OBS’s documentation lists formats for its Media Source feature, including MP4, TS, MOV, FLV, MKV, AVI, GIF, and WebM for video, and MP3, AAC, OGG, and WAV for audio. That list is for Media Source, which is documented for an individual media file; it is not an exhaustive VLC Video compatibility matrix. OBS describes VLC Video as using VLC libraries for extended media support, but the documentation does not promise that every file in every mixed playlist will play.
Actual playback may depend on the file’s codecs, its integrity, and the installed OBS and VLC versions. A file can open in one desktop player but still fail in a particular OBS setup. Test the actual clips in the source you plan to use; do not treat a familiar extension as proof of compatibility.
If you find a problem, isolate the clip and check whether it plays with sound and picture in OBS before altering the entire collection. A conversion can sometimes make a troublesome input more consistent, but conversion takes time and may change quality or audio behaviour. Keep the original and test the converted file in the complete playlist before replacing anything in a scheduled programme.
Configure YouTube encoder delivery
Once the scene plays locally, configure OBS to deliver it to YouTube Live. Follow the current YouTube encoder setup guidance for connecting the broadcast and setting up the encoder. YouTube recommends RTMPS for live ingestion; use that standard route unless a specific workflow calls for another documented option.
Choose an encoder available in your OBS installation and supported by your computer. YouTube’s published live guidance lists H.264, H.265 (HEVC), and AV1 video support, and AAC or MP3 audio. Availability in OBS depends on the installed version and hardware, so use only choices you can select and test in your own setup. Do not confuse a codec listed by YouTube with a guarantee that every computer can encode it reliably.
YouTube’s guidance recommends constant bitrate encoding, a two-second keyframe interval, and a keyframe interval not exceeding four seconds. It also documents frame rates up to 60 fps. Treat these as output guidance, not a promise of smooth playback: the encoder, content, computer, and connection all affect what reaches the platform. Check YouTube’s current official page before settling on settings, because published guidance can change.
For most creators, RTMPS is the simpler starting point. YouTube also documents HLS ingestion, which can be useful for particular HDR or codec requirements, but it has higher latency and a more involved segment-based setup. YouTube’s HLS setup instructions and HLS API guide describe requirements such as TS segments and a rolling playlist with no more than five outstanding segments. Unless your encoder workflow calls for HLS, do not add that complexity merely because your local playlist contains mixed formats.
Keep the three decisions separate when troubleshooting: whether OBS can read a source file, which video and audio encoders OBS uses for the programme, and which ingest protocol carries that programme to YouTube. Changing a local file extension is not a substitute for configuring output settings, and changing the ingest route will not repair a broken source file.
Preview and start the live stream
Before a public broadcast, play the playlist in OBS and watch the preview. Check the first clip, several transitions between clips, and the point where the final item returns to the first. A playlist that plays at the beginning but fails on its last file is not ready for an unattended run.
Listen with headphones and watch the audio meters. Check that each clip has audible sound where expected, that no item is unexpectedly silent, and that the loudness does not jump sharply between sources. A silent or unusually quiet item can be easy to miss when several videos are involved; the silent-file checking guide offers a focused way to think about that failure mode.
Also inspect aspect ratio, black bars, cut points, subtitles, and any overlays. VLC playlist playback does not promise seamless transitions, so decide whether a brief gap or cut at a boundary is acceptable for your programme. If it is not, adjust the material or scene and rehearse again rather than assuming the source will blend clips smoothly.
Connect OBS to the YouTube Live setup you intend to use and check the YouTube preview and stream-health indicators before making the broadcast public. If your workflow permits, rehearse as an unlisted or private stream first. That gives you an opportunity to catch framing, sound, or encoder warnings without treating a local preview as proof of the complete delivery path.
A local computer running OBS still needs to stay on and connected for the broadcast to continue. If keeping your own computer off is the specific problem you are trying to solve after preparing the video and channel, StreamNeo can run an uploaded video as a YouTube live stream without leaving your personal machine running. It is YouTube-only, so it is not a route for sending the same programme to other streaming platforms.
Troubleshoot playlist playback
When a clip fails, first determine whether the problem is local playback or live delivery. If the OBS preview itself is wrong, investigate the source file, VLC installation, source properties, or scene layout. If the OBS preview looks right but YouTube reports a problem, look instead at the encoder settings, connection, stream setup, and YouTube’s current health indicators.
If VLC Video is missing, check that VLC is installed and that its architecture matches OBS. In particular, OBS’s documentation says 64-bit OBS requires 64-bit VLC. Reopen OBS after installation and check the source menu again. If the source is present but no clip plays, test one file at a time before restoring the full playlist.
If one item shows a black picture, missing sound, or stops early, check that the file is accessible and plays through from start to finish in the intended source. A partially copied or damaged file can fail even if its name and extension look correct. If you replace or convert it, test the new copy, then test its neighbours and the playlist wrap; a fix for one clip can reveal a separate issue at a boundary.
If picture and sound work in OBS but the YouTube output is unsuitable, review OBS’s streaming output configuration and the current YouTube recommendations. Keep notes of the settings you changed so you can undo a change that makes matters worse. Do not try to fix a mismatch in outgoing codec by renaming a source file; the file is an input, while the encoder produces the live output.
For a channel expected to run for long periods, rehearse the complete scene and delivery path for a meaningful period before relying on it. No preview can guarantee uninterrupted operation for a particular computer, network, playlist, or duration. Have a way to notice a dropped broadcast and a practical plan for restarting it or communicating a break to viewers.
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 mix MP4, MOV, MKV, and other files in one VLC playlist?
You can add local files to a VLC Video playlist, but mixed extensions do not guarantee compatibility. Playback depends on the actual media, codecs, and installed OBS and VLC versions, so test every entry in your own scene before going live.
Does the file format decide what YouTube receives?
No. OBS reads and composes the local files, then its streaming encoder creates the outgoing video and audio. Configure that output separately from the playlist; the source files do not determine the live ingest protocol.
Does YouTube Live loop a playlist of uploaded videos for me?
This workflow loops a local playlist in OBS, not a native YouTube Live playlist. YouTube receives the programme OBS sends, so keep the playback device or chosen playback service operating and verify the loop at its wrap point.
Should I use RTMPS or HLS?
Start with RTMPS for the usual YouTube encoder workflow, which YouTube recommends. Consider HLS only when your encoder or a specific codec or HDR requirement calls for it; it involves higher latency and additional segment and playlist requirements.