For YouTube Live, choose the recommended ingest bitrate that matches your resolution, frame rate and video codec. Then check that the network carrying the stream can sustain the total upload rate with headroom; the encoder value is not the bitrate every viewer will receive.
The figures below are YouTube’s recommended video bitrates for a live stream sent to YouTube. They are not settings for encoding a prerecorded file to upload. YouTube transcodes live video for viewers, so a sensible ingest setting is a starting point, not a guarantee of a particular playback quality or resolution.
Use live-ingest recommendations, not upload settings
A live encoder continuously sends video to YouTube while the broadcast is running. Its bitrate is the rate at which that incoming stream is encoded. The right YouTube Live bitrate depends on the format you are sending: resolution, frames per second and codec all matter.
A prerecorded upload is a different workflow. You encode a file, then transfer it to YouTube; that file’s encoding bitrate is not the same thing as a live encoder’s recommended ingest bitrate. YouTube’s live encoder settings and its recommended upload encoding settings have separate guidance. For example, the upload page recommends 8 Mbps for standard-frame-rate 1080p uploads, while the live table recommends 10 Mbps for 1080p30 using AV1 or H.265, or 14 Mbps using H.264.
That difference is easy to miss when a channel uses prerecorded material as the content for a live broadcast. The video may have been rendered in advance, but once an encoder sends it as a live stream, the relevant values are the live-ingest recommendations. If you are setting up a recurring broadcast, keep the file’s export settings and the live encoder’s output settings as two separate decisions. The guide to running a prerecorded YouTube Live stream on Airtel Broadband is useful for thinking through that distinction in a real streaming workflow.
YouTube live bitrate by resolution and frame rate
The table shows YouTube’s recommended video bitrate for the incoming live stream. Values are in Mbps. AV1 and H.265 share the recommendation shown in the middle column; H.264 has its own value. The minimum figures are included for context, but a minimum is not the same as the recommended starting point.
| Live resolution and frame rate | AV1 or H.265 recommended | H.264 recommended | AV1/H.265 minimum | H.264 minimum |
|---|---|---|---|---|
| 1080p30 | 10 Mbps | 14 Mbps | 4 Mbps | 5 Mbps |
| 1080p60 | 12 Mbps | 17 Mbps | 4 Mbps | 6 Mbps |
| 1440p30 | 15 Mbps | 21 Mbps | 5 Mbps | 7 Mbps |
| 1440p60 | 24 Mbps | 34 Mbps | 6 Mbps | 8 Mbps |
| 2160p / 4K30 | 30 Mbps | 42 Mbps | 8 Mbps | 11 Mbps |
| 2160p / 4K60 | 35 Mbps | 50 Mbps | 10 Mbps | 14 Mbps |
For a straightforward 1080p30 stream encoded in H.264, use 14 Mbps as the YouTube-recommended starting point. For 1080p60 H.264, the recommendation is 17 Mbps. If the encoder is set to AV1 or H.265 instead, the corresponding recommendations are 10 and 12 Mbps. The resolution and frame rate may appear unchanged in the settings panel, but changing the codec changes the recommended ingest bitrate.
For live 4K, also called 2160p, YouTube’s recommendations are 30 Mbps at 30 fps and 35 Mbps at 60 fps for AV1 or H.265. With H.264, the corresponding figures are 42 and 50 Mbps. Those higher rates have practical consequences for upload capacity, so do not choose 4K simply because the source file is 4K. Choose it only if the encoder and connection can keep sending the selected format reliably.
The minimum columns describe lower bounds in YouTube’s table, not a promise that a stream running at the minimum will look as intended for your material. A static devotional image, a lofi animation and fast-moving footage place different demands on encoding, but the table’s recommended value is the sensible place to begin. If you need to reduce the rate because your upload connection cannot sustain it, consider stepping down resolution or frame rate rather than assuming the minimum will suit every scene.
Compare AV1 and H.265 with H.264
YouTube lists AV1 and H.265 (HEVC) together for these recommended bitrate values, while H.264 has a separate set. At the same resolution and frame rate, the AV1/H.265 recommendation is lower. For example, YouTube recommends 12 Mbps for 1080p60 AV1 or H.265, compared with 17 Mbps for H.264. The bitrate difference is useful when planning upload capacity, but it does not by itself determine which codec your setup should use.
Your encoder must support the chosen codec, and the receiving workflow must be configured to send it correctly. H.264 is widely supported in streaming tools and is often the most familiar setting to operators. If your available encoder offers only H.264, use the H.264 column rather than selecting a lower AV1/H.265 value on the assumption that the numbers are interchangeable. A codec setting that your encoder cannot produce is not a practical bandwidth saving.
If AV1 or H.265 is available and stable in your encoder, its lower recommended live bitrate may make a higher-resolution or higher-frame-rate choice more workable on a limited upload connection. That is a trade-off, not a guarantee: the encoder still has to process the stream, and the connection still needs margin for audio and other traffic. Compare like with like in the table, then test the actual configuration.
YouTube’s live settings page also lists CBR encoding, RTMP or RTMPS, and a two-second keyframe interval, with the interval not exceeding four seconds. It recommends RTMPS where supported. These are part of the ingest configuration, alongside bitrate; changing codec alone does not replace the need to use a supported protocol and keyframe setting. For HDR over RTMP(S), YouTube recommends H.265, and its guidance says AV1 is not supported for HDR. If you are configuring HDR, check the current official live encoder requirements rather than carrying over SDR assumptions.
Choose a setting your encoder and stream can sustain
Start by identifying the actual output format in your encoder, not just the source file’s properties. Confirm the output resolution, frame rate and codec, then read across the matching row in the table. A 1080p source sent at 30 fps is not the same ingest format as 1080p60; likewise, a 4K file downscaled to 1080p is a 1080p live stream if that is what the encoder outputs.
Next, decide whether the higher frame rate is useful for the content. A channel showing a still image, lyrics or a slow visual loop may have little reason to send 60 fps. Sports, gameplay or quick camera movement may benefit more from a higher frame rate, if the encoder and upload connection can manage it. This is not a quality guarantee: the setting describes the video you send, while the result seen by viewers depends on YouTube’s processing and playback conditions as well.
Use the recommended rate for your chosen row as the first configuration to test. Avoid combining a 60 fps target with an upload connection that only has room for a 30 fps stream, or choosing 4K because the table has a larger number that sounds like a quality target. A lower resolution at a stable recommended bitrate can be a more practical choice than a higher one that repeatedly drops frames or disconnects.
For a 24/7 channel, stability is part of the format decision. A short test during a quiet period may not represent a busy evening, a shared household connection or an ISP slowdown. If you run an encoder from a computer, also check whether its processing load stays reasonable during a representative scene. Operators using OBS can refer to this guide on checking a YouTube stream that is at risk despite stable OBS bitrate, since a stable encoder number does not rule out other ingest or network problems.
Check upload capacity and stability
The bitrate in the table is video, but your connection has to carry the stream’s total outgoing traffic, including audio and any additional stream data. YouTube Help advises that total streaming bitrate must not exceed available upload bandwidth and recommends leaving 20% headroom. A shared network can reduce the capacity available to your encoder, so do not plan around a download-speed figure or a package’s headline speed alone.
A simple planning calculation is to take the total stream bitrate and allow the recommended margin on top. For example, a 17 Mbps video stream needs more than 17 Mbps of available upload capacity: audio and other traffic add to the total, and the connection should retain headroom. YouTube’s 20% advice is a margin to preserve, not an assurance that a line reading slightly above the encoder setting will remain stable throughout the night.
Check outbound speed from the network and location that will actually carry the broadcast. If you stream from a shop, home or studio, run the check on that connection, ideally at times when it is normally busy as well as quiet. Pause other uploads during a test, then consider what will share the connection during the real broadcast: cloud backups, video calls, CCTV uploads or another live stream can all compete for capacity. A speed test is a snapshot, not a guarantee of overnight stability.
Before committing to a bitrate, run a representative test with the intended resolution, frame rate, codec and audio. YouTube’s guidance on testing and stream health says tests should include movement and audio similar to the planned stream. A still screen test alone may conceal the impact of motion; test a busy visual section and listen for audio issues. Then check YouTube’s stream health indicators during the test and after going live.
If the stream drops or health warnings appear, do not respond only by raising bitrate. A higher value increases the upload demand. Check whether the outgoing network is shared, whether the encoder output matches the selected row, and whether the connection is fluctuating. If reliable capacity is insufficient, use a lower resolution or frame rate, or choose a codec the encoder supports that has a lower recommended bitrate. The article on OBS disconnections and network settings in India covers other connection checks that may help when a stream struggles despite apparently adequate nominal speed.
What viewers receive after YouTube transcodes
The bitrate you configure is the incoming stream sent to YouTube. YouTube then transcodes live video into output formats for viewers using different devices and network conditions. Viewers may be offered different playback resolutions or rates; they do not all receive the exact encoder bitrate you selected.
That distinction matters when diagnosing what someone reports on a phone or television. A viewer’s playback quality can depend on the stream’s available renditions, their device and the connection at that moment. Your encoder setting establishes the input, but it does not force every viewer to see 1080p or 4K, nor does a 50 Mbps 4K60 ingest setting mean each viewer downloads video at 50 Mbps.
The useful operator task is to make the ingest feed consistent and monitor the broadcast, not to promise an identical result across viewers. Share the resolution and frame rate you are sending when explaining the setup, and avoid describing the encoder bitrate as the audience’s playback rate. If you are running a prerecorded loop continuously, the same rule applies: looping a high-resolution file does not override the live format and network capacity used to send it. A practical guide to looping prerecorded videos into YouTube Live with FFmpeg can help with that separate playback workflow.
There is also a latency trade-off at 4K. YouTube says the low-latency option is unavailable for 2160p live streams, which are optimised for quality and set to normal latency. Lowering or raising the bitrate does not unlock low latency at 4K. If fast audience interaction matters more than a 4K feed, decide on the resolution and latency mode as separate requirements before building the schedule around them.
For a channel that needs a prerecorded video to keep broadcasting while your own computer is off, StreamNeo removes the overnight burden of keeping a local encoder and connection running. It does not change YouTube’s ingest recommendations or the way YouTube transcodes for viewers, so you still need to prepare the file and channel for the intended broadcast.
A practical configuration sequence
Work through the choices in order rather than adjusting several encoder fields at once. First settle the content and output resolution. Next choose 30 or 60 fps based on the movement viewers need to see. Then select a codec that the encoder supports, and take the bitrate from the corresponding YouTube row. Configure CBR and the keyframe interval, then set RTMPS where the tool supports it.
Once the encoder is configured, check the actual outbound capacity and allow room for the total stream rate and other network use. Test with realistic content and audio, inspect stream health, and note any warnings before relying on the setup for a long broadcast. If a test is unstable, change one meaningful variable at a time: reduce resolution, reduce frame rate, or choose a supported codec with a lower recommended rate. Retest after each change.
Keep a note of the final settings so that a restart or a second operator does not quietly change the output format. Record the chosen resolution, frame rate, codec and bitrate together, rather than writing down “1080p” alone. A setting saved in an encoder can be invalidated by changing a scene profile, source or output preset, so verify it after updates or major configuration changes. For a long-running music or devotional channel, the bitrate is one part of a dependable routine that includes the source material, audio continuity, connection and monitoring.
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 1080p60 YouTube Live?
YouTube recommends 17 Mbps for H.264 at 1080p60, or 12 Mbps for AV1 or H.265. Match the value to the codec your encoder actually sends, and leave upload headroom beyond the stream’s total bitrate.
What is YouTube’s recommended bitrate for 4K live streaming?
For 2160p30, YouTube recommends 30 Mbps with AV1 or H.265 and 42 Mbps with H.264. For 2160p60, the figures are 35 Mbps and 50 Mbps respectively. These are live-ingest recommendations, not playback rates promised to viewers.
Is YouTube’s upload bitrate the same as its live bitrate?
No. A prerecorded upload is encoded as a file before it is transferred, while a live encoder sends an ongoing stream to YouTube. Use YouTube’s separate live-ingest table for a broadcast, even when the live content is a prerecorded video.
Does a higher encoder bitrate make every viewer watch in 4K?
No. YouTube transcodes the incoming stream into formats for different devices and network conditions. The encoder bitrate describes the input you send, not the exact bitrate or resolution every viewer receives.