For a 24/7 YouTube stream from a pre-recorded 4K playlist, use YouTube’s published ingest settings as a starting point, then check that your encoder and upload connection can sustain them. For H.264, YouTube recommends 30 Mbps at 2160p30 or 35 Mbps at 2160p60; neither figure guarantees uninterrupted delivery or 4K playback for every viewer.
Set up the stream in YouTube Studio, test the complete playlist and audio, and monitor the broadcast after it starts. Do not rely on YouTube to save a continuous 24-hour replay: its archive guidance warns that streams longer than 12 hours may not be captured at all.
Choose a 4K frame rate and codec
Start with the frame rate of the source video rather than selecting the largest number available in your encoder. A 4K file recorded at 30 frames per second can normally be sent as 2160p30; changing it to 60 fps does not add motion detail that was not in the original and raises the recommended H.264 bitrate. For a playlist made from mixed sources, matching the output to the material and avoiding needless conversion is usually simpler to maintain. Our guide to choosing a frame rate for mixed-source videos in an OBS playlist covers that decision in more detail.
YouTube’s encoder-settings guidance lists H.264, H.265/HEVC and AV1 as supported ingest codecs. Its published H.264 recommendations for 2160p are:
| Output format | YouTube-recommended H.264 video bitrate |
|---|---|
| 2160p at 30 fps | 30 Mbps |
| 2160p at 60 fps | 35 Mbps |
These are YouTube recommendations, not a test of your particular encoder, internet connection or playlist. The same guidance gives minimum-to-maximum bitrate ranges for HEVC and AV1: 8–35 Mbps for 2160p30 and 10–40 Mbps for 2160p60. Those ranges are not the H.264 recommendations in the table. If you choose a codec other than H.264, consult the current YouTube encoder settings page and use settings that your encoder can sustain.
For SDR video, YouTube’s guidance includes progressive scan, square pixels and Rec. 709 colour, with AAC audio as an appropriate choice. The exact menu labels depend on the encoder. Keep the output consistent with the source: applying an unsupported frame rate or colour conversion can add work without improving what viewers see.
A 4K ingest signal also does not mean that every viewer receives a 4K rendition. YouTube transcodes live input into formats for different devices and network conditions; playback quality depends on the available rendition and each viewer’s circumstances. If many viewers use mobile connections, a clean source feed and sensible frame rate matter more than assuming everyone will select the top quality.
Set the encoder bitrate
For H.264, choose the row that matches the intended 2160p frame rate and set constant bitrate (CBR), as YouTube recommends. Use a two-second keyframe interval; YouTube says it should not exceed four seconds. Confirm whether your encoder expresses the interval in seconds or frames, since the frame count changes with frame rate. These settings describe the outgoing video stream, not a promise about what the platform will deliver to every viewer.
The difference between 30 Mbps and 35 Mbps is not a reason to up-convert a 30 fps source. At 60 fps, more frames are sent each second, so the higher recommendation is relevant when the source and encoder genuinely support 60 fps. If the source is still imagery or slow-moving ambience, test the intended output with its actual audio and motion rather than making assumptions from the words “4K” alone.
You also need to account for audio and normal network variation. YouTube’s network advice recommends leaving 20% of upload capacity free. Applying that headroom to a 30 Mbps video target means planning for at least 36 Mbps of usable upload capacity for the stream, before other traffic; this is arithmetic based on YouTube’s recommendation, not an additional bitrate target published by YouTube. If other people share the connection, their activity can reduce the capacity available to the encoder.
Do not set a bitrate your connection can only reach in a brief speed test. Test at the place and time the channel will run, using the intended encoder and representative audio and video. Leave room for ordinary variation and other devices. If your connection cannot sustain the chosen 4K target with headroom, lower the output resolution or frame rate rather than repeatedly sending a feed that fluctuates.
Configure YouTube Live ingest
In YouTube Studio, create or schedule an encoder stream in the Live Control Room. The encoder needs YouTube’s stream URL and the stream key associated with that event. Treat the key like a password: do not put it in a public screenshot, shared document or broadcast overlay. If you think someone else has obtained it, reset it in Studio before using the stream again.
You can use “Reuse settings” when creating another event, but check the copied title, visibility, latency, DVR and other event choices before starting. Reusing settings can save entry work; it does not establish that the new stream is configured for the same playlist or purpose. YouTube’s live stream settings guide explains the controls available in Studio.
YouTube accepts RTMP and RTMPS ingest. RTMPS is its encrypted option; choose it if your encoder offers it and configure the matching URL. Confirm that the encoder is sending the selected codec, resolution and frame rate, rather than relying on a saved profile whose details you have not checked. A short private or unlisted test can help expose a wrong key, URL or video setting before you schedule a public broadcast.
For 2160p, YouTube says the low-latency improvement option is unavailable and the stream uses normal latency. That is often acceptable for a pre-recorded playlist with little audience interaction: there may be no live presenter waiting for an immediate reply. DVR is a separate decision. It lets viewers pause or rewind a live stream and continue from where they paused, which may suit an ambient station but be less appropriate for a stream where viewers should see the current moment.
YouTube documents the Live Control Room controls, but its reviewed guidance does not prescribe how to build or loop a playlist. That behaviour belongs to your encoder or streaming service. Look up its instructions for ordering files, handling the end of a file and returning to the start of the playlist, then verify those steps in a test. Do not assume a stream will resume at the right item after an encoder restart.
Prepare and loop the playlist
Before scheduling a long broadcast, check the files and the order in which they should play. Confirm that the encoder can read every file, that audio levels are appropriate from one item to the next, and that the transition from the final item back to the first is acceptable. A playlist that works once may still have an unexpected pause, silence or black frame at the loop point. Watch a test long enough to include that transition.
If you use OBS, check the media source’s loop and restart behaviour rather than expecting a file to replay automatically. For a specific example of the failure mode, see how to fix an OBS media source that stops after one play. The software’s behaviour can depend on how sources and scenes are configured, so verify the settings in your own project instead of copying a configuration without context.
Keep a record of the intended order and the source files somewhere you can reach if a playlist needs to be rebuilt. If one item has a different frame rate, aspect ratio, loudness or colour appearance, test it in the full sequence. An encoder can produce a valid live signal while the content still changes visibly or audibly at each transition. A test is useful for finding those defects, but it cannot prove that a continuous stream will run without interruption for days.
If the computer running the encoder must remain on, the setup also depends on its power, sleep settings and the stability of the application. Preventing a display from sleeping is not the same as preventing a computer from sleeping, and an operating system update or restart can stop the output. For a local machine, review the relevant application and power settings; our article on keeping XSplit running overnight on a Windows PC in India describes practical checks for that kind of arrangement.
A playlist can be technically valid and still need a human check after launch. Confirm that the intended item is playing, audio is present, and the stream title and visibility are correct. If you need to avoid showing a scheduled broadcast before its start, follow a separate checklist such as keeping a pre-recorded YouTube live stream private until its scheduled start. The mechanics of scheduling and looping are distinct; check both.
Check upload capacity and stream health
Measure upload capacity from the location and connection the stream will actually use. A headline speed from a different room, a different network or a quiet time of day may not reflect the conditions during a long broadcast. YouTube advises testing bandwidth, leaving headroom and accounting for other people sharing the connection. Its network guidance says total stream bitrate must not exceed available upload capacity and recommends 20% room. For more detail on the arithmetic for another live format, see how much upload bandwidth a YouTube radio livestream needs.
Before going public, inspect the Live Control Room preview for the correct picture and sound, then check its stream health indicators and alerts. A preview that appears once is not evidence of long-term continuity, but it can reveal a missing audio track, wrong resolution or failed ingest. During the broadcast, check that the encoder remains connected and the source continues to move through the playlist. If you cannot watch continuously, arrange a way to receive and act on alerts rather than assuming a stream is healthy because it started.
Plan what you will do if the encoder or connection drops. Know how to reconnect, whether the playlist restarts or resumes, and whether viewers will see a new live event or a continuation. These details vary by the tools used and should be tested rather than inferred. YouTube’s streaming tips recommend preparing the encoder in advance, checking stream health and keeping a local archive where needed.
A local recording is useful if you need to diagnose a fault or preserve a replay, but confirm that it is actually being written and that storage is available for the planned duration. Check a recording while the stream is running and open a completed test file. If maintaining an always-on encoder on a computer is the main source of worry, StreamNeo removes the need to leave your own computer switched on for the broadcast, while leaving you responsible for the video, channel settings and rights checks.
No short test can establish that a particular setup will remain uninterrupted through a night, a network change or a later software update. Use tests to catch known configuration problems, then keep monitoring and a recovery plan. If the stream has business or community importance, decide in advance who can check alerts and what to tell viewers if the broadcast stops.
Understand 24/7 archive limits
YouTube’s archive guidance says it automatically archives live streams shorter than 12 hours and automatically archives 1440p and 2160p streams. It also warns that streams longer than 12 hours may not be captured at all. A 24/7 stream necessarily exceeds that duration, so do not promise that YouTube will preserve one continuous replay or treat the live archive as your only copy. See the current YouTube archive guidance before relying on a platform behaviour that may change.
If the replay matters, arrange a separate local recording and test that it is complete and playable. Think about storage for the actual recording duration, not just the length of one playlist pass. A local archive is independent of whether YouTube captures the live event; it still needs monitoring, a suitable destination and a plan for checking the resulting file.
You may choose to end and restart broadcasts on a schedule to make separate events, but that changes the viewing experience and requires its own operational plan. Do not infer from a scheduled restart that the old broadcast will be archived, or that viewers will automatically move to the next event. If an uninterrupted audience experience matters, communicate the event structure and test transitions. YouTube’s published warning is the reason to plan a backup, not a guarantee about any particular archive outcome.
Review copyright and monetisation policies
A pre-recorded playlist does not avoid live-stream copyright checks. YouTube says it scans live streams for third-party content, including material appearing in another broadcast. If it identifies such content, it may show a placeholder and warn the channel; if the content remains, it may interrupt or terminate the stream. A live stream may also be terminated after a copyright or Community Guidelines strike. Check YouTube’s current copyright guidance for live streams and make sure you have rights for every video and audio item in the playlist.
If a rights holder has licensed content for use, that alone may not prevent an interruption. YouTube says the rights holder may need to add the channel to its Content ID allowlist. Check the arrangement with the rights holder and follow YouTube’s current process before relying on a licence during a live broadcast. If YouTube archives a live stream, Content ID claims on that archive can be made after the stream ends. Permission, platform detection and archive review are related but separate issues.
Monetisation is a different question from copyright. YouTube’s channel monetisation policy says highly repetitive or mass-produced material with little educational, commentary, narrative or other viewer value may be ineligible. Owning a video or having permission to use it does not by itself establish that a channel meets monetisation requirements; conversely, a monetisation review does not replace rights clearance. Read the current YouTube channel monetisation policies and check how they apply to your channel.
A recurring stream can be useful to viewers when it has a clear purpose, but repeating a playlist is not by itself a promise of monetisation. Consider whether the programming, context or presentation gives viewers something meaningful beyond an unattended loop. Do not claim that a continuous schedule, 4K picture or a particular title guarantees eligibility or approval. Policies and channel decisions belong to YouTube, and you should check its official pages for current requirements.
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
How do I stream a pre-recorded 4K playlist 24/7 on YouTube?
Create an encoder stream in YouTube Studio, configure an encoder or service to send the playlist to the stream URL with the associated key, and verify the loop and output in a test. Use YouTube’s codec and bitrate guidance as a starting point, then check the preview, stream health and upload capacity. A test can find setup faults; it does not guarantee uninterrupted operation.
What bitrate should I use for a 4K YouTube live stream?
For H.264, YouTube recommends 30 Mbps at 2160p30 and 35 Mbps at 2160p60. Match the output frame rate to the source where practical, use CBR and set a two-second keyframe interval, not over four seconds. Leave upload headroom and test the actual content and connection.
Will YouTube save a 24-hour livestream?
Do not count on it. YouTube says streams longer than 12 hours may not be captured at all, even though it automatically archives shorter streams and 1440p and 2160p streams. If you need a replay, arrange and check a separate local recording.
Does 4K mean every viewer will see 4K?
No. YouTube transcodes the incoming stream into formats for different devices and connections, and playback quality depends on the available rendition and viewer conditions. Sending a 2160p feed is an ingest choice, not a promise about every viewer’s screen.