For a typical H.264 stream to YouTube, use RTMPS, constant bitrate (CBR), and a two-second keyframe interval. Choose a bitrate for the resolution and frame rate you actually send, then check that your upload connection can sustain the full stream with headroom.
Those settings are a starting configuration, not a guarantee against dropped frames or interruptions. Test with the audio and movement your channel will use, check YouTube's preview and stream-health messages, and adjust if the connection or picture is not holding up.
YouTube H.264 settings at a glance
The encoder sends a video signal to YouTube's ingest service. The settings need to agree: the bitrate must suit the output resolution and frame rate; the connection must carry video and audio continuously; and the keyframe interval must fit YouTube's guidance. YouTube recommends RTMPS, CBR and a two-second keyframe interval, and says not to exceed four seconds. Its live encoder settings also describe supported codecs and other encoder parameters.
Use the following table as a reference for H.264. These are YouTube's published minimum and recommended bitrates, in Mbps, for the listed ingestion resolutions and frame rates. If your connection can reliably support the recommended value plus audio and headroom, use that as a target. A minimum is not a promise that every kind of picture will look equally good at that rate.
| Output resolution and frame rate | H.264 minimum | H.264 recommended |
|---|---|---|
| 2160p (4K) at 60 fps | 14 Mbps | 50 Mbps |
| 2160p (4K) at 30 fps | 11 Mbps | 42 Mbps |
| 1440p at 60 fps | 8 Mbps | 34 Mbps |
| 1440p at 30 fps | 7 Mbps | 21 Mbps |
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 3 Mbps | 8 Mbps |
| 480p at 30 fps | 0.4 Mbps | 4 Mbps |
| 360p at 30 fps | 0.4 Mbps | 4 Mbps |
For a straightforward 1080p30 broadcast, the table's recommended target is 14 Mbps; for 1080p60 it is 17 Mbps. Do not carry either value over to a different output mode without checking the matching row. A static devotional image, a lofi animation and a busy local-news loop can also behave differently in compression, so the table cannot tell you whether your own material will look acceptable. Inspect a representative preview.
YouTube lists H.264, H.265 (HEVC) and AV1 as video codec options for live streaming. Its general guidance permits frame rates up to 60 fps. This article concerns H.264 in SDR; for HDR, YouTube's guidance recommends a separate HEVC path, so do not treat H.264 as its HDR recommendation. Check the current official page if you are configuring HDR or another codec.
Choose settings for your output resolution and frame rate
Start with the signal you intend to send, not the resolution of the original file or the monitor in front of you. In an encoder, output resolution and frame rate determine what reaches YouTube. A 4K source reduced to 1080p30 is a 1080p30 ingest stream for bitrate selection; a 1080p source sent as 720p30 should use the 720p30 row. Confirm the output fields in your encoder rather than assuming it preserves a source file's properties.
Higher resolutions and frame rates need higher recommended H.264 bitrates in YouTube's table. For example, moving from 1080p30 to 1080p60 raises the listed target from 14 to 17 Mbps. Moving from 1080p30 to 1440p30 raises it to 21 Mbps. These are comparisons between specific listed modes, not a rule for interpolating a rate for every possible combination. Use the published row for the exact mode you select.
The right choice is a balance between the picture you need and the connection you can hold steadily. A small local business showing a mostly fixed camera view may have little reason to send 4K if 1080p communicates the detail customers need. A channel with moving graphics or fast footage may value a higher frame rate, but it must support the corresponding bitrate. For a study channel or quiet ambience loop, try the intended output on a private or otherwise controlled test before settling on a lower mode; a still image can hide problems that appear once transitions or motion begin.
If the recommended bitrate does not leave sufficient upload headroom, choose a lower output mode rather than forcing a larger rate through a constrained link. Check YouTube's current table before publishing or changing a long-running channel, as recommendations can change. For a broader look at the relationship between a machine's workload and reliability, the discussion of OBS or FFmpeg on an Azure VM may help when you are deciding how to run an encoder; it does not replace selecting the bitrate for your actual output.
Set RTMPS and CBR
RTMPS is YouTube's recommended secure extension of RTMP. Select it in the encoder if it is available, and use YouTube's current setup instructions to enter the server address and stream key. Do not paste a stream key into a public screenshot or message: it grants access to the live ingest destination, and should be treated like a credential. The official encoder guidance is the place to recheck protocol and settings details.
Set rate control to CBR, or constant bitrate. CBR aims to keep the encoded data rate near the value you set rather than allowing it to fluctuate widely with scene complexity. That makes the network demand more predictable for a continuous broadcast. It does not mean the image is constant in quality: a complicated scene may need more bits to preserve detail than a static slide, even while the encoder holds its target rate.
Some encoders offer VBR or quality-based modes that vary bitrate. Those modes can suit file encoding or other workflows, but YouTube's live guidance recommends CBR. For a 24/7 channel, avoid choosing a variable mode merely because the average rate looks lower in a short sample. The peaks still have to cross your upload connection, and congestion can coincide with a peak. Set the CBR target from the correct YouTube table row, then verify the encoder is actually reporting the intended output.
YouTube's general H.264 guidance also lists square pixels, progressive scan, two B-frames, one reference frame and CABAC. For SDR it lists Rec. 709 colour and 8-bit depth. These fields may be exposed as advanced options in some encoders and fixed in others. If you have a reason to change an advanced parameter, change one at a time and test; otherwise, avoid turning a working configuration into a troubleshooting puzzle by adjusting fields without a need.
For audio, YouTube lists AAC or MP3, stereo sampling at 44.1 kHz and 128 kbps for stereo. Its guidance lists 5.1 audio only with AAC for RTMP/RTMPS, at 48 kHz and 384 kbps. Audio is part of the upload load, even if your channel mostly shows a still image. If you need exact current details for multichannel audio, confirm them on YouTube Help rather than relying on a remembered encoder preset.
Set the keyframe interval
Set the keyframe interval to two seconds. YouTube's current settings table says, “Keyframe frequency: Recommended 2 seconds Do not exceed 4 seconds.” That is YouTube Help's instruction, not a benchmark or a setting inferred from a particular channel's performance. A keyframe is a complete reference frame; other frames can encode changes relative to reference frames. Regular keyframes help the receiving and playback workflow find reference points in the stream.
Many encoders express this setting as a time interval or as a number of frames. If yours asks for frames, the equivalent depends on the frame rate: at 30 fps, a two-second interval corresponds to 60 frames; at 60 fps, it corresponds to 120 frames. Check whether the field is in frames, seconds or another unit before typing a value. A mistaken unit can turn a correct intention into a much longer interval.
Use two seconds rather than aiming at the four-second ceiling. The maximum is not a recommended target, and a setting longer than four seconds is outside the stated limit. If a preset changes frame rate, revisit the keyframe value too, particularly when the encoder expresses it in frames. For a detailed connection-side check when a stream is unstable, see how to check YouTube stream health from a DigitalOcean Bangalore VPS; a keyframe setting alone cannot diagnose the network path.
Check upload capacity and headroom
A speed test is a snapshot, while a live channel needs a connection that can carry the stream steadily over time. YouTube's streaming tips recommend testing upload speed, choosing a quality the connection can reliably support, and leaving 20% headroom. The total streaming bitrate cannot exceed the available upload bandwidth. Remember to account for audio as well as video, and for other activity sharing the same connection.
For illustration, if your intended video rate is 14 Mbps, your connection needs to carry more than 14 Mbps because audio and headroom also count. YouTube's 20% headroom recommendation means not planning to consume the full measured upload rate with the stream. Treat the speed-test result as a guide rather than a permanent guarantee: performance can change by time of day, Wi-Fi conditions, congestion, or other devices uploading files or backing up data.
If you run a channel from home in India, test on the same connection and in the same room where the encoder will operate. If possible, use a wired connection and pause cloud backups, file uploads and other high-demand traffic during the test. A shared broadband or office connection may not give your encoder all the measured capacity when other people are using it. Ethernet is a practical way to reduce dependence on wireless conditions, but it cannot fix a provider-side outage or insufficient upload capacity.
When the recommended bitrate plus headroom does not fit, do not simply ignore headroom and hope the line stays clear overnight. Lower the output resolution or frame rate and use its corresponding bitrate row, or arrange a more suitable connection. The Airtel broadband video-library upload guide concerns moving files to a VPS, not a live bitrate prescription, but it illustrates why the upload path itself deserves checking before you rely on a remote workflow.
Test and monitor stream health
A useful test resembles the actual channel. Send the selected resolution and frame rate, include the normal audio, and show representative motion: a scrolling ticker, animation, changing camera view or transitions between clips. A static title card is not a meaningful substitute for a moving news loop. Use YouTube's Live Control Room preview before the public event or routine broadcast, and read its stream-health status and messages rather than relying only on the encoder's local “streaming” indicator.
A practical preflight is to confirm the connection, verify the encoder's output resolution, frame rate and bitrate, confirm RTMPS and the two-second keyframe interval, then check audio and the preview. Let the test run long enough to notice whether the rate remains steady and whether YouTube reports a problem. This is a synthesis of YouTube's own test and monitoring advice, not a claim of independent testing or a guarantee that a later event will be trouble-free.
While live, keep an eye on YouTube's stream-health messages and the encoder's connection state. If you see warnings, note when they begin and whether the encoder's outgoing bitrate changes, then compare that with the available upload capacity and any activity on the shared network. Do not respond to every warning by raising bitrate: if bandwidth is the constraint, a higher target increases the demand. A lower output mode may be the safer practical choice.
For a 24/7 prerecorded loop, the operating burden is not limited to choosing a codec once. The source can end, a connection can drop, or a process can stop while nobody is watching. StreamNeo addresses the specific problem of needing to leave your own computer on to keep an uploaded video running: after setup, the broadcast can continue with your computer switched off, with monitoring and automatic restarts if it drops. It is YouTube-only, so this is relevant only if YouTube is your destination; codec choices and stream-health checks still matter.
If the channel is ready to move from test to a continuous broadcast, compare the practical operating choices before committing.
Latency and other boundaries
Codec settings do not decide every audience experience. YouTube offers latency choices, and its guidance notes that lower latency can mean more playback buffering. Choose based on whether near-real-time interaction matters more than buffering tolerance for your viewers. A devotional stream intended for listening in the background may have different priorities from a live local-news discussion where chat interaction is central.
YouTube says 4K/2160 live streams cannot use its low-latency optimisation and are set to normal latency. If low latency is essential to your format, check the current live stream management guidance while deciding whether 4K is appropriate. Do not assume that a higher resolution automatically improves the overall experience if viewers face buffering or your upload connection cannot sustain it.
These choices also have limits outside the encoder. H.264 settings do not settle questions about rights to music or video, eligibility, or whether YouTube will accept a specific broadcast. Review YouTube's current rules and the relevant official guidance for your channel. Nor does a clean test promise an uninterrupted night: it only helps expose issues in the tested setup before you depend on it.
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 1080p60 YouTube Live?
YouTube's H.264 table lists 17 Mbps as the recommended bitrate for 1080p60, with 6 Mbps as the minimum. Use the recommended value only if your upload connection can sustain it along with audio and the recommended headroom; otherwise consider a lower output mode.
Should I use CBR or VBR for YouTube Live?
YouTube recommends CBR for live encoder settings. CBR makes the target rate more consistent, but it does not make the picture equally complex from moment to moment or remove network risk.
How long should my keyframe interval be?
Use two seconds, as recommended by YouTube, and do not exceed four seconds. If your encoder asks for frames rather than seconds, convert using your actual frame rate and check the unit before applying the setting.
Do these H.264 settings apply to HDR?
No. YouTube's guidance recommends H.265 (HEVC) for HDR and says AV1 is not supported for HDR. Treat HDR as a separate configuration and check YouTube's current codec guidance before sending it.