To stream a 720p video playlist to YouTube Live without configuring OBS to upscale it, set the OBS output resolution to 1280×720, add the files as a VLC Video playlist, and send that feed to your YouTube event. This sets the size of the frame OBS sends; it does not change the resolution or detail in the source files.
YouTube transcodes live input into multiple formats for viewers, so a 1280×720 OBS output is not a promise that every viewer will receive one identical 720p rendition. The practical aim is to keep your outgoing encoder frame at 1280×720, use appropriate source files, and test the complete playlist before relying on it.
What “without upscaling” means for the stream output
In OBS, the Base (Canvas) Resolution is the working area where you arrange sources. Output (Scaled) Resolution is the size of the frame OBS encodes for streaming. Set the latter to 1280×720 when your goal is a 720p outgoing feed, rather than selecting 1920×1080 or a larger output and asking OBS to scale the composition upwards. OBS explains the distinction in its Video settings documentation.
That setting controls the output frame, not the files themselves. A 640×360 clip placed on a 1280×720 canvas does not gain real 720p detail. Depending on how you size it in the scene, it may be displayed smaller or enlarged to fill more of the canvas. For a straightforward workflow that avoids enlarging low-resolution material, use 1280×720 source files and avoid scaling those sources above their native size. This is a practical composition rule, not a guarantee that every stage of video processing bypasses scaling.
For a playlist made entirely of 1280×720 clips, keeping both the base canvas and output at 1280×720 is simple to inspect. The 16:9 shape also matches the common frame shape for 720p video. If your base canvas is a different size for a reason, still verify that Output (Scaled) Resolution is 1280×720; it is that output setting that defines the encoded frame size.
There is a second resolution distinction at YouTube. Your encoder sends an input stream at the resolution and frame rate you configure. YouTube then processes that live feed into multiple viewer formats. Its live encoder settings guidance describes those viewer renditions. Avoid interpreting a 720p OBS preview or ingest setting as a guarantee of a particular playback option on every device or network.
Add a VLC Video source and populate the playlist
OBS’s VLC Video source can play a list of media files in order. VLC must be installed for the source to be available, and the VLC and OBS installations need to match architectures: for example, 64-bit OBS with 64-bit VLC. The OBS VLC Video Source guide lists supported media formats and explains the source controls.
In the scene where the programme should appear, use the Sources panel to add a VLC Video source. Give it a useful name, such as “Main playlist”, then add the files in the order you want them to play. Use the list shown in the source properties as the definitive order; filenames in a folder may sort differently from the programme sequence you intended. If you replace or reorder files later, reopen the source properties and check the order again.
Keep the files in a stable location. If you move or rename one after adding it, OBS may no longer find it at the path stored in the source. Before a long broadcast, avoid treating a playlist assembled from temporary downloads or removable storage as ready until you have restarted OBS and confirmed the source still loads. A short preview after changing the list can catch a missing path before the event is live.
Check the scene preview after adding the source. If the video is smaller than the canvas, select the source and use a fit-to-screen transform only when its proportions allow it. A mixed playlist can contain different dimensions or aspect ratios. Fit or contain keeps the full picture visible but can leave empty bars; stretching can fill the frame but distort faces, text, or circular objects. OBS’s aspect ratio guidance explains why stretching sources to a different ratio changes their appearance.
If a 4:3 clip appears between 16:9 clips, decide whether bars are preferable to cropping or distortion. Make that decision intentionally rather than assuming the playlist will make every file match. Inspect the transition into and out of each unusual item, since a source transform that looks right for one clip may not frame another the same way.
A playlist is not the same as a YouTube playlist of hosted videos. Here, OBS reads local media files and encodes them as one live programme. For a different workflow based on an audio feed, see the practical notes on streaming an RSS podcast feed live on YouTube. For a video programme with a fixed sequence, the local VLC list gives you direct control over the clip order.
Set the OBS output to 1280×720
Open OBS Settings, choose Video, and set Output (Scaled) Resolution to 1280×720. If your clips are already 1280×720 and your scene contains no other size requirements, set Base (Canvas) Resolution to 1280×720 as well. The canvas is where you compose the scene; the output resolution is the frame size sent to the encoder. Check the text in the settings rather than assuming that changing one dropdown changed both.
Choose a common frame rate that suits the material. For a playlist of ordinary 30 fps clips, 30 fps is a sensible starting point; if the source is 60 fps and its motion benefits from that cadence, 60 fps may be appropriate. A setting of 60 fps does not make 30 fps footage contain additional motion detail. Conversely, sending 30 fps when the source was made for 60 fps can make motion look less fluid. Check representative footage in the OBS preview after changing the setting.
The 720p setting describes the output dimensions, not a quality repair tool. OBS cannot recover detail lost by a smaller source, poor compression, or a soft original. If one file is only 480p, the overall outgoing feed can still be 1280×720, but that portion will not have native 720p detail. Keep this distinction in mind when you assemble the playlist and when you judge the preview.
For a 24/7 channel, it may be tempting to choose a larger canvas now in case you later add graphics. That can be reasonable if your actual target is 1080p, but it does not meet the specific aim of a 1280×720 output. A separate guide to YouTube Live settings for 1080p at 30 fps covers that different target. Do not copy a 1080p output setting into a 720p workflow simply because it appears to be a higher-quality default.
Enable playlist looping if needed
In the VLC Video source properties, enable Loop Playlist if the programme should begin again after the final file. OBS documentation says this option is on by default, but it is worth verifying the actual checkbox rather than relying on a remembered default. If the playlist is meant to play once and stop, leave looping off and plan what the live scene should show at the end.
Turn off Shuffle Playlist when viewers should hear or see the clips in a known order. Shuffle is useful only when variation is intended. For a devotional sequence, lessons arranged by topic, or a news loop with a planned running order, confirm the list order and shuffle setting together. These settings answer different questions: looping decides what happens after the last item, while shuffle changes how the items are selected.
Test a complete pass through a short representative playlist, then confirm the transition from the final file to the first. If you are using a long list, also test several transitions between different formats or aspect ratios. A video that plays correctly by itself may still reveal a blank interval or an audio change when the next item starts.
The VLC source has visibility behaviour to consider if you switch scenes. Depending on its source settings, media can continue, pause, or stop when the source is hidden. If your live programme will move between scenes—for example, from the playlist to a holding slide—check that behaviour in a rehearsal. A channel built around one uninterrupted scene has fewer scene-transition variables, but it still needs a plan for a finished, missing, or stalled file.
Check frame rate and bitrate settings
For H.264 live input, YouTube’s current encoder table recommends a video bitrate of 8 Mbps for both 720p30 and 720p60. YouTube recommends constant bitrate (CBR), a 2-second keyframe interval, and says not to exceed 4 seconds. These are YouTube’s ingest recommendations, not a promise about the quality or resolution viewers will receive after processing. Check the current YouTube encoder settings table if you use another codec or revisit the setup later.
In OBS, open Settings and then Output, select the streaming encoder settings, and choose the bitrate and keyframe interval that match the guidance. H.264 is a broadly supported baseline for a simple software workflow. YouTube also lists other codecs, but use one only when your encoder and workflow support it reliably. On a modest computer, fewer moving parts are often easier to diagnose than a codec change made without testing.
Audio is part of the outgoing bitrate as well. YouTube lists AAC or MP3 audio for RTMP/RTMPS ingest, and its detailed guidance specifies 128 Kbps for stereo. Check that the VLC source’s audio is reaching OBS, that the correct device or mixer is active, and that levels are not clipping. A silent stream can have a perfectly configured video resolution; resolution settings do not test the audio path.
YouTube recommends RTMPS where supported for encrypted delivery. In OBS, use the server URL and stream key supplied for the event in YouTube Live Control Room. The stream key is password-like: anyone who obtains it could send a feed to that event. Do not show it in screenshots, overlays, or public instructions. YouTube explains where to find and use these details in its encoder setup help.
Your upload connection needs more capacity than the stream’s total bitrate, and download speed is not a substitute for an upload check. YouTube’s streaming tips recommend leaving 20% headroom above the total bitrate needs of the stream. That margin allows some variation in a real connection; it does not make an unstable connection dependable. Test over the same connection and at the time of day you expect to run, particularly if other people or devices share it.
For comparisons with other settings, the useful question is not “which number is always best?” but which one matches your source and available upload capacity:
| Choice | When it fits | What to check |
|---|---|---|
| 720p30 | The playlist is mostly 30 fps or has modest motion | Set 30 fps and use YouTube’s H.264 720p recommendation |
| 720p60 | The source is 60 fps and the motion benefits from it | Confirm the computer and upload connection can sustain the feed |
| Loop enabled | The sequence should repeat continuously | Verify the last-to-first transition |
| Loop disabled | The programme should end after one pass | Decide what the live scene does at the end |
| Fit or contain | You want the whole image and its proportions retained | Accept bars where source and canvas ratios differ |
| Stretch to fill | Rarely appropriate when proportions matter | Expect distortion if the source ratio differs |
The table is a decision aid, not a recommendation to raise bitrate or frame rate without regard to the source. YouTube lists the same H.264 video bitrate for 720p30 and 720p60 in its current table, but a higher frame rate still asks OBS to encode more frames. A machine or connection that struggles should be assessed in a test rather than assumed to be suitable from the bitrate figure alone.
Test the outgoing stream and viewer renditions
Create or select the live event in YouTube Studio’s Live Control Room, copy its server URL and stream key into OBS, and start a private or otherwise suitable test event before the broadcast you care about. Keep the key confidential and double-check that OBS is connected to the intended event. A test using the wrong event can look technically healthy while leaving the planned event untouched.
Check the chain in order. In OBS, confirm the preview is framed at 1280×720 and that the VLC source is advancing. Watch the audio mixer while the clip plays. In Live Control Room, confirm YouTube is receiving the stream and review the stream health messages. Then open the viewer playback and check that the picture and sound are present. The preview inside OBS proves only that OBS can compose the scene; it does not prove the YouTube ingest or playback path is working.
Use clips with representative motion, audio, and transitions in the test. A still title card does not reveal a frame-rate problem that appears in moving footage. Listen across a clip change to catch a volume jump, silence, or unwanted overlap. If the playlist contains mixed aspect ratios, inspect each kind of transition rather than checking only the first item.
Viewer playback options can differ from your OBS output because YouTube transcodes the live input into multiple formats. Test the rendition options available in the player, and try playback on the types of devices your viewers use where practical. A viewer may have a different network or device, and YouTube’s processing determines which playback options are available. You can configure the encoder’s output; you cannot promise every viewer the same rendition or a particular playback choice.
When a test drops frames or shows poor health, do not immediately increase the bitrate. First check upload capacity, competing network use, OBS rendering or encoding warnings, and whether the selected frame rate is appropriate. If the test looks good only when no one else is using the connection, plan for that shared-use condition rather than treating the quiet test as proof. A checklist for keeping a YouTube radio livestream running after a power cut may help with a different continuity risk, but it does not replace testing the connection and playlist itself.
If your aim is an unattended channel, a desktop workflow also means the computer, OBS session, and local files must remain available. StreamNeo removes the specific burden of leaving your own computer running by taking an uploaded video and running it as a YouTube live stream after you provide the channel’s stream key. It is YouTube-only, so an OBS playlist remains the more direct fit when you need local scene controls or a live, changing programme.
Before relying on a long-running schedule, repeat the test after a computer restart and after any media, scene, or network changes. Confirm the playlist starts where expected, loops where intended, and reaches YouTube with sound. For continuous operation, a tested opening is not enough: the last-to-first hand-off is part of the programme too.
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 setting OBS to 1280×720 change my video files?
No. The setting controls the outgoing OBS frame size; it does not rewrite or add detail to the source clips. A lower-resolution clip can appear in a 720p output, but it does not become native 720p material.
Will every YouTube viewer get the same 720p rendition?
No such guarantee follows from the OBS canvas setting. YouTube transcodes a live feed into multiple output formats, and viewer playback options can vary with the platform’s processing, device, and connection.
Should I choose 30 fps or 60 fps for a 720p playlist?
Choose a frame rate that matches the source motion and that your computer and connection can sustain. For ordinary 30 fps files, 30 fps is a sensible starting point; use 60 fps when the source and programme benefit from it, then test the complete stream.
Why is the VLC Video source missing in OBS?
Install VLC and check that it matches OBS’s architecture, such as 64-bit VLC with 64-bit OBS. Restart OBS after installing VLC, then check the Sources menu again.