If your prerecorded videos have different resolutions, you can play them in sequence through an encoder such as OBS and send one live stream to YouTube. You do not need to prepare a separate quality variant for every file: the encoder produces one configured output, which YouTube processes for viewer playback.
The word “playlist” causes much of the confusion. Here it means your list of video files in OBS, not the segment playlist described in YouTube’s HLS ingestion documentation. The distinction matters because each list has a different job.
What “playlist” means here
For this workflow, a playlist is a group of prerecorded files that your encoder plays one after another. You might arrange a morning bhajan programme, a loop of nature footage, or a sequence of recorded local updates. OBS reads the files and combines their video and audio into its outgoing programme.
YouTube receives that programme as a single live feed. It does not receive each file as an independent live channel, nor does it require you to create a set of quality versions for every clip. Your encoder has a single output profile at any moment: a chosen resolution, frame rate, codec and bitrate.
This is different from adding uploaded videos to a YouTube channel playlist. A channel playlist organises videos for people to watch individually; it does not make them play as a continuous live broadcast. If your aim is to play recordings in a live stream, the files need to be played by an encoder or another playback workflow that sends a live feed.
If you are planning pauses or announcements between recordings, decide how those should appear before you build the sequence. A countdown between podcast episodes is one example of a deliberate transition rather than an abrupt cut. For a simple loop, however, a direct transition may be enough if you test it with your actual files.
Build a local file playlist in OBS
OBS’s VLC Video source can play a list of media files. In OBS, add a VLC Video source, select the files in the order you want, and configure whether they should loop or shuffle. OBS notes that VLC must be installed for this source to be available. The OBS Media Sources guide describes the source and its playlist controls.
Use paths that will remain valid for the duration of the broadcast. If files are on a removable drive, make sure it stays connected and does not enter a power-saving state. Keep a copy of the intended order somewhere outside the OBS scene as well; that makes it easier to check whether the source list matches your programme plan after an edit.
A reliable first test is deliberately small: add two representative files, one at the beginning and one later in the intended sequence. Confirm that each starts, that the source advances when expected, and that loop or shuffle behaviour matches your plan. This catches file access problems before you load a long programme into the scene.
If the source is part of an always-on setup, also consider what should happen if a file fails or the computer restarts. A local OBS playlist depends on the computer, OBS and the media files remaining available. The same practical concern comes up in reducing CPU use for an FFmpeg loop: choose a playback method that the machine can sustain, and test the actual workload rather than assuming that a long loop will behave like a short preview.
Mixed source resolutions: what changes and what does not
A playlist can contain files with different dimensions, such as a wide high-definition clip followed by a smaller older recording. That difference does not create separate YouTube quality variants. OBS renders the current source into its scene and sends the scene using the output settings you have chosen.
For example, if OBS is configured to send a 1920 by 1080 output, a smaller source has to be fitted into that canvas. Depending on the scene layout and scaling choices, it may appear with empty space around it, be cropped, or be enlarged. A larger source may be reduced to fit. The details are controlled by your scene and output configuration, not by a separate YouTube setting for each playlist item.
The output resolution therefore sets a ceiling on the detail the outgoing feed can carry, but it does not make every original file equally sharp. Enlarging a small or compressed recording cannot restore detail that is not present in the source. Conversely, choosing a very large output does not automatically improve a clip that was recorded at a much smaller size.
Inspect how each aspect ratio appears. A portrait phone video in a landscape scene may leave side bars unless you choose another layout. Cropping to fill the frame can remove important content at the edges. For devotional lyrics, news captions or a business notice, check that text remains readable and is not cut off during the switch to the next item.
Audio needs the same attention. Files may differ in loudness, channel layout or encoding even when they look similar on screen. A transition can be visually acceptable and still be unpleasant if one recording is much quieter or has a sudden peak. Listen to the join on ordinary speakers or headphones, not only by watching the preview.
Choose one outgoing encoder profile
Before connecting to YouTube, choose an output profile your computer and upload connection can sustain continuously. The relevant choices include resolution, frame rate, video codec, bitrate and audio settings. A higher output profile carries more data and can demand more from the encoder and connection; a lower one can be a sensible choice when stability matters more than preserving fine detail.
YouTube publishes recommended settings for live encoders, including bitrate guidance by resolution and frame rate. Use the row that matches the resolution and frame rate you actually intend to send, rather than treating a bitrate as universal. Its guidance also covers supported video and audio formats, constant bitrate and a recommended two-second keyframe interval. See YouTube’s encoder settings and bitrate recommendations for current details.
A profile should be selected for the programme as a whole. If your collection ranges from small archival clips to newer high-resolution recordings, a moderate output may avoid unnecessary load while still giving the sharper sources room to look good. If the most important material needs more detail, test whether the machine and connection can sustain the higher profile through a representative sequence.
| Decision | What to consider | Practical check |
|---|---|---|
| Output resolution | Desired detail, source material and connection capacity | Check the smallest and largest files in the scene |
| Frame rate | Motion in the content and the profile you can maintain | Watch movement and text at transitions |
| Bitrate | YouTube’s recommendation for the chosen resolution and frame rate | Compare the encoder setting with the matching YouTube guidance |
| Codec and audio | Encoder support and YouTube’s current accepted settings | Confirm the encoder can use the selected format reliably |
| Stability | Computer load and sustained upload capacity | Run a test long enough to expose drops or overload |
A profile that works for a short clip is not automatically a good choice for a full night. If OBS struggles, reduce the demands or simplify the scene, then test again. For a computer intended to run around the clock, power use and heat also matter; this guide to estimating the power bill for an always-on OBS stream can help you account for that operating trade-off.
Connect OBS to YouTube Live
In YouTube Studio’s Live Control Room, create or select the live stream and obtain its server URL and stream key. Enter these in OBS’s stream settings, keeping the key private. YouTube’s encoder setup instructions explain the connection process. The outgoing feed is still one stream, regardless of how many files the VLC source will play.
Start the encoder and inspect the Live Control Room preview before making the stream public or beginning a scheduled event. Check that video appears, audio is present, the correct scene is being sent and the intended first file is playing. If the preview is black or silent, fix that before you rely on the broadcast; changing a playlist order will not resolve an encoder or scene issue.
For a continuous channel, the choice of playback arrangement also affects how much you have to manage. A computer running OBS gives you direct control over scenes and transitions, but it must remain powered, connected and attended to when something needs intervention. If that is the pain you are trying to remove, StreamNeo lets you upload a video file, connect your YouTube stream key and leave your own computer switched off while the broadcast runs and is monitored for interruptions.
Whatever tool you use, check that every video and audio track is appropriate for your channel and that you have the rights needed to broadcast it. A technical test cannot establish those rights or guarantee that a platform will approve particular content. YouTube’s live-streaming guidance is the right place to review current platform requirements, and you should assess your own material before going live.
What YouTube does with the incoming video
The encoder’s configured feed is the input YouTube receives. YouTube says it automatically transcodes a live stream to create different output formats for viewers using different devices and network conditions. That means viewers may be offered playback choices derived from the live input; it does not mean the original files in your OBS playlist each need to be encoded into a set of separate variants first.
There are two stages to keep separate. OBS takes each file as it plays and places it into the single outgoing programme according to your scene and output profile. YouTube then processes that incoming programme for playback. A change of source resolution inside OBS is not a request to change YouTube’s live ingestion profile for that file.
Do not expect this process to make all files look identical. A clean high-resolution source may retain more visible detail than a soft, compressed source after both are fitted into the same output. YouTube’s processing also does not remove black bars, repair a crop you chose in OBS, restore clipped audio or make a low-quality source match a better one.
This is why consistency is mostly a preparation task. Check the fit, scale, colour and sound of the files in your encoder scene. Choose an output profile that is realistic for your connection and computer, then examine the viewer-facing result in a private or unlisted test. The YouTube live-streaming tips include recommendations to test and monitor the stream rather than assuming the preview or configuration alone proves everything is working.
HLS Media Playlists are a different kind of playlist
You may see “Media Playlist” in YouTube’s HLS documentation and assume it refers to a creator’s list of video files. It does not. In HLS delivery, a Media Playlist describes media segments that belong to a live transport stream. Those segments are part of how a stream is represented and delivered, not a queue of separate programmes that you arranged in OBS.
Google’s HLS ingestion documentation distinguishes Media Playlists from Master Playlists. It says YouTube supports Media Playlists and ignores Master Playlists for this ingestion workflow, because YouTube handles transcoding of the incoming stream for viewers. That is a protocol-level detail, not a requirement for someone using an OBS VLC source to sequence local files.
In practical terms, you do not need to edit HLS segment manifests to play your recordings one after another through OBS. You choose the files in the encoder, set its output, and send the live feed to YouTube. If you are using a specialist HLS encoder instead, follow YouTube’s current documentation for that protocol and avoid applying terminology from a creator playlist to transport manifests.
Keeping these meanings separate prevents a common detour: searching for a way to add each source file as a YouTube HLS quality stream. The local playlist controls what the encoder plays; the HLS Media Playlist is part of a delivery format; YouTube’s transcode process creates playback formats from the one incoming feed.
Test transitions and viewer playback
Run a private or unlisted test with a representative sequence before a public broadcast. Include files with the different resolutions and aspect ratios you expect to use, and let each transition occur at least once. The goal is not to prove that every possible file combination is flawless, but to identify problems in your actual programme while there is still time to adjust it.
Watch the Live Control Room preview and listen for gaps, abrupt level changes, wrong audio tracks, unexpected black frames or a source that fails to advance. Check captions, logos and text at the point where the next source replaces the previous one. If you use shuffle, repeat the test under that setting; an orderly sequence test does not validate a shuffled programme.
Then check playback as a viewer. A preview in the control room and a public viewer’s playback path are not identical checks. View the test on a typical phone or television if those are important audiences, and check that the available quality options and picture framing are acceptable. Do not assume that because one device looks good, every connection or screen will behave the same way.
Monitor stream health while the test runs. If you see dropped frames, connection warnings or encoder overload, lower the profile or simplify the scene and repeat the test. YouTube recommends testing before an event and monitoring audio and video quality. If your issue is instead that an always-on broadcast repeatedly drops offline, this diagnostic guide for a low-memory VPS stream covers a different failure mode from mixed-resolution playback.
Once the test looks and sounds acceptable, save the scene and settings you used, and retain the test notes. A later file replacement can change aspect ratio, loudness or playback behaviour without changing the nominal output profile, so test again whenever the playlist changes in a meaningful way.
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
Do all videos in an OBS playlist need the same resolution?
No. OBS can play files with different dimensions in one source playlist and render them into the configured scene and output. Check how each one is scaled or cropped, because the result will not necessarily have identical sharpness or framing.
How do I stream multiple videos with different resolutions on YouTube Live?
Add the files to an OBS VLC Video source, set the order and loop or shuffle behaviour, then send OBS’s single configured feed to YouTube Live. Test transitions and audio using the actual files before relying on the sequence in a broadcast.
Does YouTube create a separate quality setting for every source file?
The encoder sends one configured live feed, and YouTube transcodes that incoming stream into playback formats. You do not configure a set of separate YouTube quality variants for each file in the local playlist.
Is an HLS Media Playlist the same as an OBS file playlist?
No. An OBS file playlist is a sequence of recordings for the encoder to play. An HLS Media Playlist lists media segments associated with a stream, so its role is different.