A reliable 24/7 YouTube stream starts with settings your encoder and internet connection can sustain continuously. For many relatively simple programmes, 1080p at 30 frames per second, H.264, CBR and a two-second keyframe interval is a sensible starting point, but YouTube does not publish one profile that is best for every channel.
The important distinction is between a setting that looks good for a short test and one that remains stable overnight. Choose the format from your programme, match the bitrate to measured upload capacity, test representative audio and motion, and plan separately for the fact that YouTube may not save a stream that runs beyond 12 hours.
Choose the protocol and stream format
For a standard encoder workflow, use RTMPS when your software or hardware supports it. YouTube describes RTMPS as the secure extension of RTMP and recommends it for YouTube Live. You can check the current protocol guidance in YouTube's encoder settings documentation.
RTMPS is usually the straightforward choice for a devotional channel, bhajan loop, local news scene, study timer or ambience station. It fits the common workflow where an encoder sends one continuous feed to YouTube using a stream key. Use a custom stream key only when you need manual control over settings that YouTube would otherwise detect automatically.
HLS is another supported route for particular encoder and codec workflows, including some HDR use cases. It is not automatically a more dependable option for a 24/7 stream. HLS sends video in segments, so it normally brings higher latency. Its documented workflow includes HTTPS POST or PUT, transport-stream segments of one to four seconds, and a rolling playlist with no more than five outstanding segments. That makes it useful when your encoder requires HLS or when its specific capabilities matter, but it adds requirements that are unnecessary for a simple RTMPS setup.
Choose progressive video rather than interlaced video for a modern web broadcast. Use square pixels. For standard dynamic range content, YouTube's guidance points to Rec. 709 colour space. These choices matter because a continuous stream is easier to troubleshoot when the source, encoder and destination are using the same basic assumptions.
Do not treat the protocol as an uptime guarantee. A stream can still stop because the source computer sleeps, the encoder crashes, the network changes, or the upload path becomes congested. If you are comparing operating methods, the practical difference between a local machine and an unattended service is covered in how to keep a YouTube live stream running while your laptop is off.
Select resolution, frame rate and codec
Resolution describes the number of pixels in each video frame. Frame rate describes how many frames arrive each second. Higher values can preserve more detail or smoother motion, but they also increase encoding work and usually require more sustained upload bitrate.
H.264 is the broadly compatible choice for a 24/7 stream. YouTube also lists H.265, also called HEVC, and AV1 as supported RTMP or RTMPS ingest codecs. The right choice depends on whether your encoder can produce the codec reliably and whether the receiving workflow supports the matching bitrate guidance. A codec that is theoretically efficient is not useful if the encoder cannot run it unattended for the whole broadcast.
For a comparatively static scene, such as a still temple image with gentle motion, a 30 fps output may be sufficient. A channel showing a presenter, scrolling local news, dancing, sports or frequent camera movement may benefit from 60 fps if the encoder and connection can sustain it. You should compare the visible improvement with the extra processing and bandwidth rather than assuming that 60 fps is always better.
YouTube's encoder settings page says that resolution and frame rate can be detected automatically by default. Manual selection requires a custom stream key with manual settings enabled. Leave detection in place when you have no clear reason to override it. Manual values are useful when you have deliberately prepared a fixed output, but an unnecessary override can make a mismatch harder to diagnose.
The following figures are YouTube's published bitrate examples, not requirements for every 24/7 programme. The H.264 figures are often the most relevant starting point for general-purpose encoders.
| Ingest format | AV1/H.265 minimum | AV1/H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 1080p at 60 fps | 4 Mbps | 12 Mbps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 4 Mbps | 10 Mbps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 1440p at 60 fps | 6 Mbps | 24 Mbps | 8 Mbps | 34 Mbps |
| 1440p at 30 fps | 5 Mbps | 15 Mbps | 7 Mbps | 21 Mbps |
| 2160p at 60 fps | 10 Mbps | 35 Mbps | 14 Mbps | 50 Mbps |
| 2160p at 30 fps | 8 Mbps | 30 Mbps | 11 Mbps | 42 Mbps |
For example, YouTube's current encoder guidance lists 5 Mbps as the H.264 minimum and 14 Mbps as the recommended bitrate for 1080p30. For 1080p60 H.264, it lists 6 Mbps minimum and 17 Mbps recommended. These are platform-published configuration figures, not results from a performance study and not a promise that a given connection will remain stable.
A 1080p30 H.264 output can be a reasonable editorial starting point for a low-motion 24/7 scene. It is not a YouTube-mandated 24/7 preset. If your content contains fast movement or fine detail, test 1080p60 or a higher resolution against the real upload headroom and the encoder's sustained load. If the source is only 720p, upscaling it to 1080p will not create additional detail and may add work without improving the picture.
Set bitrate for sustained upload
Bitrate is the amount of data your encoder sends each second. For a continuous broadcast, the relevant figure is not the best download speed shown by a broadband test. Measure the outbound connection used by the encoder, at the time and location where the stream will operate.
YouTube advises leaving approximately 20 per cent headroom between the total stream bitrate and available upload bandwidth. Include the video bitrate, audio bitrate and any other stream overhead in your planning. If you operate a backup feed, account for the primary feed, backup feed and margin together when they share the same connection.
A simple example shows why a nominally adequate connection can still be a poor choice. If your planned H.264 video bitrate is 14 Mbps for 1080p30 and your audio is 128 Kbps stereo, the connection must carry more than those encoder values, not exactly those values. You also need room for normal variation and any other activity on the network. If the measured upload speed falls during busy periods, the practical headroom falls with it.
Do not solve an unstable connection by raising the bitrate. First check whether another device is using the upload path, whether the router is changing connections, and whether the encoder is reporting dropped frames. A lower, stable output is more useful to viewers than a higher output that repeatedly buffers or disconnects.
Use constant bitrate, or CBR, for the outgoing stream. A variable bitrate mode can be useful in other video workflows, but a continuous live contribution benefits from a predictable rate that YouTube and your network can handle. Set the encoder's video bitrate to the selected value and then observe the actual stream health rather than assuming the setting is being applied correctly.
If you are troubleshooting repeated drops, compare the encoder log, YouTube's stream health messages and the network test at the same time. The causes are not always inside the bitrate field. Our guide to why a 24/7 YouTube live stream keeps disconnecting covers the wider failure pattern, including local power and connection issues.
Configure audio and keyframes
For ordinary stereo audio, AAC or MP3 can be used. YouTube's advanced guidance lists 128 Kbps for stereo at 44.1 kHz and 384 Kbps for 5.1 at 48 kHz. A devotional or music channel should pay particular attention to clipping, hum, silence and sudden level changes because viewers may listen for long periods, sometimes without watching the screen.
Use the channel's actual audio during testing. A silent test tone or a microphone that is not part of the final scene will not reveal whether a bhajan loop is clipping, whether a news presenter is too quiet, or whether a playlist has a missing audio track. Check both the encoder's local preview and the YouTube playback device.
Set a keyframe interval of two seconds. YouTube recommends two seconds and says not to exceed four seconds. Keyframes give the receiving service regular complete reference frames, while the frames between them describe changes. An interval that is too long can make seeking, recovery and processing less predictable.
Keep the setting consistent throughout the broadcast. If your encoder exposes both a keyframe interval in seconds and a GOP size in frames, check that they agree with the selected frame rate. At 30 fps, a two-second interval corresponds to 60 frames; at 60 fps, it corresponds to 120 frames. The encoder may use different terminology, so verify the resulting stream health rather than relying only on the labels.
Avoid changing codec, frame rate, resolution and keyframe settings during an unattended run unless you have tested the encoder's behaviour. A fixed profile is easier to monitor than a stream that changes shape whenever a scene changes.
Test continuous operation and monitor health
A short test can confirm that YouTube receives a signal. It cannot prove that a broadcast will survive the night. Test with the same source file, audio mix, output resolution, frame rate and network that you intend to use in production.
Use footage that represents the hardest part of the programme. For an ambience channel, include the scene with the most movement. For a local news loop, include the fastest ticker and any transition. For a devotional stream, test the loudest musical section as well as quieter passages. Watch for audio drift, frozen images, dropped frames, encoder overload and repeated reconnects.
Review YouTube's stream health messages while the test is running. Also open the public watch page and check the stream from a second device, preferably one using a different connection. This catches problems that are invisible in the encoder preview, such as a viewer-facing delay, a missing audio track or a playback failure on mobile.
If you use a backup encoder or feed, test the actual handover. YouTube's guidance describes stopping the primary encoder or disconnecting its Ethernet connection and verifying that the player rolls over. A backup that has never been exercised is only an assumption. Confirm which stream key it uses, whether it starts automatically, and what viewers see while the change takes place.
Monitor the source machine if one is running locally. Disable sleep, automatic restarts at inconvenient times and background updates that can interrupt the encoder. Check disk space if a local recording is being made. A computer that is technically powerful enough for a short video may still be unsuitable if it overheats, loses its audio device or depends on a person restarting it.
A cloud workflow can remove one particular operational burden. StreamNeo lets you upload the file once, add the YouTube stream key, and keep the channel running with your own computer switched off, with automatic monitoring and restart when the broadcast drops. It does not remove the need to choose suitable source media, check the channel and consider YouTube's archive behaviour.
For a practical pre-launch check, confirm these items in order:
- The source file plays from beginning to end and has the expected audio.
- The encoder output is progressive, uses the intended resolution and frame rate, and is set to CBR.
- The video bitrate leaves roughly 20 per cent upload headroom.
- The keyframe interval is two seconds and no longer than four seconds.
- YouTube reports a healthy incoming signal.
- The public watch page works on desktop and mobile.
- The local recording file is growing if an archive matters.
- You know who or what will respond if the stream stops.
Plan for a stream longer than 12 hours
The 12-hour issue is primarily about archives and DVR, not an encoder bitrate ceiling. A stream can remain live while YouTube's later handling of the recording is uncertain.
YouTube says that a stream exceeding 12 hours may not be captured at all. Its guidance also warns that DVR, which allows viewers to pause and rewind a live broadcast, may be limited or unavailable on streams longer than 12 hours. Do not design a 24/7 channel on the assumption that one uninterrupted day-long replay will always appear afterwards.
If the complete programme matters, record it locally or in another controlled location while streaming. Check that the file is actually growing and that the storage capacity is sufficient for the planned recording. A local archive is useful only if it is readable after the broadcast and stored somewhere that will not be lost with the encoder machine.
You should also decide whether one very long broadcast is the right publishing structure. A devotional station may value a continuous live presence more than a replay. A study channel may want shorter sessions viewers can find later. A news loop may need separate updates. Shorter planned segments can make archives easier to use, but they introduce transitions, new stream events and additional operational work.
Do not confuse this caveat with a setting that needs to be changed at the 12-hour mark. There is no special bitrate adjustment that guarantees a complete YouTube archive. The decision is about recording and publishing expectations, so make it before the stream begins.
Understand YouTube archive considerations
Live playback and the saved video are separate outcomes. The live player can work correctly while the resulting archive is incomplete, unavailable or difficult to navigate. This is why archive testing belongs in the launch checklist rather than being left until the next morning.
After a test, check the channel's live area, the watch page and the archive controls using the account and devices your viewers use. Confirm whether the recording is visible, whether its duration is what you expected, and whether the audio and video remain in sync. For streams above 12 hours, treat the YouTube archive as uncertain even when the live broadcast looked healthy.
Keep a local recording when a complete copy is important. If the programme is built from a file, retain the original media as well as the captured output when practical. The original can be easier to edit into shorter videos, while the captured output shows what viewers actually received.
YouTube's official live streaming archive guidance is the right place to check the current treatment of long broadcasts. Platform behaviour and product documentation can change, so review the current page before planning an important event or relying on a replay for your audience.
Archive planning also affects your content workflow. If you use a playlist of prerecorded material, make sure you understand how the source changes and transitions behave rather than assuming that a continuous player creates useful chapters automatically. The question of using a playlist of different prerecorded videos in a 24/7 stream is separate from the encoder settings, but it affects what you need to test.
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
What are the best settings for a 24/7 YouTube live stream?
There is no single YouTube profile that is optimal for every channel. A practical starting point for a simple programme is H.264, 1080p30, CBR, a two-second keyframe interval and YouTube's recommended bitrate, provided your encoder and upload connection can sustain it with headroom.
What bitrate should I use for a 24/7 stream?
Use YouTube's table for your chosen codec, resolution and frame rate, then check that the actual outbound connection can sustain the total stream while leaving approximately 20 per cent room. For H.264, YouTube lists 14 Mbps as the recommended figure for 1080p30 and 17 Mbps for 1080p60; these are guidance values, not guarantees of stability.
Will YouTube save a 24/7 live stream?
YouTube says a stream exceeding 12 hours may not be captured at all. DVR may also be limited or unavailable, so keep a local recording when a complete archive matters and do not promise viewers that one uninterrupted 24/7 replay will be available.
Should I use RTMPS or HLS?
Use RTMPS for the standard workflow when your encoder supports it, as YouTube recommends it for Live. Choose HLS when a required encoder or codec workflow calls for it, while allowing for its segment-based delivery and higher latency.