YouTube Live ingest guide
Choose bitrate from YouTube’s current ingest contract, then prove your real upload path
YouTube bitrate is not one universal number. The current recommendation depends on the codec, resolution and frame rate sent by the encoder. The safe production choice must also fit the sustained uplink, the content and every relay between the source and YouTube.
What bitrate should you use for YouTube Live?
For H.264 ingest, YouTube currently lists 10 Mbps for 1080p30, 12 Mbps for 1080p60, 15 Mbps for 1440p30, 24 Mbps for 1440p60, 30 Mbps for 2160p30 and 35 Mbps for 2160p60. Its 720p recommendations are 4 Mbps at 30 fps and 6 Mbps at 60 fps. These are platform recommendations, not a promise that your connection or encoder can sustain the profile.
Use the official matrix below as the destination guidance: a range for AV1 or H.265 and a recommended value for H.264. If the measured path cannot carry the chosen profile with headroom, reduce frame rate or resolution and test again rather than forcing an unstable bitrate.
The moving samples illustrate a sustained flow through the route; they do not report a measured rate. Motion is disabled for users who request reduced motion.
YouTube’s current live bitrate matrix
| Ingest resolution and frame rate | AV1 / H.265 minimum | AV1 / H.265 maximum | H.264 recommended |
|---|---|---|---|
| 2160p at 60 fps | 10 Mbps | 40 Mbps | 35 Mbps |
| 2160p at 30 fps | 8 Mbps | 35 Mbps | 30 Mbps |
| 1440p at 60 fps | 6 Mbps | 30 Mbps | 24 Mbps |
| 1440p at 30 fps | 5 Mbps | 25 Mbps | 15 Mbps |
| 1080p at 60 fps | 4 Mbps | 10 Mbps | 12 Mbps |
| 1080p at 30 fps | 3 Mbps | 8 Mbps | 10 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps | 6 Mbps |
| 240p–720p at 30 fps | 3 Mbps | 8 Mbps | 4 Mbps |
YouTube presents AV1 and H.265 as a minimum-to-maximum setting range, while the H.264 column is a recommended value. Do not mix the columns. A 10 Mbps H.264 1080p30 recommendation and a 3–8 Mbps AV1/H.265 range describe different codec paths.
The official YouTube encoder-settings page is the source of truth. Recheck it before each important production because the platform can revise codecs, ranges and constraints without changing your saved OBS profile.
Keep the rest of the profile consistent
Bitrate is only one field in YouTube’s current live contract. The same first-party guidance specifies CBR, a recommended two-second keyframe frequency that must not exceed four seconds, progressive scan, square pixels and up to 60 fps. It lists H.264, H.265 and AV1 for video ingest, with AAC or MP3 audio in the RTMP/RTMPS path.
For ordinary SDR production
- Keep the source, OBS canvas and output aspect ratio deliberate.
- Use Rec. 709 and 8-bit only when that matches the complete SDR chain.
- Configure a two-second keyframe interval and CBR for the YouTube output.
- Test fine detail, movement and gradients, not only a static talking-head frame.
For HDR, AV1 or H.265
- Confirm that the encoder, transport, Callaba route and YouTube entry point all support the selected codec and bit depth.
- Use YouTube’s separate current HDR and HLS guidance; do not infer HDR compatibility from an SDR H.264 test.
- Verify color metadata and playback on an HDR-capable device as part of acceptance.
- Keep a tested SDR fallback when the event cannot tolerate an experimental codec path.
For the broader trade-offs behind a profile, use the streaming bitrate guide. For a detailed 1080p planning decision, use the 1080p bitrate guide. Those pages explain general bitrate behavior; this page stays focused on YouTube’s current ingest requirements.
Do not size the stream from a single speed-test result
- Test the production network. Use the wired or bonded path, router, firewall and service that will carry the event. An office test on another ISP is not venue evidence.
- Exercise representative content. Include camera movement, detailed slides, gameplay or playback rolls, music and the full audio mix.
- Run long enough to expose variation. Short bursts can hide congestion, thermal limits, mobile-path changes and competing uploads.
- Watch both sender and receiver evidence. In OBS, distinguish encoding or rendering lag from network-dropped frames. In YouTube Live Control Room, require a stable preview and resolve health warnings.
- Leave headroom. The complete video and audio program plus protocol behavior and other traffic must fit below the sustained capacity available to the production.
If OBS reports dropped frames, the official OBS stream-connection guide treats them as a network path problem between the computer and ingest. For the exact OBS control and rate-selection method, use the OBS bitrate guide.
Publish directly when one YouTube destination is enough
- Enable live streaming on the channel before the production day; YouTube warns that first-time enablement may take time.
- In YouTube Studio, open Live Control Room and create or select the intended stream.
- Use the YouTube service connection in the encoder when appropriate, or copy the current stream URL and stream key into the matching encoder fields.
- Apply the approved codec, raster, frame rate, bitrate, keyframe and audio settings.
- Start the encoder, wait for the Live Control Room preview and health result, then use the platform’s current go-live control when the selected workflow requires it.
- At the end, follow the current platform sequence and confirm that the session has actually stopped.
YouTube’s official encoder workflow distinguishes first-time setup from a returning stream and explains the current Live Control Room sequence. Treat the stream key like a publishing credential. If it appears in a screenshot, chat message or public document, reset it and update the sender.
Use Callaba when YouTube is one controlled destination
If the same verified program must reach YouTube and other services, or if the production needs a managed contribution boundary, start with Callaba Multi-Streaming. OBS or another encoder sends one contribution to Callaba; a dedicated restream then publishes the approved output to YouTube.
- Prove the source at Callaba. Require stable incoming media, decoded picture and the intended audio before opening the YouTube route.
- Create one YouTube destination. Follow the Callaba Restreaming user guide and use the exact destination values supplied by YouTube.
- Pass through when the source already conforms. Transcode only for a documented mismatch. Every extra encode adds capacity, quality and recovery considerations.
- Compare the actual outgoing profile with the YouTube row. A correct OBS profile does not prove a transformed downstream output retained the intended settings.
- Open YouTube’s preview. Verify picture, audio, health, event identity and latency behavior at the platform, not only in Callaba.
For the complete stream-key and RTMPS task, continue with the YouTube stream-key setup through Callaba. Keep the YouTube key on its destination route, not in the OBS-to-Callaba publisher field.
Diagnose bitrate symptoms at the right boundary
| Symptom | What it suggests | First action |
|---|---|---|
| OBS reports dropped frames | The sender cannot sustain the network path to its ingest at the configured rate. | Measure the path, competing traffic and alternate approved endpoint before changing YouTube metadata. |
| OBS reports encoding overloaded | The system cannot render or encode the current scene and profile in time. | Reduce competing GPU load, scene cost, frame rate or raster; bitrate alone may not repair it. |
| Callaba input is stable but YouTube warns about bitrate | The outgoing profile or destination route differs from YouTube’s expected contract. | Inspect that route’s actual output, including any transcoding, then compare it with the current official row. |
| YouTube accepts the stream but motion looks blocky | The profile may be too demanding for its codec and rate, or the source already contains artifacts. | Compare a local recording, Callaba preview and YouTube preview. Test a lower frame rate or raster rather than only adding bits. |
| Viewers buffer although ingest health is clean | The issue may be downstream of ingest or limited to a viewer path or device. | Test several controlled playback networks and devices; preserve healthy ingest evidence. |
| The wrong YouTube event receives the feed | A reused or mismatched stream key selected another stream configuration. | Stop safely, verify the event and key in Live Control Room, then update the intended destination. |
Automate after the profile and route are approved
When a scheduler or customer system must create destination routes, use the Callaba Restreams API workflow after the same route has passed manual acceptance. Store the approved source, destination type and profile as versioned operational data. Make retries idempotent so they do not create duplicate outputs.
A successful API response confirms a requested state change. It does not confirm the YouTube preview, live health, audio program, event identity or audience playback. Keep those checks in the release gate.
Official references
- YouTube: choose live encoder settings, bitrates and resolutions — current bitrate matrix and encode requirements.
- YouTube: create a live stream with an encoder — current Live Control Room and encoder sequence.
- YouTube: manage live stream settings — stream keys, reset behavior and latency controls.
- OBS: stream connection troubleshooting — network dropped-frame isolation.
Frequently asked questions
Is 6 Mbps enough for YouTube 1080p60?
It is below YouTube’s current 12 Mbps H.264 recommendation for 1080p60. The official AV1/H.265 range for that raster and cadence is 4–10 Mbps. Do not use the codec range for an H.264 encode. If the path cannot sustain the H.264 recommendation, test a lower frame rate or raster.
Should YouTube bitrate be set to CBR or VBR?
YouTube’s current live encoder guidance specifies CBR. A recording or VOD workflow may make another rate-control decision, but that is not the YouTube Live ingest contract described here.
Does YouTube transcode a live stream for viewers?
YouTube says it automatically transcodes live input into multiple output formats. That does not excuse an unstable or non-conforming ingest. The source still has to reach YouTube reliably and pass current health checks.
Does Callaba change the bitrate automatically?
Do not assume it does. A pass-through route preserves the compatible source behavior, while an intentionally configured transcoding workflow can create another output profile. Verify the actual route configuration and decoded result.
Approve the profile with motion, audio and a real route
Select the current YouTube row, prove the encoder locally, sustain the production uplink and require a clean Live Control Room preview before the event becomes public.
Plan a managed YouTube destination