For a 720p, 30 fps YouTube Live stream, choose the bitrate from the live-ingest recommendation for the codec your encoder sends: 8 Mbps for H.264, or 6 Mbps for AV1 or H.265/HEVC. These are recommendations, not guarantees; test the actual outgoing connection and loop before relying on either setting.
A pre-recorded file played into a live encoder is still being sent as a live stream. Do not substitute the separate bitrate guidance for uploading a normal video file. The codec, resolution, frame rate, available upload capacity and stability of the connection all matter.
Set the output to 720p30
Start by setting the stream output to 1280 × 720 pixels at 30 frames per second. The encoder’s output matters here, not just the dimensions and frame rate of the original file. If the source is a different size or frame rate, decide deliberately how it will be scaled or converted, then confirm the resulting output in the encoder settings.
YouTube’s live encoder guidance gives recommendations by ingest codec, resolution and frame rate. For this question, use the row for 720p at 30 fps and the codec actually sent to YouTube. A loop does not have a separate row: YouTube does not publish a different bitrate recommendation for pre-recorded or low-motion material.
This is worth checking even when the file looks right in a media player. An encoder can output a different resolution or frame rate from the source, and your bitrate choice should match the stream you are sending. In your test, confirm that the live control room reports the intended resolution and that the encoder has not silently reverted to another profile.
If the video has mostly still artwork, a devotional image or a slowly changing ambience scene, it may appear to need less bandwidth than fast-moving footage. That visual impression does not change YouTube’s stated recommendation. Lowering the bitrate is a quality trade-off to test, not an official adjustment for loops. Watch for blockiness, smearing or other visible damage during movement, fades, text changes and transitions.
Choose the ingest codec
The codec is the first decision in the bitrate table. H.264 is widely supported by streaming encoders. YouTube also lists H.265/HEVC and AV1 for live encoder settings, but the encoder you use must support the chosen codec and be configured to send it. The setting in the software is not enough on its own: verify that the selected profile is the one being used for the stream.
For most readers, this is a practical compatibility choice rather than a reason to change the whole setup. If your current encoder is already configured for H.264, use the H.264 live recommendation rather than copying a lower figure from an AV1 or H.265 row. If you can select another codec, first check that your encoder and workflow support it and then use that codec’s own recommendation.
A pre-recorded source does not mean YouTube receives the original file unchanged. The live encoder produces an outgoing stream, and it is that stream’s codec, resolution, frame rate and bitrate that guide the settings. Keep this distinction in mind when you compare a file’s properties with the encoder panel.
For an overview of the workflow around replaying a file as a live broadcast, see how to run prerecorded videos on a YouTube Live stream. It is useful context for this setting, but the bitrate figures below come from YouTube’s live encoder guidance, not from a particular playback method.
Use the matching recommended bitrate
At 720p30, set the encoder’s video bitrate according to its outgoing codec. YouTube Help’s live encoder settings table recommends 8 Mbps for H.264 and 6 Mbps for AV1 or H.265/HEVC. These figures answer the live-ingest question. They are not promises that a particular connection, encoder or picture will behave well.
| Live video codec sent to YouTube | 720p30 minimum listed by YouTube | 720p30 recommended by YouTube |
|---|---|---|
| H.264 | 3 Mbps | 8 Mbps |
| AV1 | 2 Mbps | 6 Mbps |
| H.265/HEVC | 2 Mbps | 6 Mbps |
Treat the minimum and recommendation as distinct settings, not interchangeable targets. The minimum is the lower figure in YouTube’s table; it is not a guarantee of acceptable picture quality for your loop. The recommended figure is the default to aim for if your tested upload connection can carry the stream with room to spare.
If you must reduce the bitrate because the actual connection cannot sustain the recommended value, make that choice knowingly. A lower rate can reduce the data the stream sends, but can also make fine detail, text, gradients or moving elements less clear. Test the changed profile using the actual loop and inspect the result on YouTube before committing to a long broadcast.
The network check should account for the whole outgoing stream, including audio, rather than treating the video number as the only data being sent. YouTube’s streaming tips advise leaving about 20% room between the stream’s total outgoing bitrate and available upload bandwidth. That is guidance for planning, not evidence that a line with a particular advertised speed will sustain the stream continuously.
Know the codec-specific minimums
The lower figures are useful when diagnosing a constrained connection, but they should not be confused with the recommended targets. At 720p30, YouTube lists 3 Mbps as the H.264 minimum and 2 Mbps as the minimum for AV1 and H.265/HEVC. The recommended rates remain 8 Mbps and 6 Mbps respectively.
Do not mix rows. An encoder set to H.264 should not use the AV1 minimum simply because that number is smaller. First check the codec being sent, then compare the minimum and recommendation in that row. If your encoder display uses kilobits per second, convert consistently: 8 Mbps is 8,000 Kbps, for example. Confirm whether the panel expects bits per second, kilobits per second or megabits per second so that a unit mismatch does not produce a drastically different setting.
A low-motion loop can still contain difficult material: scrolling text, fine patterns, moving water, leaves, candlelight or a cross-fade can expose compression artefacts. A static opening frame is a poor test of how the full file will look. If picture quality is not acceptable at a reduced rate, the practical choices are to improve the available connection, select an appropriate supported codec, or reconsider the output profile. Do not claim that a minimum figure is enough without checking the actual result.
Set protocol and encoder basics
Use RTMPS if your encoder supports it; otherwise use the protocol supported by your setup. YouTube describes RTMPS as RTMP sent over TLS/SSL and recommends it for encrypted ingestion. Its RTMPS setup guidance explains the secure protocol. Protocol choice does not replace a bitrate test: it addresses how the stream is sent, not the upload capacity available on your connection.
Set the video bitrate mode to CBR, or constant bitrate, as specified in YouTube’s encoder recommendations. CBR keeps the selected target rate consistent rather than allowing the video rate to vary substantially with the scene. Use a keyframe interval of two seconds, and do not exceed four seconds, following the same YouTube guidance. Check that the encoder profile has not retained a different keyframe interval from an older preset.
Set the frame rate to 30 fps and keep it consistent with the intended output. YouTube supports higher frame rates, but that does not make them relevant to a 720p30 target. Match the source and encoder output where practical; if the source is not 30 fps, test how conversion looks at scene changes and motion rather than assuming the conversion is invisible.
For audio, YouTube lists AAC and MP3 as supported encoder audio codecs and gives 128 Kbps stereo as a recommended advanced setting. Choose the audio configuration that matches the material and verify that it is actually present in the broadcast. A music or devotional loop that has no sound in one section may still have audio encoding active, so test both a quiet section and a representative section with sound.
Here is a compact checklist to review before sending the stream:
| Setting | Starting point for this 720p30 stream |
|---|---|
| Resolution and frame rate | 1280 × 720, 30 fps |
| Video codec | H.264, AV1 or H.265/HEVC; use its matching row |
| Bitrate mode | CBR |
| Video bitrate | H.264: 8 Mbps recommended; AV1/H.265: 6 Mbps recommended |
| Keyframe interval | 2 seconds recommended; no more than 4 seconds |
| Protocol | RTMPS where supported, otherwise the supported option |
| Audio | AAC or MP3; test the actual audio in the loop |
| Network capacity | Total outgoing rate fits measured upload with room left over |
The checklist is a starting profile, not a certification of the complete setup. Encoder labels and controls differ, so confirm what each field means in your software and test the stream after changing settings.
Keep uploaded-video guidance separate
A common source of confusion is the 5 Mbps figure associated with YouTube’s recommendation for uploading SDR 720p video at standard frame rates. That number is for encoding a file that you upload as a video. It is not the live-ingest recommendation for a 720p30 broadcast.
A file can be pre-recorded and still be part of a live workflow. If software plays the file into an encoder that sends a YouTube Live stream, use the live table for the outgoing encoder stream: at 720p30, 8 Mbps recommended for H.264 or 6 Mbps for AV1/H.265. The fact that the source was uploaded to, stored on or prepared from a file does not turn the live broadcast into a normal video upload.
YouTube publishes the distinct file guidance on its recommended upload encoding settings page. Keep that page for the separate task of preparing a regular upload. For the bitrate of a live encoder, use the live settings table instead. If you are calculating storage or data consumption for an always-on stream, the outgoing rate and broadcast duration are relevant to that estimate; this guide’s figures should not be read as a monthly data total. A related guide to estimating data usage for a YouTube stream can help separate rate from duration.
Test the actual loop before going live
A speed test is a snapshot of the connection, not a promise about what it will sustain throughout a long broadcast. Run it on the same connection and, as far as possible, in the same conditions as the encoder will use. Measure upload capacity rather than relying on download speed or the headline speed of an internet plan. Other devices and network activity can affect what is available at the time.
Compare the measured outbound upload capacity with the total outgoing stream rate. YouTube recommends leaving about 20% room, so avoid planning to consume the full measured capacity with the stream. Include audio and account for other traffic sharing the connection. If the remaining room is too small or results vary, reduce competing traffic, test at a less busy time, or choose a lower profile and inspect its picture quality. Do not infer reliability from a single favourable test.
YouTube’s encoder guidance says to test before starting and to monitor stream health and messages during the event. For a loop, make the test representative: include the actual audio, the most visually active part, a transition or fade, and any text or overlay that viewers will see. A test consisting only of a still title card will not show how the encoder handles the rest of the programme.
Check the stream preview and health indicators, then watch the result rather than relying only on the encoder’s green status. Look and listen for dropped or distorted material, audio that disappears, visible compression, unexpected scaling and interruptions. If you adjust bitrate, codec or frame rate, repeat the test; a configuration change can alter the result. For troubleshooting interruptions that occur during a long sequence, this guide to a YouTube stream skipping episodes offers a separate diagnostic path.
For an always-on channel, consider where the encoder runs and what happens if its connection or computer stops. StreamNeo can remove the need to keep your own computer switched on for a file-based YouTube broadcast, which is useful when a local machine is the part you cannot leave running overnight. It does not change YouTube’s codec-specific bitrate guidance or remove the need to check the stream and the available connection for the workflow you choose.
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 720p 30 fps YouTube Live loop?
Use the live recommendation that matches the codec sent by your encoder: 8 Mbps for H.264, or 6 Mbps for AV1 or H.265/HEVC. YouTube also lists minimums of 3 Mbps for H.264 and 2 Mbps for AV1/H.265. Test the actual stream and connection before relying on a setting.
Does a pre-recorded video loop need a different bitrate?
YouTube’s live encoder table does not give a separate bitrate for pre-recorded or looped content. If the file is played into a live encoder, use the live-ingest row for the outgoing codec, resolution and frame rate. Lowering bitrate for a visually simple loop is a quality trade-off to test, not a separate YouTube recommendation.
Is 5 Mbps enough for a 720p30 live stream?
The 5 Mbps figure is YouTube’s separate recommendation for uploading SDR 720p video at standard frame rates, not its live-ingest recommendation. For a live encoder at 720p30, use the codec-specific live recommendation and test available upload capacity. Do not treat the upload figure as a substitute.
How much upload bandwidth should I leave for a 720p30 stream?
Measure outbound upload on the connection the encoder will use and compare it with the total outgoing stream bitrate, including audio. YouTube recommends leaving about 20% room, but a speed test cannot guarantee what the connection will sustain later. Test in representative conditions and monitor stream health during the broadcast.