For an automated YouTube live stream, choose the output resolution and frame rate first, then set the bitrate for the encoder codec and use a two-second keyframe interval. YouTube recommends constant bitrate (CBR), advises not to exceed a four-second keyframe interval, and recommends leaving upload headroom.
These are settings for the feed going into YouTube, not guarantees about what every viewer will see. YouTube transcodes streams for playback. The encoder, network and unattended restart behaviour still need to be checked in a real test.
Start with the stream you need to send
Bitrate and keyframe interval solve different problems. Bitrate controls how much data the encoder sends over time; the suitable value depends on the codec, resolution and frame rate. Keyframe interval sets how often the stream contains a full reference frame, which helps the receiving system decode and seek through the video. Meeting a bitrate target does not compensate for an interval that is too long.
Decide what the channel is meant to show before choosing either setting. A devotional channel with a mostly static altar may not need the same output mode as a local news loop with motion and lower-third graphics. A lofi channel may prioritise a dependable long-running feed over a higher frame rate that adds little to the viewing experience. The source file's resolution is one consideration, but so are the encoder's available options and the upload connection that must carry the stream continuously.
For a recurring or unattended stream, distinguish between configuring YouTube and configuring the encoder. YouTube Studio can provide a stream URL and key, and its stream settings include Auto-start and Auto-stop controls. Those controls do not establish that a third-party encoder will launch on schedule, reconnect after a network interruption, or recover unattended. Verify those behaviours in the encoder's own documentation and in a test, rather than assuming that YouTube's controls operate the whole system.
Choose a YouTube bitrate for codec and output mode
Use YouTube's published recommendations for the specific ingest codec and mode you intend to send. Do not take a number from one codec column and apply it to another. YouTube's encoder setup guidance and bitrate table lists recommended bitrates for AV1 or H.265 and for H.264; its values differ for several resolution and frame-rate combinations.
| Output resolution and frame rate | AV1 / H.265 recommended | H.264 recommended |
|---|---|---|
| 2160p60 | 35 Mbps | 50 Mbps |
| 2160p30 | 30 Mbps | 42 Mbps |
| 1440p60 | 24 Mbps | 34 Mbps |
| 1440p30 | 15 Mbps | 21 Mbps |
| 1080p60 | 12 Mbps | 17 Mbps |
| 1080p30 | 10 Mbps | 14 Mbps |
| 720p60 | 6 Mbps | 8 Mbps |
| 720p30 | 6 Mbps | 8 Mbps |
| 480p30 | 3 Mbps | 4 Mbps |
| 360p30 | 3 Mbps | 4 Mbps |
The values are YouTube-published recommendations, not a promise of a particular picture quality. The table is useful for setting an encoder, but the actual image also depends on the source and encoder quality. A simple loop with little motion and a busy news graphic are not identical encoding jobs, even when their output modes match.
Be careful not to mistake a minimum bitrate for the normal target. YouTube also publishes minimums; for example, at 1080p30 it lists 5 Mbps for H.264 and 4 Mbps for AV1 or H.265, below their recommended values. A minimum is not the same as the recommended setting. If the connection cannot sustain the recommended rate, consider whether a lower output mode is a better fit than running the desired mode at a bitrate that leaves no margin.
For example, if your encoder sends H.264 at 1080p30, YouTube's listed recommended bitrate is 14 Mbps. At H.264 1080p60, it is 17 Mbps. If you instead use AV1 or H.265, the corresponding recommendations are 10 Mbps and 12 Mbps. Check that the encoder supports the codec you intend to use before selecting a number. YouTube lists H.264, H.265 (HEVC) and AV1, with frame rates up to 60 fps, but the available combination depends on your software or hardware encoder.
The 1080p always-on streaming guide can help you think through the output mode as part of a continuous-channel workflow. If your source is 4K HDR, consult the 4K 60fps HDR OBS guide as well; YouTube's guidance treats HDR codec and latency choices differently from a typical SDR stream. In particular, the cited YouTube encoder page recommends H.265 over RTMP(S) for HDR and does not support AV1 for HDR in that guidance.
Set the keyframe interval in time
YouTube Help's settings table says, “Keyframe frequency: Recommended 2 seconds Do not exceed 4 seconds.” Set the interval to two seconds when the encoder allows you to enter seconds directly. The number is a duration, not a fixed frame count.
Some encoder interfaces ask for an interval in frames instead. Multiply the desired number of seconds by the output frame rate: at 30 frames per second, two seconds is 60 frames; at 60 frames per second, it is 120 frames. If you change frame rate later, revisit the frame-count field. Leaving it at 60 frames after changing from 30 to 60 fps halves the interval in time.
Keep bitrate and keyframes separate in your checklist. If the video looks unstable or the ingest connection reports an issue, check the stream health and encoder messages rather than changing both values at random. A correct keyframe interval does not fix an undersized upload connection; a higher bitrate does not fix a keyframe interval beyond YouTube's stated maximum. Make one change at a time so you can identify which adjustment affected the test.
YouTube says 4K/2160p streams do not have the low-latency improvement option and are set to normal latency. That is another reason to choose resolution for the channel's actual use rather than selecting the largest available number by default. A study loop, ambient scene or repeating devotional video may have no need for a 4K output mode if the additional bitrate and network demand make the unattended setup harder to sustain.
Use CBR and the recommended ingest protocol
Set bitrate encoding to CBR, as YouTube specifies for its live encoder recommendations. Constant bitrate gives the upload a steadier target to carry than a mode that varies its data rate. It does not mean the internet connection itself is constant: competing household or business traffic can still reduce the capacity available to the encoder.
YouTube supports RTMP and RTMPS ingest and recommends RTMPS, which is the secure extension of RTMP. If the encoder offers RTMPS for the selected YouTube ingest point, use it. Follow the encoder's current instructions for the protocol and stream URL rather than guessing from an old saved profile.
The codec, mode, bitrate, CBR setting, keyframe interval and protocol form a useful configuration record. Save it alongside the source-file details and the date you checked YouTube's recommendations. If another person takes over the channel, this record helps them distinguish intentional settings from values that were inherited from an unrelated event profile.
For a 24/7 channel, use a custom or reusable stream key where appropriate, but handle it like a password. YouTube's stream settings documentation describes stream keys and Auto-start/Auto-stop controls. Limit access to people who need it, and reset the key if you believe it has been exposed. Keep in mind that a reusable key makes repeated setup easier; it does not make an encoder's schedule or recovery behaviour reliable by itself.
Check upload capacity, not just the speed-test headline
The selected bitrate has to fit the available outbound capacity for the whole time the stream is running. YouTube recommends leaving 20% headroom and emphasises upload capacity rather than download speed. Its live streaming network guidance recommends testing the upload bitrate. A connection that can download a video quickly may still be a poor fit for a high-rate outgoing stream.
As a practical example, if you select a 10 Mbps video bitrate, do not treat a speed test result of exactly 10 Mbps upload as comfortable capacity. YouTube's stated 20% headroom guidance means that the connection should have capacity beyond the stream's target, and competing uses can consume some of that margin. Treat the bitrate and headroom as a planning check, not a guarantee that a fluctuating connection will remain clear.
Run a speed test from the place and connection where the encoder will operate. If other users share the line, observe the network at a time when it is busy as well as quiet. Where you have a backup stream or a second output, include its demand in the bandwidth plan rather than counting the full upload rate twice. You can also review the practical considerations in this guide to upload speed for a continuous lecture stream.
A wired Ethernet connection can remove some sources of local wireless variation if the encoder and network equipment support it, but it does not increase the upstream capacity supplied by your internet provider. If the connection cannot reliably support the desired mode with margin, reduce resolution or frame rate and choose the corresponding YouTube bitrate recommendation. This is generally more predictable than keeping a demanding mode and hoping the connection has spare capacity.
Configure YouTube and test the unattended path
In YouTube Studio's Live Control Room, create or schedule the stream, then copy its stream URL and key into the encoder. YouTube says the encoder needs resolution, frame rate and bitrate specified; it detects other encoder settings. Manual resolution selection is available with a custom stream key and manual settings enabled. Check the current setup steps in YouTube's encoder documentation, since interfaces and available choices can change.
If you intend to start or stop the broadcast from the encoder, enable YouTube's Auto-start or Auto-stop controls where appropriate. Those are YouTube-side stream controls. They do not wake a powered-off computer, guarantee that an encoder process will restart after a crash, or prove that a third-party service can run unattended indefinitely. Confirm the encoder's own scheduling and reconnect behaviour before depending on it overnight.
Test with representative material: not just a still image, but the kind of motion, text and audio your channel will actually send. Check that a preview appears in Live Control Room, that stream health has no unexplained warnings, and that the audio is present. For an automated channel, also test what happens when the connection or encoder is interrupted and whether the expected schedule resumes. A brief successful start is not the same as confirming recovery after a failure.
If keeping a home computer awake and recovering a dropped encoder session is the part you need to remove, StreamNeo turns an uploaded video into a YouTube-only 24/7 live stream, so the broadcast can continue with your computer switched off. You still need to prepare the video, provide the YouTube stream key, and check that the channel workflow suits your needs.
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 bitrate should I use for H.264 at 1080p30?
YouTube's published recommended bitrate is 14 Mbps for H.264 at 1080p30. Set CBR and check that the available upload capacity can carry the stream with headroom. If it cannot, consider a lower output mode and use the recommendation for that mode.
How many frames is a two-second keyframe interval?
At 30 fps, set 60 frames; at 60 fps, set 120 frames. The interval is two seconds in either case, so recalculate if you change frame rate. YouTube recommends two seconds and says not to exceed four seconds.
Does YouTube Auto-start make my stream fully automatic?
No. Auto-start and Auto-stop are YouTube stream controls that let you start or stop from an encoder. They do not guarantee that the encoder will launch on schedule, recover from an interruption, or operate unattended; test those behaviours with the encoder you use.
Should I use download speed to check the stream connection?
No. The encoder sends video out, so upload capacity is the relevant measurement. YouTube recommends a speed test of upload bitrate and 20% headroom; shared network use can reduce what is available to the stream.