To stream a pre-recorded playlist to YouTube Live in 1080p, use an encoder to play the files and send the resulting feed to a YouTube Live event. Set the encoder output to 1920×1080, choose one frame rate explicitly, and confirm the incoming picture in YouTube Studio before the event is public.
The frame rate is set by the encoder, not by a promise that YouTube will preserve every chosen setting regardless of the incoming signal. Playlist order, audio, and looping also depend on the playback tool. Treat the local test and the Live Control Room preview as essential checks, not optional polish.
What 1080p at a fixed frame rate means
“1080p” describes a progressive video frame that is 1920 pixels wide and 1080 pixels high. “Fixed frame rate” means the encoder is configured to output at a selected rate, rather than varying the target during the broadcast. Common choices in YouTube's guidance include 30 or 60 frames per second (fps). The right choice depends on what is in your files and what your upload connection can sustain.
The distinction matters because the encoder takes the files and produces the live feed. A source file may have a different resolution or frame rate from the encoder output. Setting output to 1920×1080 establishes the dimensions you are asking the encoder to send; it does not restore detail missing from a lower-resolution source. Similarly, selecting a frame rate does not create motion detail that was not present in the original footage.
For a devotional channel built from static artwork and a song, 30 fps may be a sensible target if it matches the source and the encoder produces a clean feed. A local news loop with camera movement or other more fluid footage might have a reason to use 60 fps, provided its files and connection support it. Those are choices to test, not universal rules.
YouTube transcodes the incoming live feed into playback formats for viewers. A successful 1080p encoder configuration therefore does not mean every viewer will immediately see a 1080p option. The viewer's connection, device, and YouTube's processing affect playback. For a useful background on the delivery side, see how HLS streaming works; for this setup, judge the signal you send and the preview YouTube reports.
Create or schedule the YouTube Live event
Start in YouTube Studio's Live Control Room. Create a live event or schedule one, then set its title, description, privacy, and any other details before configuring the encoder. Check that the selected account and channel are the ones meant to host the stream. If you are scheduling for later, allow enough time to start the encoder and inspect the incoming feed before the planned public start.
YouTube's live streaming setup guidance covers creating a stream and connecting an encoder. Follow the current on-screen instructions because labels and layouts can change. The important outcome is that you have an event in Live Control Room and the event's encoder connection details, rather than a general upload page or a local recording profile.
Choose the stream key associated with the event or an appropriate reusable key. A stream key authorises the encoder to send video to the event, so handle it like a password: do not publish it, include it in a screenshot, or send it in an untrusted message. If it is exposed, use YouTube's current controls to replace or reset it. Avoid pasting it into a public troubleshooting post.
Before connecting, confirm the event privacy and intended start behaviour. A private test event can help you inspect the path without sending an unfinished broadcast to viewers. If you are testing the actual scheduled event, be clear about whether it is public, unlisted, or private and whether starting the encoder may begin the event. You control the event settings; test deliberately rather than assuming the preview is invisible to everyone.
Choose an encoder and provide its stream details
An encoder is the application or device that plays the prerecorded material and sends the live audio-video signal to YouTube. YouTube lists OBS among its verified software encoders. A software encoder can suit you if the computer that will run it is available for the broadcast and can play the files reliably. YouTube also lists dedicated hardware, including AJA HELO Plus, whose product listing describes prerecorded scheduling functionality. Hardware may suit an operation that needs a standalone appliance; it is not required merely because the source is a local video file.
Compare the work involved rather than assuming one category is always better. With software, you typically manage the computer, application, media files, and any operating-system interruptions. With hardware, you may have a more focused device workflow but need to assess purchase cost and the functions of the particular model. Do not buy a capture card just to play a file already on the computer; it is not inherently needed for that task.
In the encoder's streaming configuration, supply the YouTube stream URL and stream key shown for the event or selected key. Check each field carefully. A wrong key or URL can result in no feed or a feed going to a different destination. Keep the key private after setup as well; saving it inside your encoder does not make it safe to reveal in a screen recording.
OBS is one documented option, but exact playlist and loop controls should be confirmed in the version you are using. The OBS Media Sources documentation is the place to check its current media-source behaviour. The source material does not establish a reliable click-by-click playlist path for every version, so do not rely on an unverified menu sequence. If you use OBS, check the current documentation and test the actual scene and media arrangement. For a narrower guide to connection credentials, see stream key settings in OBS for an always-on bhajan channel.
Set encoder output to 1920×1080
In the encoder, locate its video output or video settings and set the output dimensions to 1920×1080. Some tools distinguish a base canvas from a scaled output resolution. Check the resulting stream output, not only the size of the canvas on which you arrange sources. If the source is a different shape or resolution, inspect how the encoder scales or crops it: letterboxing may be preferable to cutting off a logo, lyric, or caption.
The encoder may also expose separate settings for a local recording and for streaming. Make sure you are changing the live output profile, not only the settings used to save a file to disk. If you use a saved profile, verify it belongs to the event workflow and has not carried over an old resolution from another channel. After setting dimensions, check a representative frame in the preview for unexpected borders, stretched artwork, or text outside the visible area.
YouTube's encoder guidance lists recommended ingest settings by codec and frame rate. For H.264, it recommends 14 Mbps at 1080p30 and 17 Mbps at 1080p60. These are recommendations, not a guarantee of quality or an invented minimum for every system: YouTube's table also lists minimum figures, but the connection and encoder must be tested for your material. The difference between the two recommended H.264 settings is a reason to account for upload capacity when choosing 60 fps. Do not assume a number copied into a settings box proves the connection can sustain it.
YouTube lists CBR as the bitrate mode for RTMP/RTMPS ingest, with a recommended keyframe interval of two seconds and a maximum of four seconds. It recommends RTMPS, and its advanced SDR recommendations include Rec. 709, progressive scan, square pixels, and 8-bit depth. Use the relevant current values in the YouTube encoder settings guide, checking that your encoder exposes the setting and that it applies to streaming. If a setting is unavailable or labelled differently, do not guess that a similarly named recording setting applies.
YouTube's video quality settings article helps distinguish the incoming stream from the options available to a viewer. Likewise, the site's YouTube upload settings guide concerns uploaded video, so do not transfer its advice blindly to a live encoder. Upload encoding and live ingest are related video workflows, but this task is about the signal arriving at a live event.
Choose one frame rate and verify it
Select one target frame rate in the encoder, such as 30 fps or 60 fps, and leave it fixed through the broadcast. Prefer a target that suits the source files. If your playlist mixes files with different frame rates, the encoder still has to output a single chosen rate; test transitions between those files for judder, repeated frames, or a brief disruption. Avoid changing the target halfway through a live session, since viewers and the ingest path then receive a changing signal.
The trade-off is not simply “higher is better”. At 60 fps, motion can look smoother when the original footage supports it, but the encoder and upload connection have more work to do. At 30 fps, a static visual or conventional prerecorded programme may be adequate and can need less upload capacity than the 60 fps H.264 recommendation. YouTube's recommended H.264 figures are 14 Mbps for 1080p30 and 17 Mbps for 1080p60. Use them as ingest guidance for the matching codec and resolution, then test the real connection rather than treating them as a promise of performance.
| Encoder target | YouTube H.264 recommended ingest bitrate | Consider it when |
|---|---|---|
| 1920×1080 at 30 fps | 14 Mbps | The source is 30 fps or mostly static, and a steady, lower-bandwidth target is useful. |
| 1920×1080 at 60 fps | 17 Mbps | The source contains motion that benefits from the rate and the upload can sustain the higher recommendation. |
The table is specific to YouTube's H.264 recommendations; it is not a universal bitrate chart for every codec. YouTube lists different recommendations for AV1 and H.265. Match the codec row in its current guidance if using one of those formats, and do not combine an H.264 figure with a different codec as if the numbers were interchangeable.
After selecting the target, inspect the encoder's status or output information to make sure the live profile is actually using it. Then verify the feed in YouTube's preview, where the incoming stream and stream health are visible. If the preview does not appear as expected, check encoder output dimensions and rate, connection details, and stream health before going public. A configured target is only the starting point; observed output is the confirmation.
Check YouTube's automatic and manual setting options
YouTube says it automatically detects encoder settings by default. In other words, the incoming encoder signal informs the stream settings YouTube detects. Do not treat an automatic setting as a control that overrides the encoder or guarantees a particular resolution independent of what it receives.
If you need to select a resolution manually in YouTube, its guidance says to create a custom stream key and enable “Turn on manual settings” under Stream Resolution. Consult the current YouTube stream settings instructions for the exact path and available choices. The manual option is a YouTube-side setting; it does not replace configuring the encoder output to 1920×1080 or choosing the frame rate there.
Keep the roles separate when diagnosing a mismatch. The encoder produces the feed; YouTube ingests and processes it; the viewer receives a playback version. If you ask the encoder for 1080p but the incoming preview is not showing the expected format, first check the encoder profile and input. Then check the event's stream settings and health indicators. If the incoming feed looks correct but a viewer cannot select 1080p, processing or playback conditions may explain the difference. Do not promise that toggling a manual setting will make every viewer receive 1080p.
Test playlist playback and the preview
Before the event, run the playlist locally in the same encoder scene, with the same audio route and output profile you plan to use. Verify the order, whether each item starts and finishes as intended, transitions between clips, and what happens at the end of the final item. If the playlist is meant to repeat, confirm that it actually returns to the first item without a gap or an unintended stop. Playlist and loop behaviour are specific to the chosen encoder and version.
Listen as well as watch. Check that the programme audio is present, at a sensible level, and not duplicated by a desktop-audio route. Watch for black frames, cropped titles, blank gaps between clips, or an unexpected desktop notification. Test a representative section with movement and audio similar to the real stream. YouTube specifically recommends testing with sound and movement comparable to the planned broadcast in its encoder guidance.
Once the local test is sound, connect the encoder to YouTube and start sending the feed while the event is still in the intended test state. Wait for the Live Control Room preview and inspect it rather than relying on the encoder's “connected” indicator alone. Check the visible dimensions and frame appearance, listen to the preview if available, and review YouTube's stream health warnings. A successful connection only shows that data is reaching YouTube; it does not prove that the playlist, audio, rate, or picture are correct.
If you see a problem, change one relevant setting at a time and recheck the preview. A stretched frame points towards scaling or source dimensions; missing audio points towards the media or audio routing; dropped or unstable output calls for checking the connection, encoder status, and YouTube's health messages. Do not make several unrelated changes just before a scheduled start, because that makes the cause harder to identify.
For a 24/7 channel, also think through what happens beyond the test clip: what should play after a restart, whether the files remain available, and who will notice if the feed stops. This article covers format and verification, not a promise that a particular playlist tool will recover or loop correctly. If your plan uses OBS, test its playlist and replay settings in the exact version before relying on them overnight. For more on avoiding a stalled continuous stream, read about OBS auto-reconnect settings.
If you need the programme to keep running without leaving your own computer on, StreamNeo can remove that specific overnight computer-running task: you upload the video, connect the YouTube stream key, and the broadcast runs with monitoring and automatic restart if it drops. It is YouTube-only, so check that this matches your destination and workflow.
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 set 1080p and a fixed frame rate in YouTube Studio alone?
Set the encoder output to 1920×1080 and choose a single frame rate there. YouTube detects encoder settings automatically by default; its manual resolution option is a separate custom stream key setting and does not replace the encoder configuration.
Should I use 30 fps or 60 fps for a prerecorded playlist?
Choose a rate that suits the source and test it with representative clips. For H.264, YouTube recommends 14 Mbps at 1080p30 and 17 Mbps at 1080p60, so consider whether your upload connection can sustain the relevant recommendation.
Does OBS automatically loop a playlist?
Playlist ordering, loop behaviour, and end-of-file handling depend on the controls in the OBS version and arrangement you use. The exact controls were not verified here, so check current OBS documentation and test playback locally and in YouTube's preview before relying on them.
Why might viewers not see 1080p immediately?
YouTube processes the incoming live feed into playback formats, and the viewer's device and connection can affect available playback quality. Confirm the encoder output and incoming preview first; a correct encoder setting does not guarantee that every viewer immediately has a 1080p option.