Bitrate is the amount of video data your encoder sends to YouTube each second. There is no single bitrate that suits every live stream: choose the recommendation for the codec, resolution and frame rate you are sending, then make sure your connection can sustain it.
For common H.264 formats, YouTube recommends 14 Mbps for 1080p at 30 fps, 17 Mbps for 1080p at 60 fps, and 8 Mbps for 720p at either frame rate. AV1 and H.265/HEVC have separate recommendations, so do not carry an H.264 figure over to another codec.
What bitrate means for a live stream
The encoder turns your video into a stream of data and sends it to YouTube. Bitrate describes how much data is sent per second; it is usually shown in kilobits per second (Kbps) or megabits per second (Mbps). A higher target gives the encoder more data to represent detail and movement, but also asks more of the upload connection.
Bitrate is not the same thing as resolution or frame rate. Resolution describes the number of picture dimensions, while frame rate describes how many frames are sent each second. Two streams with the same resolution may need different bitrate targets if one sends more frames or uses a different codec. YouTube’s live encoder settings organise recommendations around those outgoing format choices.
A bitrate setting is a target, not a guarantee of picture quality or an assurance that a stream will remain connected. If the connection cannot sustain the outgoing data rate, YouTube may receive an uneven stream, which can show up as buffering or problems in stream health. Conversely, raising the target beyond what the source video needs does not restore detail that was absent from the original file.
For a pre-recorded devotional loop, for example, a still image with a small amount of movement is not the same visual workload as a camera showing a busy stage. The recommended target still comes from the format you send, but testing with the actual programme helps reveal whether the complete setup behaves as expected. For a broader view of continuous playback choices, see how cloud playout works.
Choose bitrate by codec, resolution and frame rate
Start by reading the outgoing settings in your encoder rather than guessing from the video file’s name or from a tutorial for a different setup. Note the codec, resolution and frame rate. A file may have been encoded one way for storage, while the live encoder sends it in another format. It is the format sent to YouTube that matters for the live ingestion recommendation.
Then use YouTube’s matching codec column and the row for the resolution and frame rate you are sending. The same resolution does not always mean the same recommendation: the H.264 guidance differs between 1080p at 30 fps and 1080p at 60 fps. And changing from H.264 to AV1 or HEVC means checking that codec’s recommendation rather than assuming the H.264 figure applies.
The source material also matters to the result you see. A static background may look acceptable at a lower effective data rate than footage with rapid motion, fine detail, or scrolling text, but that does not authorise substituting an arbitrary number for YouTube’s recommendation. Use the official figure as the reference for the selected format, then judge the test for visible quality and stability. If the source is already soft or compressed, a larger bitrate cannot recreate missing detail.
Resolution is another practical choice, not a quality shortcut. Sending 1080p asks for a different recommended H.264 rate than sending 720p, and your viewer may not benefit if the original content is only a small graphic or low-resolution recording. If you prepare playlists from several clips, check that their transitions and audio are representative; this guide to building a YouTube playlist without a gap addresses continuity rather than bitrate, but both affect how a long-running channel feels to viewers.
H.264 recommendations at a glance
These are YouTube’s current recommended H.264 video bitrates for the listed common live formats, as shown in its live encoder settings. They are recommendations for the encoder’s video stream, not a promise that a connection can sustain the rate and not a universal setting for all codecs.
| Ingest format | YouTube recommended H.264 video bitrate |
|---|---|
| 1080p at 60 fps | 17 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 720p at 60 fps | 8 Mbps |
| 720p at 30 fps | 8 Mbps |
YouTube also lists minimum settings. For example, its minimum H.264 entry is 6 Mbps for 1080p at 60 fps and 5 Mbps for 1080p at 30 fps. A minimum is not the same as the recommended target: treat it as a lower boundary in that table, not as the best starting point simply because it is easier on a connection.
The table does not cover every possible format or circumstance. If you use a different codec, consult that codec’s column in the official guidance. If your encoder offers a frame rate or resolution different from the rows above, do not interpolate a number from this small table; look up the current official recommendation. For a channel built around a consistent 720p loop, the specific 720p 30 fps bitrate guide can help put that format in context, but verify current values against YouTube’s page.
It is also easy to confuse live ingestion advice with recommendations for uploaded videos. Upload and live workflows are different. YouTube’s separate video upload encoding recommendations include figures for uploaded files; do not use those numbers as a substitute for the live encoder table.
Why AV1 and HEVC use separate recommendations
A codec is the method used to compress video. H.264, AV1 and H.265/HEVC represent video differently, so the bitrate guidance is not interchangeable. YouTube lists separate recommendation columns for supported live codecs. If you choose AV1 or HEVC in the encoder, read the corresponding official column for your resolution and frame rate rather than applying the H.264 rows above.
This matters in practice because a setting copied from another channel may have been chosen for a different codec even if the picture size looks identical. Check the actual output codec in your software and confirm that YouTube supports the selected combination. Its live encoder guidance covers H.264, H.265/HEVC and AV1 for the listed RTMP/RTMPS settings, with frame rates up to 60 fps. Check the current official page if your encoder or workflow offers a combination not described there.
Choosing a codec is not just a matter of selecting the smallest possible bitrate. Your encoder must support it reliably, and your own workflow has to be able to send the selected stream. A codec choice can also affect compatibility with other tools in the chain. If you are troubleshooting an existing channel, change one setting at a time and test the output rather than simultaneously changing codec, frame rate, resolution and bitrate.
For an always-on channel, consistency has practical value. A stable 720p format may be a better fit than a higher-resolution target that repeatedly exceeds the available upload capacity. The right answer is the highest format you can sustain reliably while matching the recommendation for its codec, resolution and frame rate—not a blanket rule that everyone should use a particular resolution.
Fit the target to your outbound connection
The encoder’s target must fit the connection’s available upload bandwidth. YouTube’s streaming tips advise leaving 20% headroom. In other words, the available outbound capacity needs to cover the stream while retaining room rather than running continuously at the edge of what the connection can send.
Think about the capacity available to the streaming device, not only the headline speed of the internet plan. Other people or devices may be uploading files, making calls or backing up data at the same time. A shared connection can vary through the day. Test the actual upload path at the time and place you plan to stream, and include any other stream using that same outbound connection.
YouTube’s advice also accounts for a backup stream where one is being sent: the primary stream, backup stream and headroom together must fit within available outbound capacity. If you are not using a backup, do not add one to the calculation. If you are, remember that it also consumes upload capacity rather than being free redundancy.
For example, do not conclude that a recommended 17 Mbps target for H.264 1080p60 will work just because a speed test once displayed a higher download number. Download capacity is not upload capacity, and a brief test does not prove a sustained connection. Check upload performance, avoid saturating it with other activity, and test for long enough to catch the conditions likely during a real broadcast. If that target is not sustainable with the required headroom, consider a lower resolution or a more suitable connection and consult the recommendation for the format you then send.
This is particularly important when your computer is also playing a local playlist, uploading media, or sharing a household connection. Before relying on a machine-based setup overnight, review the operational trade-offs in platforms for 24/7 YouTube streaming. If repeated network or power interruptions make your own computer the weak point, StreamNeo can remove the need to keep that computer running after you upload the video and provide the stream key; it does not change the need to select a suitable YouTube bitrate or verify the stream.
Set the encoder bitrate
In your encoder, locate the live video output settings and set the codec, resolution, frame rate and video bitrate as a coherent group. Use the official recommendation for that combination. Do not confuse the video bitrate with the audio bitrate, and do not use a total bitrate figure as though it were the video-only number in YouTube’s table. The stream’s total data use includes audio as well as video, so leave room for both when checking the connection.
YouTube lists constant bitrate (CBR) as the live bitrate encoding mode. It recommends a two-second keyframe interval and says not to exceed four seconds. These are separate encoder controls: bitrate controls the rate of video data, while keyframes affect points at which a frame can be decoded independently. Set them according to the official live guidance rather than trying to compensate for a poor bitrate target by changing keyframe settings.
YouTube also recommends RTMPS for secure delivery to its servers. Your encoder may present several protocol or server options; use the current instructions in YouTube Live Control Room and the supported settings for your workflow. A protocol selection is not a way to reduce the amount of video data needed for the chosen codec and format.
Once set, write down the combination that worked. For instance, record the codec, resolution, frame rate and bitrate alongside any relevant connection conditions. That makes it easier to restore a known configuration after an encoder update or a change of computer. If a channel uses several scenes or sources, confirm that they all pass through the intended output settings, rather than relying on settings from a different profile.
Test the stream and adjust carefully
YouTube advises testing before going live with audio and movement similar to the planned stream. A static test slide may not expose problems that appear when the programme has a moving camera, animated text, a scrolling ticker or a changing visualiser. Include representative audio too, since the live programme sends more than video.
Start a private or otherwise suitable test using the same encoder, connection, content and schedule conditions you expect to use. Watch YouTube’s stream health and messages, and check the output on a viewer device if possible. Look for interrupted delivery, warnings, buffering, missing audio, or visibly degraded detail. A successful short test is useful evidence, but it does not guarantee a long overnight session will encounter the same network conditions.
If the test shows instability, diagnose before changing everything. Confirm the encoder is sending the codec and format you intended. Check whether other devices are using upload capacity. Review YouTube’s health messages, then adjust the format or connection as appropriate. If you lower resolution or frame rate, look up the matching recommendation again; do not keep a bitrate selected for a previous format by habit.
Change one thing at a time where possible and repeat the test. This makes it clearer whether a result followed from reducing resolution, changing codec, easing network use, or correcting an encoder setting. Keep a short record of the test and the working values. For a 24/7 channel, repeat a test after substantial changes to source media, encoder software, connection or output profile, and check health during the live run rather than assuming yesterday’s result still applies.
Bitrate and latency are related operating decisions, but they are not the same setting. YouTube defines latency as the time from capture by the encoder or camera until the event appears to viewers. Lower latency can increase the risk of playback buffering, so it may be less useful for a non-interactive bhajan or ambience channel than for a live presenter answering viewers. See YouTube’s latency guidance and choose based on whether conversation needs to be near real time. Latency does not make an unsuitable bitrate sustainable.
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?
Use the recommendation for the codec, resolution and frame rate your encoder sends, then check that the total stream fits within available upload bandwidth with headroom. There is no one bitrate that applies to every YouTube Live stream. For H.264, the common recommendations in this article are 14 Mbps for 1080p30, 17 Mbps for 1080p60 and 8 Mbps for 720p30 or 720p60.
What bitrate is recommended for 1080p at 60 fps?
For H.264, YouTube’s current live encoder recommendation is 17 Mbps. Do not apply that number automatically to AV1 or HEVC: check the matching codec column in YouTube’s live encoder settings and ensure your upload connection can sustain the selected rate with room for other stream data and headroom.
Is YouTube’s minimum bitrate the recommended bitrate?
No. The minimum is a separate entry in the official table and should not be mistaken for the recommendation. For example, YouTube lists a 6 Mbps H.264 minimum for 1080p60 and a 5 Mbps minimum for 1080p30, while its recommended rates are higher.
Does a higher bitrate reduce buffering?
Not necessarily. A higher target sends more data and can make buffering or delivery problems more likely if the connection cannot sustain it. Choose the format-specific recommendation that fits your upload capacity, test representative content, and monitor stream health while live.