YouTube Live Bitrates for 720p, 1080p, 1440p and 4K

For a stable YouTube Live broadcast, choose the resolution and frame rate whose complete stream fits comfortably within your measured upload capacity. Start with YouTube’s bitrate guidance for your codec, reserve substantial network headroom, include audio in the budget and step down the format if the connection cannot sustain the resulting load.

For H.264, YouTube currently specifies recommended settings from 4 Mbps for 720p30 to 35 Mbps for 4K60. Treat those figures as encoder targets rather than proof that your connection can carry them: measure the production connection repeatedly and validate the selected profile with representative audio and motion before the public broadcast.

Separate platform compatibility from upload capacity

Two limits govern the choice. YouTube’s ingestion specification identifies the bitrate associated with each codec, resolution and frame rate, while your real upstream connection determines whether the complete feed can remain stable. Meeting the platform specification does not guarantee sufficient network capacity.

YouTube explains that its bitrate guidance depends on ingestion codec, resolution and frame rate. Its table provides one recommended setting for H.264 and minimum-to-maximum ranges for AV1 and H.265, so confirm the active codec before copying a value into your encoder.

Measure the connection from the production computer, through the same router and network path that will carry the broadcast. Repeat the test at representative times and use the lowest result that recurs, rather than the highest result from a single run. Leave room for remote guests, cloud synchronization, other users and any backup workflow that shares the upstream connection.

Use YouTube’s current table for the starting bitrate

YouTube Live encoder profiles compare resolution, frame rate and the upload capacity each bitrate requires.

For an H.264 feed, configure the following official video-bitrate targets. Audio and other network traffic must still fit within the overall upload budget.

AV1 and H.265 use ranges instead of the H.264 point recommendations. YouTube’s published AV1 and H.265 ranges are 3–8 Mbps for 720p30, 720p60 and 1080p30; 4–10 Mbps for 1080p60; 5–25 Mbps for 1440p30; 6–30 Mbps for 1440p60; 8–35 Mbps for 4K30; and 10–40 Mbps for 4K60.

Do not combine tables without checking their codec and publication period. The July 2022 Telestream Lightspeed guide lists ranges of 3,000–6,000 Kbps for 1080p30 and 4,500–9,000 Kbps for 1080p60. Those figures describe an older product guide rather than YouTube’s current H.264 table, which is why saved production presets should record their codec and verification date.

Choose frame rate according to the content

Use 30 fps as the conservative choice for interviews, podcasts, lectures, software demonstrations and mostly static presentations. It reduces the required H.264 bitrate at every resolution in YouTube’s table and gives you more room to preserve resolution on a constrained connection.

Choose 60 fps when gameplay, sport, rapid camera movement or detailed physical action makes smoother motion important. The network cost depends on resolution: YouTube’s H.264 targets rise from 10 to 12 Mbps at 1080p and from 15 to 24 Mbps at 1440p when the frame rate moves from 30 to 60 fps.

Resolution should follow the actual visual requirement. Small interface text may justify 1440p when the source and upload path support it, whereas an interview may gain little from an unstable 4K feed. On a limited connection, a verified 720p30 profile is preferable to a higher format that produces network-related dropped frames.

Reserve upload headroom before choosing the preset

Repeated upload measurements are converted into a conservative video-bitrate ceiling after audio is reserved.

Restream advises that the configured stream bitrate should not exceed half of the available upload speed; its illustrative rule turns 10 Mbps upstream into a 5 Mbps ceiling. This is a conservative rule of thumb, not a guarantee that every access network will behave the same way.

For planning, use maximum video bitrate = lowest repeatable upload result × 0.5 − configured audio bitrate. The one-half allowance comes from Restream’s upload-headroom recommendation; using the lowest repeatable result is an additional editorial safeguard against selecting a profile from an unusually favorable speed test.

YouTube’s advanced encoder table lists 128 Kbps for stereo audio and 384 Kbps for 5.1 surround. Convert the selected audio rate to the same units as the upload result before subtracting it, then compare the remaining video budget with the relevant codec row.

If the calculated ceiling falls below YouTube’s H.264 target, do not assume that entering an arbitrary lower value will preserve the intended format. Move to a lower frame-rate or resolution preset whose published target fits. With AV1 or H.265, you may instead choose a value within the official range, subject to encoder support and a successful private test.

Use conservative presets for common productions

The following presets are practical recommendations based on YouTube’s current H.264 values. They solve an insufficient upload budget by changing the format rather than presenting an unofficial H.264 bitrate as a platform recommendation.

Interview or presentation: start with 1080p30 at 10 Mbps if it fits the safe budget; otherwise use the official 720p30 target of 4 Mbps.
Motion on a constrained connection: choose 720p60 at 6 Mbps when smooth movement matters more than fine detail.
Detailed but slower material: favor 1080p30 over 720p60 when small text or facial detail matters more than motion, provided the 10 Mbps H.264 target fits.
High-motion Full HD: use 1080p60 at 12 Mbps only after the complete feed clears the upload calculation.
High-resolution production: allow for YouTube’s 24 Mbps target at 1440p60 or 35 Mbps at 4K60. If the safe ceiling is lower, reduce frame rate when motion permits and then reduce resolution if necessary.

For AV1 or H.265, begin in the lower portion of the applicable official range for relatively static material and allocate more bitrate to complex motion or fine texture. Increase it only after checking the delivered picture and stream health; that selection method is editorial advice, not an additional YouTube requirement.

Configure the settings that accompany bitrate

Bitrate is only one part of the encoder profile. YouTube’s encoder table lists CBR and recommends a two-second keyframe interval, with the interval not to exceed four seconds.

For SDR, the same advanced-settings table specifies progressive scan, square pixels and Rec. 709. It lists AAC or MP3 for audio, a 44.1 kHz stereo sample rate and a 128 Kbps stereo bitrate.

Select RTMPS when the encoder supports it. YouTube recommends RTMPS for encrypted live ingestion, and the platform says the data remains encrypted on its path into and through Google’s servers. Keep the stream key private and confirm that the encoder’s output codec, resolution and frame rate match the intended profile.

Consider latency before committing to 4K. YouTube states that 4K streams cannot use its low-latency optimization and are set to normal latency, which matters when rapid interaction with viewers is central to the event.

Verify the complete path with a private stream

A speed test cannot validate the encoder, scene complexity and ingest path together. YouTube’s pre-stream guidance calls for testing with representative audio and movement and monitoring stream-health messages during the event. Restream’s broader guide also advises creators to test upload conditions and connected equipment in private mode.

Create a private or unlisted test event and confirm the stream key, codec, resolution and frame rate.
Use the busiest expected scenes: move the camera, play demanding gameplay, switch layouts, share small text and connect remote guests.
Run the test across ordinary network fluctuations instead of stopping after the first clean minute.
Watch the encoder’s network, dropped-frame, rendering and encoding indicators. Network warnings implicate the upload path, while rendering or encoding lag calls for checking the production computer and scene load.
Inspect YouTube’s stream-health messages and watch the delivered feed from another connection. Check motion, text, lip synchronization and audio continuity.
If the connection is unstable, choose a value within the applicable AV1 or H.265 range or move H.264 to the next verified lower format.
Save the working preset with its codec, resolution, frame rate, video rate, audio rate and test location clearly identified.

Prepare a verified fallback

Create at least one lower profile before the broadcast begins. A conditional H.264 ladder might move from 1440p60 to 1440p30, then 1080p30 and 720p30; YouTube’s corresponding targets are 24, 15, 10 and 4 Mbps.

Test the fallback through the same path, keep its audio and keyframe settings consistent, and define the stream-health warning or sustained network condition that will trigger the switch. The practical target is the highest format your complete production can sustain throughout the event, not the largest resolution reached during one speed test.

YouTube Live Bitrate Settings: Choose 720p, 1080p, 1440p or 4K Without Overloading Your U‑