The best bitrate for YouTube Live depends on the resolution and frame rate you send to YouTube, as well as whether your encoder uses H.264 or AV1/HEVC. Choose the matching recommended value in YouTube’s live-stream table, then check that your upload connection can sustain it with headroom.
A bitrate is not a promise of stability or a universal speed threshold. YouTube lists both minimum and recommended values, and advises testing the connection and choosing a quality it can reliably support.
Choose a bitrate for the stream you are sending
Start with the encoder output, sometimes called the ingest or input stream. It is the video that travels from your encoder to YouTube, before YouTube processes it for viewers. If your source file is 4K but your encoder sends 1080p, use the 1080p row. If the encoder sends 1080p at 60 frames per second, use the 1080p60 row, not 1080p30.
Then match the codec. YouTube’s live encoder guide gives different values for H.264 and a grouped AV1/H.265 column. These recommendations are not interchangeable: for example, YouTube lists different recommended bitrates for 1080p30 H.264 and 1080p30 AV1 or H.265. If you are unsure which codec your software is sending, check the video encoder setting rather than guessing from the file type.
The table below reproduces YouTube’s current live-stream recommendations, checked on 3 October 2026. Values are Mbps, shown as minimum / recommended. They are guidance for live-stream ingestion, not the separate settings for uploading a finished video. YouTube’s guide does not show a separate H.265 column; it groups H.265 with AV1. Check the official live encoder settings guide before a broadcast, since platform guidance can change.
| Ingest resolution and frame rate | AV1 / H.265: minimum / recommended | H.264: minimum / recommended |
|---|---|---|
| 2160p (4K) at 60 fps | 10 / 35 Mbps | 14 / 50 Mbps |
| 2160p (4K) at 30 fps | 8 / 30 Mbps | 11 / 42 Mbps |
| 1440p at 60 fps | 6 / 24 Mbps | 8 / 34 Mbps |
| 1440p at 30 fps | 5 / 15 Mbps | 7 / 21 Mbps |
| 1080p at 60 fps | 4 / 12 Mbps | 6 / 17 Mbps |
| 1080p at 30 fps | 4 / 10 Mbps | 5 / 14 Mbps |
| 720p at 60 fps | 2 / 6 Mbps | 3 / 8 Mbps |
| 720p at 30 fps | 2 / 6 Mbps | 3 / 8 Mbps |
| 480p at 30 fps | 0.3 / 3 Mbps | 0.4 / 4 Mbps |
| 360p at 30 fps | 0.3 / 3 Mbps | 0.4 / 4 Mbps |
A minimum is not the same as the recommended target, and neither column tells you how fast your internet package should be on its own. The bitrate is only one part of the stream’s upload demand; audio and network variation matter too. Use the recommendation as a settings starting point, then test the complete stream over the connection and at the time you intend to broadcast.
Match the resolution and frame rate
Resolution describes the dimensions of the video frame, while frame rate describes how many frames are sent each second. More pixels or more frequent frames generally require more data to represent clearly, which is why the YouTube table separates 30 fps from 60 fps at many resolutions. A channel showing a mostly static devotional image may not need the same frame rate as a sports or gaming stream with frequent motion, but choose according to what the encoder actually sends and what viewers need to see.
For a common example, YouTube recommends 14 Mbps for 1080p30 H.264 and 10 Mbps for 1080p30 AV1 or H.265. At 1080p60, those recommendations are 17 Mbps and 12 Mbps respectively. If you make a 1080p60 setting change but leave the encoder output at 30 fps, the 60 fps row does not describe the signal you are sending. Verify the output resolution and frame rate in the encoder, not only the project or source-file properties.
At 720p, YouTube recommends 8 Mbps for H.264 and 6 Mbps for AV1 or H.265 at both 30 and 60 fps. This does not mean frame rate has no effect in every situation; it means those particular published recommendations are the same. At 4K60, the recommended values rise to 50 Mbps for H.264 and 35 Mbps for AV1 or H.265. Before choosing 4K because the source is high-resolution, consider whether your connection can sustain the relevant target and whether the additional detail matters for the channel.
If you are preparing a looping video rather than encoding a live camera feed, the output file and the live encoder still have distinct roles. A guide to encoding files for continuous YouTube streaming can help you distinguish an efficient source file from the settings used to send a live signal. Do not assume that a file’s existing bitrate is automatically the correct live ingest bitrate.
H.264 bitrate recommendations
H.264 is a widely supported choice in streaming software and encoders. Use the H.264 column when that is the codec selected for the video sent to YouTube. For example, a 720p30 H.264 stream has a YouTube recommendation of 8 Mbps, while 1080p30 H.264 is 14 Mbps. Moving up to 1440p30 is 21 Mbps, and 4K30 is 42 Mbps in the same table.
Those values are not a demand to maximise quality at any cost. A 4K H.264 stream may be a poor practical fit if your measured upload capacity is variable or shared with other household activity. A lower resolution that remains stable can be more useful than a nominally sharper stream that repeatedly loses connection. Decide based on the visible content, audience devices and actual upload conditions, then test the chosen setting.
For a channel that mostly shows a still image, lyrics or a slow-moving background, it is worth checking whether 60 fps has a visible benefit before selecting it. A more active scene may benefit from the smoother motion, but a higher frame rate can raise the recommended ingest bitrate. The decision is not simply “higher is better”: it is a balance between the picture you want and the connection your setup can sustain.
AV1 and HEVC recommendations
AV1 and HEVC (also called H.265) have their own grouped column in YouTube’s live bitrate table. At 1080p30, its recommended value is 10 Mbps, compared with 14 Mbps for H.264. At 1080p60, the values are 12 Mbps and 17 Mbps respectively. Follow the column for the codec your encoder actually sends; do not select the lower number just because it appears in the AV1/H.265 column if the stream is H.264.
Codec support depends on your encoder and workflow, so a setting that appears in a software menu is not, by itself, proof that the whole path is configured correctly. Check the chosen codec, YouTube’s current support notes and stream health during a test. For HDR, YouTube recommends H.265 and says AV1 is not supported for HDR in its encoder guidance. If you are producing HDR, check the official guide for the current requirements rather than adapting SDR settings by assumption.
The AV1/H.265 recommendations can make these codecs an appealing option when your encoder supports them and the rest of the workflow is compatible. The practical trade-off is that you must confirm the encoder’s output and YouTube’s acceptance, as well as the upload capacity. A lower recommended bitrate does not remove the need for a stable connection or a representative test.
Check upload capacity and leave headroom
Compare the stream’s total bitrate with available upload bandwidth, not the download speed shown in a broadband advert. YouTube says that the total stream bitrate must fit within the available upload bandwidth and recommends leaving 20% headroom over the stream bitrate. That margin is guidance from YouTube’s streaming tips, not a separate codec-specific minimum or guarantee of reliability. See YouTube’s streaming tips for the network guidance.
For example, if the video setting is 10 Mbps, the 20% margin means you should plan for more upload capacity than 10 Mbps; also account for audio and variation in the connection. Do not treat a speed test result taken once as a guarantee that the same capacity will be available all night. Other people using the network, Wi-Fi conditions and changes in service can affect the capacity available to the stream.
Run a speed test that measures upload, preferably from the same location and connection as the streaming device. Repeat it at a time resembling the planned broadcast if your network is busy at particular hours. YouTube notes that upload bandwidth can be lower than download bandwidth and that other people sharing a connection can reduce what is available to you. If the result is marginal, reduce resolution, frame rate or bitrate and test again rather than hoping the stream will hold.
For computer-based streaming, YouTube recommends an Ethernet connection. This is a practical way to remove some Wi-Fi variation, but it does not increase the capacity supplied by your internet connection or guarantee that every interruption disappears. If you need a cable to connect the computer to the router, a Cat 6 Ethernet cable is one possible accessory; YouTube’s guidance supports Ethernet generally, not a specific cable category or brand. More network troubleshooting is covered in this guide to OBS stream disconnections and network settings in India.
Configure and verify the encoder
Once you have chosen the ingest resolution, frame rate and codec, check the rest of the encoder settings. YouTube’s RTMP/RTMPS guidance recommends RTMPS, constant bitrate (CBR), and a keyframe interval of two seconds; do not exceed four seconds. It lists H.264, H.265 and AV1 as video codec options. For audio, the guide lists AAC or MP3, with AAC supported for 5.1 surround over RTMP/RTMPS. Use the current official settings guide for further advanced parameters.
A short checklist helps catch mismatches before they become overnight problems:
- Confirm the encoder’s output resolution and frame rate. Match those exact values to the table.
- Confirm the video codec that will be sent. Select its column, not the codec you intended to use.
- Set the video bitrate to the corresponding recommended starting point, then check that total stream bitrate fits measured upload capacity with headroom.
- Use CBR and a two-second keyframe interval, following YouTube’s published guidance.
- Verify audio, protocol and any HDR/SDR settings against YouTube’s current encoder guide.
- Test a stream with audio and movement similar to the real broadcast, then watch stream health before relying on the setup.
YouTube specifically advises testing before going live with audio and movement similar to the intended broadcast. A static image test may not reveal all the issues that appear when a video has motion or the audio is active. Its filming tips for live streams also recommend testing audio, video and equipment in an unlisted live stream, and recommend Ethernet for streaming from a computer.
During the test, look at the stream health indicators and check for unstable connection warnings, dropped frames or audio problems. If you change an encoder value, repeat the test; one successful test at a lower bitrate does not validate a higher setting. If you are building a 24/7 setup that depends on a desktop staying powered and connected, think about how you will notice and recover from a drop. StreamNeo can remove the need to leave your own computer running for a file-based YouTube broadcast, while the bitrate and stream checks still need to match your channel and connection.
For 2160p (4K), YouTube notes that the low-latency option is not available; those streams are optimised for quality at normal latency. That matters if you are comparing a 4K configuration with a lower-resolution interactive stream. Do not assume every resolution offers the same latency controls. Likewise, encoder settings do not settle rights or channel eligibility questions; check the relevant official YouTube guidance for those separately.
A final practical check is to record the working settings somewhere you can find them after an interruption: resolution, frame rate, codec, bitrate, audio and keyframe interval. If you switch from H.264 to AV1 or H.265, or change the output frame rate, revisit the relevant table row instead of carrying over an old number. If you are choosing between OBS and another encoder, this comparison of YouTube Live encoder alternatives may help you evaluate the workflow, but the same matching and upload checks apply whichever encoder you use.
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 at 1080p?
It depends on frame rate and codec. YouTube’s recommended value is 14 Mbps for 1080p30 H.264 or 10 Mbps for AV1/H.265; for 1080p60, it is 17 Mbps for H.264 or 12 Mbps for AV1/H.265. Check the output your encoder sends and make sure your upload connection can sustain the total stream bitrate with headroom.
Is YouTube’s recommended bitrate a required minimum?
No. The guide lists separate minimum and recommended values, and recommends choosing a quality your connection can reliably support. A recommendation is a useful starting point, not a promise that the connection will remain stable.
Should I use H.264, AV1 or HEVC?
Use a codec supported by your encoder and workflow, and then follow its column in YouTube’s live table. The published table groups AV1 and H.265 together rather than giving H.265 its own column. For HDR, YouTube recommends H.265 and says AV1 is not supported for HDR, so check the current guide if you are configuring HDR.
Is download speed enough to check before a 24/7 stream?
No. The relevant measure is available upload capacity, because the stream is sent from your encoder to YouTube. Test upload speed on the connection you will use, leave YouTube’s recommended headroom, and test with representative audio and motion before relying on the setup.