Choose a resolution and frame rate your upload connection can sustain, then use the current bitrate guidance for your streaming destination and codec. For YouTube Live, that means setting a constant bitrate, using a two-second keyframe interval, and leaving upload headroom; the recommendations below are for YouTube ingestion, not universal settings.
The practical order is connection first, picture format second, codec and bitrate third, then a test in YouTube Studio. That keeps you from choosing an ambitious picture setting and discovering during a devotional programme, news loop or study session that the connection cannot carry it reliably.
Choose a picture format your connection can sustain
Resolution describes the dimensions of the video frame; frame rate describes how many frames are sent each second. A higher resolution can show more detail, while a higher frame rate can make motion look smoother. Both affect the bitrate you need. For a largely still bhajan image or a text-based lecture slide, smooth motion may matter less than it does for a camera-led event, but your audience still needs a picture that remains readable on its devices.
Start by asking what the stream contains. A fixed illustration, album-style visual or slowly changing study screen may not benefit much from a high frame rate. A presenter moving around, a local news desk with frequent cuts, or a product demonstration with small moving details may make motion handling more important. In either case, pick a candidate format that fits the content rather than choosing the largest number the encoder offers.
YouTube detects the encoder's resolution and frame rate by default. Its guidance also describes custom stream keys for manually setting resolution. The audience does not necessarily receive your incoming format unchanged: YouTube transcodes live streams into multiple output formats for different devices and network conditions. That does not remove the need to send a stable, well-formed input stream.
There is also a latency trade-off. YouTube describes latency as the time between capture at the camera or encoder and the event appearing in the stream. Lower latency can make interaction feel more immediate, but may increase playback buffering. If viewers are listening to a continuous devotional or lofi channel and are not interacting in real time, immediacy may matter less than consistent playback. YouTube's guidance says its low-latency option is unavailable at 2160p/4K.
For the first pass, compare 720p or 1080p at a frame rate suitable for the material, rather than assuming 4K is automatically better. The YouTube bitrate table later in this guide shows that its recommended ingest rates rise with resolution and, in several cases, frame rate. If you are working in OBS, the stable YouTube bitrate settings guide is a useful companion, but the actual decision still depends on your connection and the content you send.
How bitrate depends on format and codec
Bitrate is the amount of encoded data sent each second, commonly expressed in megabits per second (Mbps). The encoder uses that data to represent picture and sound. More detail or more movement can be harder to represent cleanly at a given bitrate, so the same bitrate can look different across content. A still image with a voiceover and a fast-moving camera scene are not equivalent tests.
For YouTube Live, the recommended ingest bitrate depends on resolution, frame rate and codec. The codec is the method used to encode the video. YouTube's guidance lists H.264, H.265/HEVC and AV1 for video ingestion. Its table gives separate recommendations for H.264 and for AV1/H.265. Do not take an H.264 recommendation and assume it applies unchanged to another codec, and do not copy this table to another destination.
Audio is part of the stream too. YouTube lists AAC or MP3 audio. Include the full stream's network demand when checking capacity, rather than treating the video number as the only traffic. Your encoder's audio bitrate contributes to the total; if a programme depends on music or clear speech, check that the audio is present and intelligible during the test instead of focusing only on a sharp preview image.
The right target is not necessarily the highest recommended number in the table. If your upload connection cannot sustain that rate with headroom, choose a lower resolution or frame rate, or an available codec that suits your workflow, then use the corresponding YouTube recommendation. You can also consider whether your production source actually contains enough detail to justify the higher format. A small static graphic will not acquire extra useful detail just because it is encoded at 4K.
YouTube Live bitrate recommendations by format
The following figures are YouTube's recommended ingest bitrates, in Mbps, from its encoder guidance accessed on 3 October 2026. They are recommendations for sending a live stream to YouTube, not guaranteed quality levels and not presets for Twitch or another service. Check YouTube's current encoder settings guidance before a real broadcast, as platform documentation can change.
| YouTube ingest format | AV1 / H.265 recommended | H.264 recommended |
|---|---|---|
| 2160p / 4K at 60 fps | 35 Mbps | 50 Mbps |
| 2160p / 4K at 30 fps | 30 Mbps | 42 Mbps |
| 1440p at 60 fps | 24 Mbps | 34 Mbps |
| 1440p at 30 fps | 15 Mbps | 21 Mbps |
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
| 1080p at 30 fps | 10 Mbps | 14 Mbps |
| 720p at 60 fps | 6 Mbps | 8 Mbps |
| 720p at 30 fps | 6 Mbps | 8 Mbps |
| 480p at 30 fps | 3 Mbps | 4 Mbps |
| 360p at 30 fps | 3 Mbps | 4 Mbps |
YouTube's table also provides minimum ranges. A minimum is not the same as the recommended value: for example, at 1080p60 the cited guidance shows minimums of 4 Mbps for AV1/H.265 and 6 Mbps for H.264, while the recommendations are 12 Mbps and 17 Mbps respectively. Do not use a minimum as though it were the recommended target for a normal setup. Nor should you infer that every scene will look satisfactory at the minimum.
Use the row for the format you have actually selected and the column for the codec your encoder sends. If you cannot sustain the corresponding recommendation plus audio and headroom, step down and test again. For instance, a 1080p30 H.264 candidate corresponds to 14 Mbps in YouTube's recommendation table. If the available upload is shared with other users or devices, that candidate may not be prudent even when a brief speed test seems to reach the number.
This table is deliberately labelled as YouTube Live guidance. Other platforms publish their own ingest settings, and requirements can depend on their supported codecs, formats and stream workflows. Before sending to another destination, consult its official help or developer documentation rather than reusing these values. For a 24/7 radio channel, it is also worth estimating the connection and data implications of continuous delivery; the always-on radio data guide discusses that separate planning question.
Set CBR and the keyframe interval
YouTube's encoder guide lists constant bitrate (CBR) for the bitrate mode and recommends a two-second keyframe interval, which should not exceed four seconds. A keyframe is a full reference frame from which later compressed frames can be decoded. The interval affects how the video is structured for delivery; it is not a substitute for choosing enough bitrate or a stable connection.
In your encoder, find the output or streaming section and set the rate control to CBR if available. Set the keyframe interval to two seconds. Encoder interfaces differ, so verify the result in the software's own documentation and, more importantly, in YouTube Studio's incoming preview and stream health messages. If your encoder expresses the interval in frames rather than seconds, use its documentation to translate the setting for the selected frame rate instead of guessing.
YouTube lists RTMP and RTMPS ingestion and recommends RTMPS, which it describes as a secure extension to RTMP. It also lists square pixels, progressive scan and Rec. 709 for SDR among its advanced guidance; for HDR it lists H.265, and the guidance consulted does not support AV1 for HDR. These details matter when you are configuring a more involved production or diagnosing a format mismatch. If you are simply sending a prepared video loop, avoid changing colour or scan options without a reason and check that your source and encoder agree.
Your stream key should be treated like a password. YouTube's stream setup instructions describe how to configure the stream in Live Control Room and connect an encoder. Keep the key private, do not show it on screen or in a screenshot, and reset it if it is exposed. Confirm that the stream URL and key are entered in the correct fields; a carefully chosen bitrate cannot compensate for a connection that is pointed at the wrong stream.
For a basic webcam stream, YouTube supports a simpler route; an encoder is useful when you need screen sharing, external audio or video gear, multiple cameras, or more production control. The Streamlabs Desktop setup walkthrough can help if that is your chosen encoder, while the settings above remain specific to YouTube's current ingestion guidance.
Check upload capacity and leave headroom
Upload capacity is the constraint for a live encoder. Download speed is not a useful substitute: a connection can download quickly and still have limited or inconsistent outbound bandwidth. Run an upload speed test from the same location and, where possible, over the same wired or wireless connection you plan to use for the stream.
YouTube recommends leaving 20% headroom. In practical terms, the total stream bitrate should fit below the upload capacity available to your encoder, with room left over rather than consuming the entire measured rate. Account for audio and any other outgoing traffic. If you are sending more than one stream or a backup stream from the same connection, include those demands as well.
A test result is only a snapshot. If the connection is shared in a home, office, shop or place of worship, another person starting a video call or uploading a file can reduce the bandwidth your encoder actually gets. Test at a time and under conditions similar to the planned broadcast, and repeat the test if your network varies across the day. If the stream is important, a wired network connection can reduce one source of variability, though it cannot fix a constrained broadband connection or congestion upstream.
A simple decision check is to take your intended YouTube bitrate, add the audio and other stream traffic, and compare that total with the upload capacity you can rely on after leaving YouTube's recommended headroom. If the margin is unclear, do not assume the best speed-test result will persist overnight. Lower the format or bitrate to a sustainable candidate and test it. This is more useful than optimising the picture in isolation and hoping the network will hold.
The same planning applies to an always-on channel. A short event can be scheduled when network use is light; an overnight loop has to cope with changing household or business use. If your local computer must remain on to encode all night, power, updates and network interruptions become part of the setup too. StreamNeo can remove the specific burden of keeping that computer running by turning an uploaded video into a continuous YouTube broadcast, but you still need to choose a suitable source and check the destination's current requirements.
Test the stream and inspect the incoming preview
Testing is part of setup, not a finishing touch. YouTube advises setting up the stream ahead of time and its tips suggest preparing at least two hours before an event and starting encoders at least 15 minutes before it. Those are planning suggestions, not guarantees that every issue will be found. For a new channel, remember that enabling live streaming for the first time may take up to 24 hours according to YouTube's live streaming access guidance.
Create the stream in YouTube Studio, enter the stream key and URL in the encoder, and send a private or unlisted test where appropriate. Watch the Live Control Room incoming preview before making the stream public. Check that the image has the expected aspect and orientation, the audio is present without clipping, motion is intelligible, and titles or overlays are not cut off. Then look at stream health and any messages, rather than deciding only from what the local encoder window displays.
Use representative material. A static title card is not a useful test for a programme that includes camera movement, scrolling lyrics or frequent scene changes. Test speech and music if both will be present. For a long-running devotional stream, include a section with the same sort of transitions and audio level as the overnight programme; for a news loop, include the moving lower-third or ticker. The point is to see the stream behave as it will when viewers are watching.
If there is a backup encoder, rehearse failover before relying on it. YouTube's streaming tips recommend testing backup arrangements. Confirm that the secondary source can take over and that the switch does not expose private information or leave viewers with a frozen screen. A backup is only useful if the people responsible know how it is meant to be activated.
Keep notes on the tested resolution, frame rate, codec, bitrate and network conditions. If you later change any one of them, repeat the relevant part of the test. For a longer-running channel, the guide to analysing a prerecorded live stream can help you think about what to review after the technical preflight, without confusing audience analytics with encoder health.
Adjust settings when the connection is unstable
If YouTube Studio reports connection problems or the incoming preview breaks up, work from the simplest likely cause. Check that the encoder is still connected, the correct stream key is active, and no other upload is using most of the connection. Then compare the outgoing bitrate with current upload capacity. A speed test taken earlier does not prove that the same bandwidth is available now.
If capacity is insufficient or fluctuating, reduce the demand rather than raising bitrate. One reasonable step is to reduce resolution, then choose the corresponding YouTube row and test again. If the image remains readable at a lower frame rate for mostly static content, that may also reduce the required bitrate. Make one change at a time so you can tell which adjustment helped. The guide to troubleshooting a YouTube stream that keeps disconnecting covers a related failure pattern; use current YouTube messages and your own tests to diagnose the actual cause.
Do not change codec casually in the middle of a production. Your encoder, source and destination all need to support the chosen format. If you move from H.264 to H.265 or AV1, use YouTube's matching recommendation, check the encoder output, and run a fresh preview. Likewise, a lower bitrate that remains below the network's real capacity may be more stable than repeatedly trying to preserve a higher resolution that the connection cannot sustain.
Latency settings deserve a separate decision. Lower latency is useful when audience interaction depends on responses arriving quickly, but YouTube notes a trade-off with playback buffering. For a prerecorded music or ambience channel, that interaction may not justify added buffering risk. At 2160p, YouTube's guidance does not offer the low-latency option, so choose the format with that limitation in mind rather than assuming every resolution supports every latency mode.
After a change, observe the incoming preview and stream health for long enough to include the kind of network conditions that caused trouble. For a 24/7 channel, a successful few minutes in the afternoon is not proof of a reliable overnight setup. Arrange a representative test window, monitor the first real broadcast, and have a practical fallback such as a lower tested format. Avoid promising yourself that a single preset or a provider's status label will prevent every interruption.
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 YouTube Live?
Choose the row that matches your resolution and frame rate, then use the column for your codec in YouTube's current recommended ingest table. The recommendation is not universal and should not be confused with the table's minimum range. Check that the total stream fits your reliable upload capacity with headroom.
Is YouTube's bitrate table suitable for other streaming platforms?
No. The figures in this guide are YouTube Live ingest recommendations. Check the official guidance for the destination you use, because supported codecs and recommended settings can differ.
Should I use 30 fps or 60 fps?
Choose based on the content and what your connection can sustain. Sixty frames per second can suit material with more motion, while a lower frame rate may be adequate for a largely static visual; use the matching YouTube recommendation and test the result.
Why does my stream buffer even when the speed test looks fast?
A speed test captures conditions at one moment, while a shared connection can have less upload capacity during the broadcast. Compare actual upload availability with the full stream bitrate, leave YouTube's recommended headroom, and check YouTube Studio's stream health messages. If necessary, step down to a tested format that the connection can sustain.