Use YouTube’s codec-specific ingest recommendations as your starting point: at 1080p60, YouTube recommends 12 Mbps for AV1 or H.265 and 17 Mbps for H.264. At 1080p30, the recommendations are 10 Mbps for AV1 or H.265 and 14 Mbps for H.264.
Those figures are platform recommendations, not a universal AV1-to-H.264 quality conversion. Choose the row matching your resolution and frame rate, confirm that your encoder and protocol support the codec, leave upload headroom, and test with the sort of movement your channel will actually show.
YouTube’s codec-specific recommendations
YouTube’s live encoder settings page groups AV1 and H.265/HEVC together in its bitrate table. That does not mean the two codecs behave identically in every encoder or scene. It means YouTube publishes one set of recommended ingest values for that group and another for H.264.
The table below shows YouTube’s listed minimum and recommended ingest bitrates. These are the rates sent from your encoder to YouTube, not the separate versions YouTube creates for viewers.
| Ingest resolution and frame rate | AV1/H.265 minimum | AV1/H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 4K / 2160p at 60 fps | 10 Mbps | 35 Mbps | 14 Mbps | 50 Mbps |
| 4K / 2160p 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 |
The minimum column is not a second recommended target. It is useful when checking whether a particular output is within YouTube’s listed range, but starting at the minimum can leave less room for difficult motion, fine detail and encoder variation.
For the current official settings, see YouTube’s live encoder settings. Check that page again before changing a production setup, because platform guidance can change.
YouTube also lists CBR bitrate encoding, progressive scan, square pixels and a two-second recommended keyframe frequency. The keyframe interval should not exceed four seconds. Those settings sit alongside bitrate; changing only the bitrate does not make an otherwise unsuitable encoder configuration reliable.
1080p bitrate by frame rate
For most small always-on channels, the useful comparison is 1080p rather than 4K. A devotional loop, local news bulletin, study timer or ambience video may not need 4K, and the higher resolution also asks more of the encoder and upload connection.
At 1080p60, YouTube’s recommended ingest values are:
- AV1 or H.265: 12 Mbps
- H.264: 17 Mbps
At 1080p30, the recommended values are:
- AV1 or H.265: 10 Mbps
- H.264: 14 Mbps
The frame-rate change matters because 60 frames per second gives the encoder twice as many pictures to describe as 30 frames per second. It can make scrolling text, gameplay, camera movement and fast transitions look smoother, but it also changes the bitrate row you should use.
If your source is a mostly static black-screen rain stream, 30 fps may be a sensible starting point. If the channel includes a presenter moving across a set, a sports feed, a game replay or a news ticker that travels continuously, 60 fps may be more appropriate if your encoder and connection can sustain it.
You can use the YouTube live stream bitrate calculator to organise the resolution and frame-rate choice before you configure the encoder. Treat any calculator as a planning aid, then verify the result against YouTube’s current official table.
The same distinction applies at other resolutions. YouTube recommends 35 Mbps for AV1/H.265 at 2160p60 and 50 Mbps for H.264 at that frame rate. At 720p60, the listed recommendations are 6 Mbps and 8 Mbps respectively. These differences show how the official table varies by both codec and output format; there is no single bitrate that fits every live stream.
Do not read the table as saying that selecting AV1 automatically gives you the same picture as H.264 at a particular lower rate. It tells you where YouTube suggests you begin. Your source material, encoder implementation, preset, motion and upload stability still affect the result.
Why the numbers are not an equal-quality conversion
The most common mistake in this comparison is to turn the table into a formula. For example, someone sees 12 Mbps for AV1 and 17 Mbps for H.264 at 1080p60 and concludes that AV1 always needs a fixed proportion of the H.264 bitrate. YouTube’s settings page does not establish that conversion.
A bitrate is the amount of encoded data sent over time. A codec decides how that data is arranged and compressed, but the final appearance also depends on the encoder, its settings and the content being encoded. A still image, a slow devotional visualisation, a fast game and a busy street camera do not place the same demands on an encoder.
Consider two 1080p streams. The first shows a nearly static background with a small amount of text. The second shows a camera panning across a crowded market while a ticker and lower-third graphics move at the same time. Even if both are configured at the same resolution and frame rate, the second scene may expose blocking, smearing or loss of detail sooner.
The official values are therefore best described as starting points for ingest. They are not a controlled AV1-versus-H.264 quality test, and they do not promise that one codec will look better at an equal bitrate. They also do not guarantee that reducing the bitrate after switching codecs will preserve every detail in your particular video.
YouTube says it detects the encoder settings and transcodes the live stream into different output formats for viewers. Your ingest codec is the format you send to YouTube. It is not necessarily the format every viewer receives. A viewer on a slower connection may receive a different playback rendition created by YouTube.
This distinction helps with troubleshooting. If your encoder reports that it is sending 12 Mbps AV1 but viewers see a lower-quality rendition, that does not automatically mean your ingest setting is wrong. You should check the stream health, the available playback quality and the source material separately.
The practical rule is simple: use YouTube’s matching recommendation, then judge the result using an actual sample of your content. Do not promise yourself an equal-quality conversion merely because the table lists lower AV1/H.265 values than H.264.
Check encoder and protocol support first
Before choosing AV1, confirm that the encoder you plan to use can produce AV1 for a live stream at the selected resolution and frame rate. Codec support is not guaranteed merely because a computer has a modern graphics card, camera or media player. The application, hardware encoder and driver path all matter.
YouTube lists RTMP and RTMPS as the live ingest protocols and lists H.264, H.265/HEVC and AV1 as video codecs. Your encoder must support the combination you intend to send. If the application only exposes H.264 for its live output, selecting AV1 in a separate export setting will not change the live stream.
Check these items in the encoder’s live-output panel:
- Video codec: AV1 or H.264, matching your chosen plan.
- Rate control: CBR, as listed in YouTube’s encoder settings.
- Frame rate: 30 or 60 fps, matching the YouTube table row.
- Keyframe interval: two seconds recommended, and no more than four seconds.
- Output dimensions: the intended progressive resolution.
- Protocol: RTMP or RTMPS, as supported by the application and YouTube ingest path.
For SDR, YouTube lists Rec. 709 and 8-bit settings. It lists 10-bit for HDR, but its current settings page says AV1 is not supported for HDR. Do not choose AV1 for an HDR workflow on the assumption that it will provide the same support. If HDR is essential, review YouTube’s current guidance and the supported codec path before configuring the stream.
At 3840×2160 and above, YouTube calls for at least two tile columns for AV1 streams. That is a specialised setting, so check how your encoder exposes it rather than guessing. If the application does not provide the required control or behaves unpredictably, H.264 or another supported workflow may be the more practical choice for that production.
An encoder can be software running on a general-purpose computer or a standalone hardware device. You do not need expensive equipment simply because a codec is available, but you do need an encoder that can maintain the selected settings without overloading. A dropped frame caused by an overloaded encoder is not solved by choosing a lower network bitrate alone.
If your workflow brings an external HDMI camera or console into a computer, a capture device may be needed before encoding. That is a source-ingest requirement, not an AV1 requirement. YouTube’s encoder guidance can help you check the broader workflow, while the encoder manufacturer’s documentation should confirm its actual codec support.
Match bitrate to stable upload capacity
Your download speed is not the number that matters when you send a live stream. The relevant figure is stable outbound upload capacity at the location and time where the stream will run. YouTube says the total stream bitrate cannot exceed available upload bandwidth and recommends leaving 20% headroom.
That headroom is not spare quality to spend on extra video. It is room for normal variation and other traffic. A connection advertised with a high download rate may have a much smaller upload rate, and a shared household or office network may reduce what remains for the encoder.
For example, if you select the 12 Mbps AV1 recommendation for 1080p60, the connection must support more than the stream’s nominal video rate in practice. Audio and other network activity also need consideration. Apply YouTube’s headroom guidance rather than treating 12 Mbps as the full capacity your connection needs.
The same logic applies to H.264 at 17 Mbps. Switching to H.264 because an application supports it does not remove the upload requirement. In fact, YouTube’s recommended H.264 value for this example is higher, so it may be the less comfortable choice on a constrained connection.
If you configure a primary and backup stream, account for both when checking capacity. YouTube’s streaming guidance also points to headroom when applicable to the stream arrangement. A backup path that shares the same limited connection may not provide the protection you expect.
Run an upload test from the actual network rather than relying on a plan name. Repeat it at a time when other people or devices are likely to use the connection. For a 24/7 channel, consider the quiet overnight period as well as the busiest daytime period. The goal is not a single impressive reading; it is a connection that remains suitable when ordinary household or business traffic is present.
If the connection cannot comfortably sustain the recommended rate, reassess the resolution or frame rate. A stable 720p stream is more useful than an unstable 1080p stream that repeatedly loses connection. You can also test the other supported codec, but do not assume that changing codec alone will fix an upload problem.
This is also where the operating model matters. A computer that must stay awake can be affected by power cuts, sleep settings, updates or local network changes. If you want the file and stream to continue without leaving your own computer running, StreamNeo removes the need to keep that local playback process operating, while you still need to configure the YouTube ingest settings and check the channel’s health.
For a longer discussion of keeping a channel running through local interruptions, see how to restart a 24/7 ambient stream after a power cut in India. The codec decision and the continuity decision are related, but they are not the same problem.
Test representative motion before going live
A bitrate test using a still frame can give false confidence. YouTube’s own guidance says tests should include audio and movement similar to what you will use in the stream. That is especially important when comparing AV1 and H.264, because the difficult parts of a scene may not appear in a quiet opening frame.
Build a short test from the real source file or an equivalent sample. For a bhajan or devotional channel, include the most detailed artwork, animated lyrics, transitions and any scrolling text. For a lofi or ambience station, include rain, water, film grain, smoke or other moving textures rather than testing only the static title card.
For a local news loop, include the busiest lower thirds, ticker movement, map animation and a camera shot with people moving through the frame. For a gaming channel, use the section with fast camera movement, particle effects and small interface text. A test should represent the hardest ordinary material, not an unusually simple scene.
Compare the two codecs at their recommended YouTube ingest values for the same resolution and frame rate. Look for:
- Text that becomes difficult to read during movement.
- Blocks or smearing in faces, water, foliage and dark areas.
- Sudden changes when a transition or scene cut occurs.
- Encoder overload, dropped frames or unstable frame timing.
- Audio interruptions and any stream-health warnings.
Do not compare a short local recording only. Send a private or otherwise controlled test through the same YouTube ingest path you plan to use, then inspect the resulting playback at the available qualities. YouTube transcodes live streams, so the result on the platform is more useful than a file viewed only inside your encoder.
Keep notes for each test: codec, resolution, frame rate, bitrate, keyframe interval, encoder preset and network conditions. This makes a later change traceable. If you change three settings at once, you will not know whether the improvement came from the codec, the bitrate or the encoder load.
For a looped ambience stream, audio is another failure point. A video may continue while the audio source falls silent after a loop or loses synchronisation. The guide on fixing an ambience stream that loses audio after looping covers that separate issue and is worth checking before you treat a quiet test as a codec problem.
The final test should run long enough to expose the behaviour you care about, including reconnects or source changes if those are part of the workflow. You cannot prove that a stream will never fail, but you can find obvious encoder, network and content problems before the public broadcast.
A practical selection checklist
Use this order rather than starting with the codec label:
- Choose the output resolution and frame rate. Base that on the source, the viewer’s likely use and the amount of movement, not on the highest setting your encoder displays.
- Read the matching row in YouTube’s table. Record both the minimum and recommended value, but use the recommended value as the initial target.
- Check protocol and codec support in the actual encoder. Confirm that AV1 or H.264 is available for live output, not only for file exports.
- Check the rate-control and keyframe settings. Use CBR and the keyframe guidance listed by YouTube unless your tested workflow requires a different supported configuration.
- Measure stable outbound upload capacity. Leave the 20% headroom YouTube recommends and account for other traffic or a backup stream.
- Test with representative movement and audio. Inspect the platform result, not only the local preview.
- If the test is unstable, reduce the resolution or frame rate, change the encoder path or address the network before assuming the codec is at fault.
Choose AV1 when your tested encoder supports it reliably, the ingest path is suitable and the lower YouTube recommendation fits your upload plan. Choose H.264 when it is the better-supported or more predictable option in your existing workflow. Neither choice removes the need for a suitable connection and a representative test.
If you are building a continuous video loop rather than running a live camera production, first make sure the source file itself repeats cleanly. The black-screen rain sounds and FFmpeg guide is relevant to that type of channel, but its workflow should still be tested against the same YouTube bitrate and encoder requirements.
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 AV1 always better than H.264 for YouTube Live?
No. YouTube lists lower recommended ingest bitrates for AV1/H.265 than for H.264, but that is not a universal equal-quality conversion or a guarantee that AV1 will look better in every stream. Encoder support, scene movement, settings and upload stability still matter.
What bitrate should I use for 1080p60?
YouTube’s listed recommendation is 12 Mbps for AV1 or H.265 and 17 Mbps for H.264. Use the matching value as a starting point, then check that your stable outbound connection can sustain it with the recommended headroom and test your actual content.
Can I use AV1 for an HDR live stream?
YouTube’s current encoder settings page says AV1 is not supported for HDR. Review the current official requirements before choosing a codec for HDR, and do not assume that an AV1 SDR workflow can simply be changed to HDR.
Should I lower bitrate or resolution when the stream is unstable?
First check whether the encoder is overloaded or the upload connection lacks stable capacity. If the selected settings cannot be sustained, reassess resolution or frame rate and test again; changing codec alone does not guarantee a stable stream.