Use YouTube’s live-ingest bitrate table by matching three settings: resolution, frame rate and codec. The result is a video bitrate target for sending a live broadcast to YouTube, not a recommendation for encoding a finished upload and not the full amount of network traffic.
For a reliable 24/7 channel, choose the matching recommended value, then check whether your measured upload connection can sustain the video, audio and any other stream traffic with room to spare. If it cannot, reduce resolution or frame rate rather than assuming that a faster download result will help.
How to use this live bitrate calculator
Start by identifying the output you intend to send to YouTube. For example, a devotional loop might be 1080p at 30 frames per second, while a gaming channel could use 1080p at 60 fps. A local news loop with mostly static graphics may not need the same frame rate as fast gameplay, even if both are shown at the same resolution.
Next, identify the codec selected in your encoder. H.264 is still common in desktop encoders and hardware devices. YouTube’s live guidance also lists H.265/HEVC and AV1. The codec matters because YouTube publishes different minimum and recommended live-ingest values for the same resolution and frame rate.
Use the table below as follows:
- Find the intended resolution and frame rate.
- Read the column for the codec your encoder actually uses.
- Treat the minimum as a lower boundary, not the normal target.
- Prefer the recommended value when your upload connection can sustain it.
- Add audio and network headroom before deciding whether the connection is suitable.
If you do not know which codec your encoder is using, check its output settings rather than guessing from the computer’s processor or graphics card. The codec shown in the encoder is the one that determines which column applies.
YouTube says resolution and frame rate are detected automatically by default. If you need to select them manually, its guidance describes creating a custom stream key and enabling manual settings under Stream Resolution. Read the current YouTube live encoder settings and bitrate guidance before changing less familiar encoder options.
A calculator result does not decide whether your content is suitable for a 24/7 broadcast, whether your music and visuals are cleared for use, or whether a particular stream will be accepted. It answers the narrower question: what video bitrate should the encoder send for this live-ingest combination.
Codec, resolution and live-ingest bitrate basics
Bitrate is the amount of encoded data sent over time. In this article, every bitrate in the table is a video bitrate for the incoming live stream. It does not include audio, a backup stream, other devices on the connection, protocol overhead or unrelated network use.
Resolution describes the image dimensions, such as 1920 by 1080 for 1080p. Frame rate describes how many frames are sent each second. More pixels and more frames generally require more data to preserve detail and motion, but the encoder and codec also affect the result. That is why a single “best YouTube bitrate” number is misleading.
Codec is the method used to compress the video. H.264, H.265/HEVC and AV1 do not produce identical results at the same bitrate. YouTube therefore separates its live-ingest recommendations by codec. Selecting the H.264 figure for an AV1 stream, or the AV1/H.265 figure for an H.264 stream, gives you the wrong target.
These figures should not be carried over to uploaded videos. YouTube maintains separate guidance for uploading finished video files, where the file has already been encoded and is not being sent as a continuous live broadcast. A prerecorded video that you upload to YouTube and a prerecorded video that you send through a live encoder are different workflows.
For live ingestion, YouTube lists CBR, or constant bitrate, as the recommended bitrate mode. CBR keeps the encoder aiming at a steadier rate instead of allowing large short-term swings. That is useful for a long-running channel because an occasional complex scene still has to fit within the connection’s available capacity.
YouTube also recommends a keyframe interval of two seconds and says it should not exceed four seconds. A keyframe is a complete reference image from which following frames can be decoded. The interval is separate from the bitrate: changing it does not turn a low upload connection into a high-capacity one.
For audio, YouTube’s guidance lists AAC or MP3. It gives 128 kbps for stereo audio and 384 kbps for 5.1 surround, with 44.1 kHz listed for stereo and 48 kHz for 5.1 surround. Keep these audio settings separate from the video number. They add to the total stream bandwidth.
Recommended live bitrate by resolution, frame rate and codec
The following values are YouTube’s published live-ingestion minimum and recommended video bitrates. Mbps means megabits per second. Select the pair that matches the codec in your encoder.
| Resolution and frame rate | AV1/H.265 minimum | AV1/H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 2160p (4K) at 60 fps | 10 Mbps | 35 Mbps | 14 Mbps | 50 Mbps |
| 2160p (4K) at 30 fps | 8 Mbps | 30 Mbps | 11 Mbps | 42 Mbps |
| 1440p at 60 fps | 6 Mbps | 24 Mbps | 8 Mbps | 34 Mbps |
| 1440p at 30 fps | 5 Mbps | 15 Mbps | 7 Mbps | 21 Mbps |
| 1080p at 60 fps | 4 Mbps | 12 Mbps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 4 Mbps | 10 Mbps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 720p at 30 fps | 2 Mbps | 6 Mbps | 3 Mbps | 8 Mbps |
| 480p at 30 fps | 0.3 Mbps | 3 Mbps | 0.4 Mbps | 4 Mbps |
| 360p at 30 fps | 0.3 Mbps | 3 Mbps | 0.4 Mbps | 4 Mbps |
For the common question “what bitrate should I use for YouTube live at 1080p 60fps?”, the answer depends on the codec. YouTube lists 17 Mbps as the H.264 recommended video bitrate and 12 Mbps as the AV1/H.265 recommended video bitrate. At 1080p 30fps, the corresponding recommendations are 14 Mbps for H.264 and 10 Mbps for AV1/H.265.
At 720p, the published recommended values are 8 Mbps for H.264 and 6 Mbps for AV1/H.265, for both 30 and 60 fps in this table. That does not mean the two frame rates look identical in every scene. It means these are the values YouTube lists for the corresponding live-ingest combinations.
For 4K at 60 fps, YouTube lists 50 Mbps for H.264 and 35 Mbps for AV1/H.265. Those are video targets only. They are not promises that a connection advertised at either figure will be reliable once audio, overhead and other usage are included.
YouTube transcodes the incoming stream into multiple output formats for viewers. Your viewers may therefore watch at different qualities depending on their devices and connections. Sending a higher ingest resolution does not force every viewer to receive that same quality.
Minimum versus recommended bitrate
The minimum column is useful when diagnosing whether a particular encoder setting is within YouTube’s published range, but it is not the value to select automatically for a stable channel. A stream sent at the minimum may have less room to represent movement, fine text, smoke, water, foliage or fast camera changes.
The recommended column is the normal starting point when your encoder, source material and upload connection can support it. It is still a target for live ingestion, not a guarantee of picture quality. A poorly scaled source, an unsuitable frame rate, dropped frames or an unstable connection can harm the result even when the bitrate number is correct.
Consider a 1080p60 H.264 gaming stream. The table gives 6 Mbps as the minimum and 17 Mbps as the recommended video bitrate. Choosing 6 Mbps because it is the smaller number may reduce the data sent, but it leaves less room for fast movement and detailed scenes. Choosing 17 Mbps gives the encoder the recommended target, provided the measured upload capacity can carry the complete stream.
For a mostly static 24/7 information loop, you may decide that 720p30 is a more practical operating point than 1080p60. That is not because the table declares 720p universally better. It is because a lower output demand can be easier to sustain continuously, while the content may not benefit enough from the extra frames and pixels to justify the additional network requirement.
Do not compensate for a weak connection by entering a high resolution and then setting a much lower bitrate than the matching minimum. It is usually clearer to lower the resolution or frame rate and use the matching table row. This keeps the encoder configuration coherent and gives YouTube a signal closer to the format you intend to deliver.
Your source can also limit the sensible choice. A 30 fps video cannot gain real motion information by being sent as 60 fps. A small text overlay may benefit from a higher resolution, while a simple devotional background may not need 4K. Decide what viewers need to read or see, then apply the bitrate table to that output.
If you run OBS or another encoder yourself, the best OBS playlist method for looping devotional videos on YouTube Live in India is relevant to the content workflow, but its playlist advice does not replace this codec-specific bitrate check.
Add audio and network headroom
A video target is not the same as the connection capacity required by the broadcast. If the table gives you 14 Mbps for H.264 video, the connection must also carry audio and the small amount of additional traffic created by the streaming protocol. Other devices using the same connection can reduce what is available to the encoder.
YouTube’s streaming tips say that the total bitrate being streamed cannot exceed the available upload bandwidth and recommend leaving 20% of room. Treat that as a network planning rule, not as an extra 20% to add to the video bitrate field in the encoder. The encoder’s video field should remain the selected video target; the headroom belongs in your connection check.
For example, if your chosen video setting is 10 Mbps and stereo audio is 128 kbps, the stream is already above 10 Mbps before protocol overhead and other network use. You should not conclude that an upload test showing exactly 10 Mbps is sufficient. You need additional capacity so normal variation does not push the broadcast into instability.
If you use a primary and backup stream, the bandwidth requirement changes again. YouTube says its guidance recommends accounting for the primary stream, the backup stream and 20% room when both are active. A second stream is not free from a network perspective simply because it uses the same source video.
Upload speed is the relevant measurement here, not download speed. A household connection can show a strong download result while offering less upload capacity than a 24/7 encoder needs. Shared Wi-Fi, cloud backups, video calls, security cameras and other users can reduce the available upload bandwidth further.
Run the test in conditions close to the intended broadcast. If the channel will run overnight from a home connection, test while the household is operating normally rather than testing only when every other device is idle. YouTube specifically advises testing before going live with audio and movement similar to the intended broadcast.
A stream that stops after several hours may involve more than bitrate. The why is my FFmpeg YouTube stream stopping after a few hours guide covers other long-running failure points. Bitrate is still worth checking first because a connection that is close to its limit can turn ordinary variation into dropped frames or a disconnect.
Choose settings from measured upload capacity
Start with the content, not the speed-test result. Decide whether viewers need 4K, 1440p, 1080p or 720p, and whether motion justifies 60 fps. Then identify the codec and read the recommended video value from the table.
Now measure sustained upload capacity at the location and time where the channel will operate. Compare that result with the complete stream requirement: video, audio, protocol overhead, other household or business traffic, and the 20% room recommended by YouTube. The comparison must be made against upload capacity, not the advertised download figure.
If the result is comfortably above the complete requirement, test the actual encoder for a meaningful period. Watch YouTube’s stream health, look for dropped frames and inspect the Live Control Room preview. YouTube’s practical advice is direct: “Make sure to test before you start your live stream.”
If the result is close to the requirement, choose a less demanding row rather than relying on a perfect speed-test result. For example, move from 1080p60 to 1080p30, or from 1080p30 to 720p30, and use the matching codec values. This is a practical conclusion from YouTube’s bandwidth and reliability guidance, not a claim that one resolution is always preferable.
If the connection cannot sustain the selected setting, a cloud workflow can remove the need to keep your home computer and local upload connection running for the entire broadcast. StreamNeo removes that particular operational burden by letting you upload the file once, add your YouTube stream key and keep the channel running while your computer is switched off.
The same decision applies to an office, shop or place of worship. A connection may be fast enough for occasional manual streaming but unsuitable for an always-on channel if staff regularly use the upload capacity for calls, backups or other broadcasts. Planning around the lowest normal capacity is more useful than planning around the best result from one test.
Do not confuse bitrate planning with latency planning. YouTube describes lower latency as potentially causing more playback buffering and notes that it matters less when the creator does not interact with the audience. Its guidance also says 4K does not offer the “improve for low latency” option and is optimised for quality at normal latency. A bitrate calculator cannot choose the right latency mode for your audience or format.
HDR needs its own check. YouTube’s dedicated HDR instructions include HEVC, 10-bit video, compatible BT.2020 colour metadata and protocol or hardware conditions. The ordinary SDR table should not be treated as a complete HDR configuration. For advanced setups, consult YouTube’s HDR live streaming requirements and verify that the encoder and delivery method support the required signal.
Before committing to a long-running arrangement, test the exact file or scene type you intend to broadcast. A static image loop, a music visualiser, a news ticker and fast gameplay place different demands on motion and detail. Test audio as well as video, then review the stream health messages rather than judging the local preview alone.
If you are deciding between running software continuously and using a managed workflow, compare the operational details in OBS or a cloud service for a 24/7 church YouTube stream in India. The bitrate table remains the same question in either case: what signal is being sent to YouTube, and can the path sustain its complete requirement.
You can also review YouTube’s streaming tips before the first overnight test. YouTube suggests preparing ahead of the event, starting the encoder before the broadcast and checking the Live Control Room preview, audio, video and audience accessibility. These checks are operational rather than mathematical, but they are part of making the selected bitrate useful in practice.
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
Is YouTube live bitrate the same as upload-video bitrate?
No. The table in this article covers live ingestion: the video data your encoder sends continuously to YouTube. YouTube has separate guidance for finished video files that are uploaded and processed after the upload.
What bitrate should I use for 1080p60?
YouTube lists 17 Mbps as the recommended H.264 live video bitrate and 12 Mbps as the recommended AV1/H.265 live video bitrate at 1080p60. Check the codec in your encoder, then add audio, protocol overhead and YouTube’s recommended 20% network room when assessing upload capacity.
Does the bitrate include audio?
No. The table values are video bitrates only. Audio, such as YouTube’s listed 128 kbps stereo setting, contributes to the total bandwidth used by the stream.
Should I use the minimum or recommended value?
Use the recommended value when your measured upload connection can sustain the complete stream with room to spare. Use a lower resolution or frame rate if it cannot, rather than forcing a demanding output into an undersized connection.