For a 1080p, 30 fps YouTube Live stream, YouTube’s en-US encoder guidance recommends 14 Mbps for H.264, or 10 Mbps for H.265/HEVC and AV1. Those figures apply to the outgoing stream’s codec, resolution and frame rate; a prerecorded source does not get a separate bitrate recommendation.
These are ingest settings: the rate at which your encoder sends video to YouTube. They do not promise identical picture quality for every file, nor do they set the quality each viewer will receive. Set the output deliberately, leave upload headroom, and check stream health before relying on a long broadcast.
Find the 1080p30 row in YouTube’s table
Start with YouTube’s encoder settings and bitrate guidance. Its recommendations are organised by outgoing resolution, frame rate and codec. For 1920×1080 at 30 frames per second, use the row for the codec you will actually send, not a general figure labelled “1080p”.
| Outgoing video codec | Listed minimum at 1080p30 | Recommended at 1080p30 |
|---|---|---|
| H.264 | 5 Mbps | 14 Mbps |
| H.265/HEVC | 4 Mbps | 10 Mbps |
| AV1 | 4 Mbps | 10 Mbps |
The minimum and recommended figures are not interchangeable. The minimum is the lower listed threshold; the recommendation is the target to use when your connection and encoder can sustain it. Do not treat the minimum as a better efficiency setting simply because it is smaller.
These figures come from YouTube’s English-language guidance reviewed on 3 October 2026. YouTube may revise its recommendations, and language or regional versions of a page can differ. Before a new channel launch or a substantial settings change, check the current official page rather than relying on a screenshot or an old preset.
The table concerns the live video being ingested by YouTube. It is not a recommendation for the export bitrate of the original file, and it does not specify a viewer’s eventual playback bitrate. Keeping those three stages separate prevents a common setup mistake: copying a file’s export number into an encoder field without checking what the field controls.
Use 14 Mbps for H.264 or 10 Mbps for AV1 and H.265
If your outgoing video is H.264, set the video bitrate to 14 Mbps for this 1080p30 target. If it is H.265/HEVC or AV1, use 10 Mbps. Those are YouTube’s codec-specific recommended ingestion rates in the cited table, not guarantees that the picture will look the same across different material or encoders.
The source being prerecorded does not change this choice. A file might have been exported at a different bitrate, or use a different codec from the one your live encoder sends. YouTube’s guidance is about the outgoing stream. If your software decodes the file and re-encodes it as H.264, the H.264 row is the relevant row, even if the file itself was encoded as HEVC.
A lower setting may be necessary if your upload connection cannot sustain the recommended rate, but that is a compromise rather than a new recommendation for prerecorded video. First determine whether the stream is dropping frames, buffering, or reporting network trouble. If the connection is limited, consider whether a lower outgoing resolution or frame rate is more dependable than trying to push a target rate through an unstable link.
For a channel that runs overnight, consistency matters as much as the number entered in a settings panel. A file can play smoothly on your computer while the uplink has interruptions or the encoder struggles to keep pace. If you are comparing encoding choices, this codec comparison for live streaming can help you understand the practical differences before settling on an output format.
Set the outgoing resolution and frame rate
Set the encoder’s output to 1920×1080 and 30 fps if that is the stream you intend viewers to receive. Then choose its outgoing codec and bitrate. Do not assume the file’s properties automatically determine the live output: many streaming applications can scale, change frame rate, or transcode a source while it is playing.
The input file’s frame rate is still relevant to the look of motion. A 24 fps film or a 25 fps recording can be sent in a 30 fps output, but conversion may repeat or otherwise adapt frames. That does not make the bitrate row different. It is a separate production choice, and the result depends on the content and the encoder’s handling of frame conversion.
Likewise, a 1080p source does not compel a 1080p live output. If your channel’s connection or encoder cannot reliably deliver that output, choosing a lower output resolution may be more sensible than keeping 1080p at a rate that regularly fails. Conversely, upscaling a lower-resolution file to 1080p does not create additional detail; it only changes the outgoing frame dimensions.
Check the output or stream settings preview in your encoder before starting. Confirm width, height, frame rate, codec and bitrate together. If you use a hardware encoder or a managed playout workflow, the available names and controls may differ, so verify what is being transmitted rather than relying only on a profile label such as “YouTube 1080p”.
For a continuous playlist, make the output format consistent across files where possible. A stable format reduces surprises at transitions, especially when clips have different dimensions, frame rates or codecs. Advice on running a 24/7 Tamil music radio stream covers broader playlist operations; for bitrate, keep returning to the output settings actually sent to YouTube.
Match the recommendation to the codec actually used
A codec is the method used to compress the outgoing video. H.264, H.265/HEVC and AV1 are separate choices in YouTube’s RTMP/RTMPS encoder guidance. The original file’s codec and the live output’s codec can differ if the software decodes and encodes the material on the way out.
To identify the right row, inspect the encoder’s streaming output configuration, not just the file information panel. If the output encoder is explicitly set to H.264, use 14 Mbps. If it is set to HEVC or AV1, use 10 Mbps. If you cannot establish the output codec, do not guess from the file extension; check the software’s encoder settings or documentation.
Codec choice may be constrained by your encoder, operating system, hardware, and workflow. A software encoder can offer different formats from a standalone encoder, and a playback-oriented device may not support every live output option. YouTube describes both software and standalone hardware as possible encoder approaches in its overview of streaming with an encoder. There is no need to buy a particular device just to apply the bitrate table.
If you are using H.264 because it is the format your current setup reliably supports, that is a valid operational choice. Do not switch codecs solely because another row has a lower number if the new encoder path is untested or unavailable. A stream that reconnects or produces encoder errors is not improved by a more efficient codec setting on paper.
A prerecorded workflow changes the work you do before broadcast, not YouTube’s codec-specific ingest guidance. You can inspect the source file, test a representative section and make sure the live encoder produces the intended output. But the bitrate recommendation remains tied to the outgoing stream’s codec, resolution and frame rate.
Configure CBR and the keyframe interval
YouTube recommends constant bitrate, or CBR, for encoder settings. With CBR, the encoder aims to send video at a steady configured rate rather than varying the rate widely with scene complexity. This makes the configured bitrate meaningful as an ongoing network requirement, though the image still depends on the source, encoder and content.
Set the keyframe interval to two seconds. YouTube’s guidance says not to exceed four seconds. Keyframes provide reference points in the compressed video stream; an interval that is too long can affect how the stream is processed and joined by playback systems. Follow the encoder’s unit convention, since one application may express the interval in seconds and another in frames.
YouTube lists H.264, H.265/HEVC and AV1 for RTMP/RTMPS encoder settings. RTMPS is its recommended secure extension to RTMP for sending a stream. If your encoder offers RTMPS, use the connection information generated in YouTube Studio and make sure the selected protocol matches the server address and stream key details supplied there.
Audio has its own encoder settings and consumes part of the total upload bandwidth. Do not add the recommended video bitrate and call that the total required upload speed. Account for audio and any other traffic using the same connection, and leave room for ordinary variation rather than planning at the exact limit.
A settings guide for FFmpeg 1080p30 playlist streaming may be useful if you build an encoder command yourself. Check each parameter against the current YouTube guidance and your FFmpeg build; a copied command can be inappropriate if its codec, rate-control mode, frame rate or keyframe interval differs from your intended output.
Test upload capacity and stream health
Measure upload capacity, not download speed. A fast download connection can still have insufficient or inconsistent upload for a live stream. YouTube recommends leaving 20% headroom: the total streaming bitrate should not exceed the available upload bandwidth after accounting for that margin. Its streaming troubleshooting guidance advises testing upload bitrate and checking stream health.
For example, if the video is configured at 14 Mbps, the connection needs to carry that video plus audio and other simultaneous traffic while retaining the recommended headroom. The example is not a universal speed-test result: available upload can fluctuate, and a test performed at one time does not prove the connection will remain stable overnight. Avoid setting the stream to consume nearly all the capacity measured by a single test.
Run a private or unlisted test before the public broadcast, using the same encoder, network path, audio and representative content. Include material with movement as well as a still or simple scene if the channel contains both. Observe the encoder for overload or dropped frames and look at YouTube Studio’s stream health messages. A still devotional image with light movement may behave differently from a news loop with scrolling graphics or a music video with rapid cuts.
Test transitions too. For a playlist, check what happens at the end of one file and the start of the next, especially if their dimensions, frame rates or audio levels differ. Leave the test running long enough to expose problems that do not appear in a short preview, but do not mistake one clean test for a guarantee that a later session will be trouble-free.
If the stream shows network instability, check for other uploads on the same connection, Wi-Fi variation, and the router or ISP path. You can also reduce the outgoing bitrate or resolution and retest. If the encoder reports overload, the issue may be processing rather than bandwidth; use a less demanding encoder preset or a different supported encoding path, then test again.
An always-on stream also needs recovery planning. Note where the stream key and output settings are stored, who can access them, and how you will notice a stopped broadcast. Practical steps for a YouTube stream that stops overnight are relevant when planning monitoring and recovery, but no bitrate value by itself prevents a computer, network or source-file failure.
Separate ingest bitrate from viewer playback quality
Ingest bitrate is the rate your encoder sends to YouTube. Viewer playback is a later stage: YouTube processes the incoming stream and viewers receive playback according to factors that can include their device, connection and selected quality. The number in your encoder does not mean every viewer will receive a 14 Mbps or 10 Mbps video stream.
This distinction also explains why a higher ingest figure is not a promise of a better-looking picture in every case. A low-detail image, a high-motion scene, noisy footage and a clean animation put different demands on compression. The encoder matters too. YouTube’s recommended rate is a practical target for its stated ingest format, not a guarantee of identical results from every source or encoder.
The original file’s bitrate is another distinct value. It describes how that file was encoded, while the live output setting describes what your encoder sends after decoding and possibly re-encoding it. A file exported at a high rate can still be sent live at a lower configured rate; setting a high export bitrate cannot compensate for an incorrectly configured live output.
Finally, latency is separate from bitrate. YouTube describes stream latency as the delay between capture at the encoder or camera and playback to the viewer. Its latency settings help page explains that lower latency can mean more buffering. Choose latency according to whether your broadcast needs interaction or can prioritise a steadier viewing experience; do not use latency as a substitute for selecting the correct bitrate row.
For a prerecorded loop, the word “capture” may feel less intuitive because the pictures were made earlier. The relevant live point is still the encoder’s outgoing stream and its delivery to YouTube, followed by processing and viewer playback. Keep those stages distinct when troubleshooting: an ingest warning points you towards the encoder or connection, while a viewer’s playback issue may have other causes.
If keeping a computer running is the part of the workflow that makes a long playlist difficult to manage, StreamNeo turns an uploaded video into a YouTube live stream that can continue with your own computer switched off, monitored and restarted automatically if it drops. The bitrate and codec decision still needs to match the output you intend to send, and it remains sensible to test the file and check the channel’s stream health.
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 a prerecorded 1080p30 YouTube Live stream?
Use 14 Mbps for H.264, or 10 Mbps for H.265/HEVC or AV1, following YouTube’s cited en-US encoder table. The fact that the source is prerecorded does not create a different recommendation; use the row matching the outgoing stream codec.
Is YouTube’s minimum bitrate the recommended setting?
No. For 1080p30, YouTube lists minimums of 5 Mbps for H.264 and 4 Mbps for H.265/HEVC or AV1, alongside the higher recommended rates. The minimum is not the target recommendation, and your actual choice should also account for a stable upload connection.
Does a 14 Mbps encoder setting mean viewers watch at 14 Mbps?
No. That is the configured video rate sent to YouTube for ingest, not a guarantee of the playback rate delivered to each viewer. YouTube processes the incoming stream, and playback can vary by viewer and viewing conditions.
What should I check if the recommended rate is unstable?
Check upload capacity, other traffic on the connection, encoder load and YouTube Studio’s stream health messages. Test a lower output bitrate or resolution if needed, and retest with the same content and workflow before relying on it for a long broadcast.