Stream Bitrate
Stream bitrate is the amount of encoded video and audio data a live encoder sends to YouTube each second. It is usually measured in kilobits per second (Kbps) or megabits per second (Mbps).
A higher bitrate gives the encoder more data to describe each frame, which can preserve detail during motion. However, the bitrate must also fit the creator's upload connection, codec, resolution, frame rate, and hardware. A bitrate that is too aggressive can make a stream less reliable rather than more professional.
How stream bitrate works
A live encoder compresses camera, screen, and audio sources into a stream that can be sent to YouTube. The bitrate controls roughly how much data that encoded feed uses over time.
For example, a video bitrate of 6 Mbps means the encoder is trying to send about six megabits of video data each second. Audio uses an additional, much smaller bitrate. Protocol overhead and normal bitrate variation can add more network demand.
YouTube receives this contribution feed and transcodes it into multiple playback versions. A viewer on a strong connection may receive a high-resolution version, while another viewer may receive a lower-resolution version. The creator's ingest bitrate is therefore not necessarily the bitrate every viewer receives.
Stream bitrate versus related settings
| Setting | What it controls | Why it matters |
|---|---|---|
| Bitrate | Data sent per second | Influences detail, compression artifacts, and upload demand |
| Resolution | Number of pixels in each frame | Higher resolutions normally need more bitrate |
| Frame rate | Frames sent per second | 60 fps usually needs more bitrate than 30 fps |
| Codec | How efficiently video is compressed | AV1 and H.265 can preserve more quality at a given bitrate than H.264 |
| Upload speed | Capacity of the internet connection | Must reliably exceed the stream's actual data rate |
A speed test showing 20 Mbps upload does not mean a creator should automatically stream at 20 Mbps. Connections fluctuate, other devices use bandwidth, and the encoder needs room to deliver the feed without sustained congestion or dropped frames.
YouTube's current recommended live bitrates
YouTube bases its recommendations on the ingest codec, resolution, and frame rate. The following values reflect its current live encoder guidance:
| Resolution and frame rate | AV1 or H.265 range | H.264 recommendation |
|---|---|---|
| 2160p at 60 fps | 10–40 Mbps | 35 Mbps |
| 2160p at 30 fps | 8–35 Mbps | 30 Mbps |
| 1440p at 60 fps | 6–30 Mbps | 24 Mbps |
| 1440p at 30 fps | 5–25 Mbps | 15 Mbps |
| 1080p at 60 fps | 4–10 Mbps | 12 Mbps |
| 1080p at 30 fps | 3–8 Mbps | 10 Mbps |
| 720p at 60 fps | 3–8 Mbps | 6 Mbps |
| 240p–720p at 30 fps | 3–8 Mbps | 4 Mbps |
These are platform recommendations, not guarantees that every connection or encoder can sustain the listed value. YouTube also updates its technical guidance, so creators should check the current encoder settings page before a major production.
Video bitrate and audio bitrate
Most streaming software lists video and audio bitrate separately.
- Video bitrate carries the visual information and accounts for most of the upload demand.
- Audio bitrate carries the microphone, music, game audio, and other sound sources.
YouTube currently recommends 128 Kbps for stereo audio and 384 Kbps for supported 5.1 surround sound. Setting a video bitrate to 6 Mbps and audio to 128 Kbps creates a feed slightly above 6 Mbps before protocol overhead and normal variation are considered.
Why YouTube recommends CBR
YouTube's current live encoder guidance recommends constant bitrate, commonly shown as CBR. CBR tells the encoder to target a relatively consistent data rate instead of allowing large long-term swings.
The encoded stream will not use the exact same number of bits for every frame. Complex motion still needs more data than a static image. The purpose of CBR is to keep the overall outgoing rate predictable enough for live delivery and platform ingestion.
How to choose a stream bitrate
- Choose the resolution and frame rate that the production actually needs.
- Confirm which codec the encoder and YouTube ingest workflow support.
- Start within YouTube's recommended range for that combination.
- Leave meaningful upload headroom rather than using the connection's entire advertised capacity.
- Test with the same movement, audio, overlays, and hardware planned for the real stream.
- Watch stream health in Live Control Room and the encoder during the test.
- Lower the bitrate, frame rate, or resolution if the connection cannot sustain the feed reliably.
Fast-moving games and sports expose compression artifacts more easily than a mostly static presentation. They may benefit from the upper part of a supported range, but only when the connection and encoder remain stable.
What happens when bitrate is too high or too low?
| Problem | Common symptoms | Likely response |
|---|---|---|
| Bitrate is too high for the connection | Network-dropped frames, unstable stream health, disconnects, delay growth | Lower bitrate or improve the upload path |
| Bitrate is too low for the video | Blockiness, smearing, lost detail during motion | Raise bitrate within YouTube's guidance or reduce resolution/frame rate |
| Bitrate is high but encoder is overloaded | Encoding lag, skipped frames, high CPU/GPU load | Use a faster preset, hardware encoder, or lighter scene |
| Bitrate fluctuates because the connection is unstable | Intermittent warnings and viewer buffering | Use wired networking, remove competing traffic, or reduce the target rate |
A high bitrate cannot repair a poor source image, bad lighting, an out-of-focus camera, or an overloaded encoder. It only gives the compression process more data to work with.
Bitrate and stream latency
Bitrate and stream latency are separate settings, but they affect one another operationally. YouTube warns that network congestion can delay a stream even when the connection can sustain its average bitrate. Lower-latency modes also have less playback buffer available to hide short network problems.
For ultra-low latency, a stable bitrate is especially important because ingestion problems are more visible to viewers. Choosing a slightly lower, sustainable bitrate can produce a better experience than pushing for maximum image quality.
Common stream bitrate mistakes
- Copying another creator's bitrate without matching their resolution, codec, content, or connection.
- Treating advertised upload speed as guaranteed usable capacity.
- Raising bitrate to solve an encoder-performance problem.
- Using a high resolution with too little bitrate for fast motion.
- Changing settings immediately before a live event without a realistic test.
- Assuming all viewers receive the same bitrate sent by the creator.
Creator finances handled by someone who gets YouTube.
Tax prep and bookkeeping built for YouTubers — every income stream, every deduction, done right.
Tax Services for Creators Bookkeeping for CreatorsFrequently asked questions
What bitrate should I use for a 1080p YouTube live stream?
YouTube's current H.264 guidance recommends 10 Mbps for 1080p30 and 12 Mbps for 1080p60. Its AV1/H.265 ranges are 3–8 Mbps for 1080p30 and 4–10 Mbps for 1080p60. The connection and encoder must be able to sustain the selected rate.
Is a higher stream bitrate always better?
No. More bitrate can reduce compression artifacts, but an unsustainable rate causes instability, dropped frames, or disconnects. It also cannot fix poor source quality or encoder overload.
Is bitrate the same as upload speed?
No. Bitrate is the rate the encoder sends. Upload speed is the connection's available capacity. The available upload speed should exceed the stream's combined video, audio, and overhead demand with room for normal fluctuations.
Does YouTube change my stream bitrate for viewers?
YouTube transcodes the incoming stream into multiple output formats. Viewers can therefore receive different resolutions and playback bitrates based on their device, selected quality, and connection.