For a 720p, 30 fps YouTube Live stream, set the encoder to 8 Mbps with H.264 or 6 Mbps with AV1 or H.265/HEVC. YouTube lists lower minimums of 3 Mbps for H.264 and 2 Mbps for AV1 or H.265, but those are ingest figures, not the bitrate every viewer will receive.
A video being pre-recorded does not give it a separate bitrate rule. Choose the row for the resolution, frame rate and codec that your encoder actually sends to YouTube, then check that your upload connection can sustain the stream.
Select the 720p30 YouTube Live row
YouTube's live encoder guidance lists bitrate recommendations by resolution, frame rate and codec. The relevant row is 720p at 30 frames per second. “Pre-recorded” describes the content being played; it does not change the properties of the live signal going to YouTube.
The figures below are YouTube's listed encoder bitrates for that row. The recommended value is the starting point to aim for. The minimum is a lower listed value, not a guarantee that any particular video will look good or that a marginal connection will stay stable.
| Encoder codec | Recommended ingest bitrate | Listed minimum ingest bitrate |
|---|---|---|
| H.264 | 8 Mbps | 3 Mbps |
| AV1 | 6 Mbps | 2 Mbps |
| H.265/HEVC | 6 Mbps | 2 Mbps |
These are values for the video signal sent into YouTube Live. They do not describe a fixed quality or bitrate delivered to every viewer. YouTube processes live streams into viewer formats, and the format available to someone watching depends on YouTube's delivery and the viewer's conditions.
For the official figures and related encoder settings, consult YouTube's live encoder settings and bitrate guidance. YouTube's recommendations can change, so check the current help page when you configure a new encoder or revise an existing stream.
Use the recommendation for your chosen codec
If your encoder sends H.264 at 720p30, set 8 Mbps as the target. If your encoder and YouTube stream setup support AV1 or H.265/HEVC, the listed recommendation is 6 Mbps. The difference is why the codec needs to be part of the setting decision rather than treating “720p30 bitrate” as one universal number.
Do not select AV1 or H.265 just because its table value is lower. The encoder must genuinely output that codec, and the stream configuration must support it. If your tool only offers H.264, use its 8 Mbps recommendation. If you do have a choice, consider compatibility and whether your encoder can produce a consistent output as well as the bitrate figure.
A bitrate is how much encoded video data is sent over time. Raising it may help preserve detail in motion or complex scenes, but it also asks more of the outgoing connection. A devotional video with a mostly fixed image and gentle movement still uses the row matching its actual outgoing format; the table does not provide a separate reduced setting for static or pre-recorded content.
When your stream repeatedly buffers or drops frames, do not assume a lower minimum is automatically the fix. First check the encoder's output and the actual upload capacity, then test a stable configuration. If the recommended bitrate cannot be sustained, the listed minimum can inform a trial, but you must validate the result rather than treating it as a quality or stability promise.
Understand what the listed minimum means
The minimum is useful as a reference point when comparing the official table with a connection or encoder that cannot reach its recommended value. For 720p30, the listed floor is 3 Mbps for H.264 and 2 Mbps for AV1 or H.265. It does not mean YouTube recommends that setting for every stream, nor that a recording will appear equally clear at any bitrate above it.
The amount of motion and detail in the picture affects how difficult a scene is to encode. A static altar image with a slow lamp animation may be less demanding than a crowded procession, fast camera movement, or a scrolling ticker. Yet the table's minimum remains a listed encoder value, not a content-specific allowance. A file being played back as a live broadcast does not cause YouTube to use a different row.
For a small channel or a long-running music loop, test the actual file rather than judging by a short quiet section. Include the busiest visual passages and the loudest or most complicated audio segments, since they reveal problems a still frame can hide. Keep the stream at the intended resolution and frame rate during the test.
The bitrate table is only one part of the picture. An encoder can be configured correctly and still fail to send steadily if the network fluctuates, the computer is overloaded, or another upload competes for capacity. Conversely, a good connection cannot repair a source that is encoded at the wrong resolution or a frame rate that does not match the intended stream.
Match settings to the signal you actually send
Set your encoder's output resolution to 1280 by 720 and frame rate to 30 fps if that is the intended live signal, then use the matching codec row. Check the output settings rather than relying only on a file's name or its properties in a media player. A source file can be 1080p or 25 fps while an encoder scales or converts it before sending; what matters for the YouTube ingest selection is the outgoing stream configuration.
The same point applies when a playlist or automation tool handles the file. Confirm whether it passes the original media through, re-encodes it, or outputs a different frame size or rate. If you are using FFmpeg and need to reason about a 720p output pipeline, the practical examples in a 720p YouTube streaming configuration with FFmpeg are relevant; check the URL's formatting when linking (remove the space after the opening parenthesis).
Use a single consistent profile for the broadcast unless you have a specific reason to change it. A stream that unexpectedly switches resolution, frame rate or codec can complicate diagnosis, especially when you are comparing test results from different sessions. Write down the settings that produced a healthy test so you can restore them after a software update or a change to the playback source.
Encoder options vary. YouTube describes both software and standalone hardware encoders; neither category is mandatory simply to choose a bitrate. If you are deciding how to run a continuous channel, compare the operational trade-offs in home NAS and cloud VM approaches to a 24/7 YouTube stream, but the bitrate figures themselves still come from the YouTube table.
Set CBR and a 2-second keyframe interval
YouTube recommends constant bitrate (CBR) encoding and a 2-second keyframe interval. It says not to exceed four seconds between keyframes. These settings sit alongside the bitrate choice: selecting 8 Mbps does not replace the need to set the encoder's rate-control mode or keyframe spacing.
CBR aims to keep the encoded rate steady over time. That can make the outgoing load more predictable than a variable rate that rises and falls with scene complexity. It does not mean every frame contains the same amount of visual information; the encoder manages that within the chosen constraints. For a stream running overnight, predictability helps you reason about whether your connection has enough sustained upload capacity.
A keyframe is a reference frame from which later frames can be reconstructed. The interval affects how often those complete reference points appear in the video stream. Follow the recommended two seconds, and keep the interval no longer than four seconds. If your software exposes the setting as a number of frames rather than seconds, confirm the conversion against the selected frame rate and its own documentation.
Use RTMPS where your encoder offers it. YouTube recommends the secure RTMPS option for sending the stream. The correct protocol does not alter the bitrate row, but it is part of a sound encoder setup. You can check YouTube's guidance on creating a live stream with an encoder if you need the steps for connecting an encoder to a stream.
Leave upload headroom
Your upload connection needs capacity for the stream's outgoing traffic, not just enough to match the nominal video bitrate at a single moment. YouTube's streaming tips recommend leaving 20% headroom. It also says to account for the total outgoing stream bitrate within the available upload capacity.
That margin matters because a home or shop connection is shared and can vary. Other people may be on video calls, a cloud backup may start, or a mobile connection may weaken. A speed test that looks comfortable while the network is quiet does not prove that a 24/7 broadcast will remain steady under all conditions. Test upload speed, as download speed is not the capacity the encoder uses to send the stream.
If you send both a primary and backup stream, include both in the capacity calculation along with the recommended margin. Avoid treating the connection's advertised top speed as an amount reserved for streaming. For guidance on the practical difference between connection types, see the fibre versus mobile broadband comparison for 24/7 YouTube streaming. The useful question is whether your real upload path can sustain the encoder's total output when other normal network use is happening.
If you repeatedly see dropped frames, compare what the encoder reports with what the connection can provide. A dropped-frame troubleshooting guide for a 24/7 Indian music stream can help distinguish network and encoding symptoms. Do not make several changes at once: reduce competing uploads, verify the configured bitrate, and test again so you can tell which change helped.
Test live ingest and stream health
Run a test before relying on the stream for an overnight schedule. Use the same file, encoder, resolution, frame rate, codec and network you intend to use in the real broadcast. YouTube advises testing before a live stream and recommends testing with similar audio and motion, then monitoring stream health and messages.
A useful test includes more than a few seconds of playback. Let representative parts of the video run long enough to reveal intermittent network or encoder issues. Watch Live Control Room for its status messages, and inspect the encoder for dropped frames, disconnections or overload warnings. If you hear crackles, see a frozen picture, or get repeated health warnings, note when they occur and what else the computer or connection was doing.
YouTube can detect encoder settings automatically. Manual resolution selection is associated with using a custom stream key and enabling manual settings, so do not force a setting without understanding how your chosen stream key is configured. Check the current official instructions rather than assuming a control works the same way across every encoder interface.
For a first test, write down the intended values: 720p, 30 fps, codec, bitrate, CBR, keyframe interval and protocol. Then compare the encoder's status with YouTube's health messages. If a setting is not being detected as expected, resolve that mismatch before you schedule a longer run. A test is especially useful after changing codecs or moving the stream to another network.
When the test is healthy, keep a note of the profile and avoid changing it casually. If the stream later becomes unstable, you can compare its current settings and network conditions with the known test rather than rebuilding the configuration from memory. A connection that passes once is not proof of guaranteed future uptime, so continue to observe a channel that matters to your audience.
Why viewers may receive a different format
The encoder's bitrate describes the feed you send to YouTube. It is not a promise that each person watching receives that exact bitrate, resolution or codec. YouTube transcodes live streams into output formats for viewers, so viewers can be offered different versions according to the platform's processing and delivery conditions.
A viewer on a mobile connection may choose a lower playback quality than someone on a stable home broadband connection. The YouTube player may also expose quality choices that differ from the encoder's input. As a result, one viewer's picture can look softer or use less data even though the ingest stream is unchanged. That is not evidence by itself that you should raise or lower the encoder bitrate.
Keep diagnosis on the right side of the hand-off. If the incoming stream health is poor, investigate the encoder, source, or upload connection. If YouTube is receiving a healthy stream but one viewer reports a particular playback issue, check the viewer's selected quality and connection before changing the broadcast profile. The distinction prevents a common mistake: treating the ingest figure as a guaranteed viewer-side setting.
For a channel built around a fixed video loop, the recurring operational concern may be keeping the file running without leaving a computer on. StreamNeo can remove that specific burden by turning an uploaded video into a YouTube Live broadcast that runs with your computer switched off, while monitoring and restarting the broadcast if it drops. The bitrate choice still needs to match the outgoing stream setup, and YouTube remains the platform that transcodes for viewers.
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
Does a pre-recorded video use a lower 720p30 bitrate?
No. YouTube's listed row is based on the live ingest resolution, frame rate and codec, not whether the pictures were recorded earlier. Use 8 Mbps for H.264 or 6 Mbps for AV1/H.265 as the recommendations for 720p30, and treat the listed minimums as lower reference points rather than a separate prerecorded rule.
Is 3 Mbps enough for 720p30 H.264?
It is YouTube's listed minimum for H.264 at that setting, while the recommendation is 8 Mbps. A stream at the minimum still needs a stable connection and a test with representative content; the figure does not guarantee a particular appearance or reliability.
Will every viewer receive my 8 Mbps stream?
No. That is an encoder ingest bitrate sent to YouTube, not a viewer delivery promise. YouTube transcodes live streams into viewer formats, and playback can vary with delivery and the viewer's selected quality or connection.
Which settings should I test together?
Test the actual 720p, 30 fps output with the intended codec and its recommended bitrate, CBR, a 2-second keyframe interval, and a connection with upload headroom. Use representative audio and motion, then check both the encoder and Live Control Room for stream health messages before relying on the setup.