Choose YouTube’s recommended live-ingestion bitrate for your input codec, resolution and frame rate, then confirm that your upload connection can sustain it. For H.264, the recommended rates include 14 Mbps for 1080p at 30 fps, 17 Mbps for 1080p at 60 fps, and 8 Mbps for 720p at either frame rate.
YouTube does not specify a separate bitrate just because a livestream runs continuously. For an always-on channel, the practical difference is that a setting must remain sustainable over time: use CBR, follow YouTube’s keyframe guidance, test representative content, and watch the stream-health panel. Verify exact FFmpeg options against your installed build before relying on a command.
Choose bitrate for the input format
Bitrate is the rate of the encoded video being sent to YouTube. It is not a universal quality dial: the recommended value depends on the codec, the dimensions of the picture and how many frames are sent each second. A 1080p H.264 stream at 60 fps has a different recommendation from 1080p H.264 at 30 fps, and both differ from an AV1 or H.265 stream at the same dimensions.
Start by identifying what your encoder will actually send, rather than choosing from the resolution of the original file alone. If you are scaling a source video to 720p, your output is 720p for this decision. If the output frame rate is 30 fps, use that row even when the source file was recorded at 60 fps. Check the output codec as well: a recommendation for H.264 should not be copied to AV1 or H.265 without checking YouTube’s table for that codec.
These are YouTube’s recommended video ingestion rates for live encoding, not a total that includes audio. Do not confuse them with YouTube’s separate guidance for uploading prerecorded videos. The YouTube Help live encoder settings page is the primary reference for the live table and adjacent encoder recommendations; check it again when you configure a channel because guidance can change.
A recommended rate is a target, not a promise that a particular picture will look good under every condition. A static devotional image and a busy dance performance can behave differently after encoding, even at the same resolution and bitrate. The content, encoder and source quality all affect the result. Start from the row that matches your intended output, then assess a real test rather than assuming the number alone guarantees quality.
For a continuous channel, duration does not add a new row to the table. The challenge is operational: an upload rate that works briefly but varies or is shared with other household traffic may not sustain the stream. If it does not, lowering output resolution or frame rate can be a more sensible reliability choice than keeping a higher format and repeatedly suffering interruption. For more on the practical costs of adding resilience to a home setup, see what a second internet connection adds to a home YouTube streaming setup.
H.264 bitrate recommendations by resolution and frame rate
The table below reproduces YouTube’s H.264 live-ingestion recommendations in Mbps. “Minimum” is included as context, but do not treat it as the preferred setting: use the recommended column as your starting point when the connection can sustain it. YouTube labels these as video bitrates, so audio should not be added to or mistaken for the listed video target.
| H.264 input format | Minimum video bitrate | Recommended video bitrate |
|---|---|---|
| 2160p (4K), 60 fps | 14 Mbps | 50 Mbps |
| 2160p (4K), 30 fps | 11 Mbps | 42 Mbps |
| 1440p, 60 fps | 8 Mbps | 34 Mbps |
| 1440p, 30 fps | 7 Mbps | 21 Mbps |
| 1080p, 60 fps | 6 Mbps | 17 Mbps |
| 1080p, 30 fps | 5 Mbps | 14 Mbps |
| 720p, 60 fps | 3 Mbps | 8 Mbps |
| 720p, 30 fps | 3 Mbps | 8 Mbps |
| 480p, 30 fps | 0.4 Mbps | 4 Mbps |
| 360p, 30 fps | 0.4 Mbps | 4 Mbps |
For a typical 1080p30 H.264 loop, that means starting from 14 Mbps, not selecting a different value because the playlist runs overnight. At 720p30 or 720p60, the recommended video rate is 8 Mbps. A higher frame rate changes the recommendation at some resolutions, but not every row: the two listed 720p options share the same recommended value.
If your actual output uses AV1 or H.265, consult the corresponding rows in YouTube’s live settings page instead. As one comparison, YouTube’s table gives 10 Mbps as the recommended rate for AV1 or H.265 at 1080p30, while H.264 at that format is 14 Mbps. That does not make one codec universally preferable; the encoder you can use, the chosen output format and your connection all matter.
When the recommended H.264 value is not sustainable, avoid quietly treating the minimum as a guaranteed equivalent. First check whether the issue is upload variability, competing traffic, or a mismatch between the selected and actual output. If the connection remains the constraint, choose a lower resolution or frame rate that you can test successfully. A smaller, stable picture can serve an always-on channel better than a nominally sharper stream that repeatedly starves.
Set CBR and keyframe interval
YouTube recommends constant bitrate (CBR) for live encoding. The point is to keep the stream’s outgoing rate consistent with the selected target rather than allowing it to vary widely. The exact encoder controls that produce CBR depend on the encoder and FFmpeg build you are using; a bitrate option on its own does not establish that the output meets this behaviour.
YouTube recommends a keyframe frequency of two seconds and says not to exceed four seconds. A keyframe, or intra frame, gives the receiving platform a reference point for decoding the video. In encoder terminology, the spacing between these points is often described through the GOP (group of pictures) interval. Check that the configured interval matches the frame rate and intended duration, and investigate whether the GOP is open if YouTube reports an open-GOP issue.
The documented recommendation is about the output stream, not merely a number entered in a command. If you change frame rate, scaling or encoder, recheck the resulting keyframe behaviour. The YouTube Live Streaming API health guidance lists long or overly short GOPs and open GOPs among configuration issues, and advises a keyframe frequency of four seconds or less.
Treat CBR and keyframe frequency as related checks, not substitutes for the bitrate choice. A well-spaced keyframe pattern cannot compensate for an upload link that cannot carry the video. Likewise, matching the recommended bitrate does not make an incorrect codec, unsupported output or missing video acceptable. Confirm each part separately in the test and in YouTube’s diagnostics.
Check connection capacity before going live
The relevant capacity is the upload that is reliably available to the streaming device while the stream is running, not only the headline download figure on an internet plan. Other users, cloud backups, software updates and Wi-Fi changes can compete with the encoder. A result from one speed test is a useful clue, but it does not prove that the connection will behave the same way for an overnight broadcast.
Run an upload test at the place and time you expect to stream, and repeat it when the household or workplace is using the network normally. Compare the observed upload capacity with the intended video bitrate, while remembering that the listed YouTube recommendation is for video and the stream also has audio and protocol overhead. Do not set the target at the very edge of a result that fluctuates. You need usable headroom, although there is no single margin in the supplied YouTube guidance that applies to every connection.
If the stream will run from a local computer, wired Ethernet can remove one source of wireless variation, though it cannot fix an overloaded or unstable internet connection. Avoid starting a large upload or backup during the test. For a channel that uses playlists of prerecorded content, this is part of the wider setup described in running a 24/7 YouTube video playlist with FFmpeg’s concat demuxer: the playlist may be ready, but the outgoing connection still has to carry it consistently.
YouTube’s advice is to select a quality your internet connection can sustain. If capacity is not dependable at the target rate, lower the output format and test again rather than repeatedly raising bitrate to address a visual problem that may have another cause. If you depend on a computer staying awake for the broadcast, also account for power and sleep behaviour; what happens when Windows enters Connected Standby during an OBS stream covers one separate cause of an unexpected disconnect.
Run a representative test stream
Before making a format the channel’s default, send a test with the same codec, resolution, frame rate, bitrate, audio and network conditions you intend to use. A still image by itself is not a representative test for a music visualiser, a news loop with a ticker or footage with frequent movement. Include the sort of audio and motion that appears in the actual broadcast so you can see whether encoding and upload remain stable under realistic content.
YouTube specifically advises testing before going live with audio and movement similar to the intended stream. Use the preview and stream-health messages in YouTube Studio, and let the test run long enough to observe normal variations in your connection rather than deciding from the first few moments. A private or otherwise non-public test can help you check presentation without treating the main channel as a trial run; testing a kids’ cartoon loop privately before a 24/7 YouTube stream is relevant when you need to inspect a loop first.
Check that the picture dimensions and frame rate reported by YouTube match your chosen output. Look for warnings, buffering or a delayed preview, and confirm audio is present if the programme needs it. A clean local FFmpeg log does not prove that YouTube is receiving a healthy stream: the ingest side sees what arrived over the network, not just what the encoder attempted to send.
If the test shows a bitrate or ingestion problem, change one factor at a time. Confirm the configured rate, then inspect the upload link and stream-health messages. If the rate is correctly configured but the incoming stream is starved, reduce the output format or address the network constraint and repeat the test. If the issue points to keyframes or codec, changing the internet plan is unlikely to address it.
Monitor stream health and adjust carefully
After starting the real broadcast, keep YouTube Studio’s stream-health panel available and read its messages rather than watching only the preview. The Live API health documentation describes diagnostics such as bitrate too high or low, long or short GOP, open GOP, unsupported codec, missing audio or video, multiple audio or video streams, mismatched backup-stream settings and video ingestion starvation. Most creators do not need to query the API, but the categories help you interpret the warnings surfaced in Studio.
A high- or low-bitrate warning calls for checking both the target you configured and what is actually reaching YouTube. A keyframe warning points towards GOP timing or GOP structure. Starvation means YouTube is not receiving enough video data for smooth playback; it is a reason to investigate delivery and capacity, not simply to assume that the displayed target number is wrong. Correct the cause indicated by the message, then verify the result in the panel.
Do not change bitrate repeatedly based on a single brief warning without checking whether the underlying condition persists. Note the time, message, current format and network conditions. If the warning appears during busy household or business hours, compare that period with a quieter test. If the format is ambitious for the available connection, a deliberate step down in resolution or frame rate may be clearer than a series of undocumented bitrate changes.
For a continuous channel, monitoring is part of the operating plan. Decide who will see an alert or check Studio if the stream is being run manually, and make sure the person knows what a health warning means. A cloud service can remove the need to leave your own computer running: StreamNeo takes an uploaded video and runs it as a YouTube live stream after you provide the stream key, with monitoring and automatic restart if the broadcast drops. It remains your responsibility to choose suitable content and a workable output, and to check the channel’s live status.
Verify FFmpeg syntax for your version
The settings above describe the intended output behaviour; they are not a verified, universal FFmpeg command. FFmpeg command-line options, encoder names and supported controls depend on the installed version and on which video encoder you select. The reviewed YouTube guidance establishes target behaviour, but it does not define exact FFmpeg syntax or prove that a generic video-bitrate flag by itself creates CBR.
Before adding flags to a production command, check the installed FFmpeg version and identify the encoder actually selected. Then consult the documentation for that version and encoder for bitrate control, rate-control mode, buffer behaviour and GOP options. A flag that exists for one encoder may have a different meaning, or be unsupported, in another. Avoid copying a command from a different machine without checking those details.
Inspect the output from a short test and compare it with YouTube’s stream-health information. Confirm the codec, resolution, frame rate, bitrate behaviour and keyframe pattern rather than assuming that a syntactically accepted command produced the expected stream. Save the verified configuration and record which FFmpeg build and encoder it applies to, so later changes do not silently alter the output.
This check matters especially when you change hardware or move the stream to another machine. A command that worked with one build may not select the same encoder in another environment. The safe instruction is not to rely on an exact command here: verify each option against your installation, test the result, and use YouTube’s diagnostics to confirm what it receives.
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 24/7 YouTube livestream?
Use the YouTube recommendation for the output codec, resolution and frame rate, then test whether your upload connection can sustain it. For H.264, common examples are 14 Mbps at 1080p30, 17 Mbps at 1080p60 and 8 Mbps at 720p30 or 720p60. These are video ingestion rates, not audio-inclusive totals.
Does YouTube need a different bitrate for a continuous stream?
YouTube’s guidance does not publish a separate bitrate based on how long a stream runs. The always-on requirement is operational: a rate that matches the format still needs to be sustainable over time, so test and monitor it.
Is the minimum bitrate in the table the best choice?
No. YouTube labels a separate recommended rate, which is the sensible starting target when the connection can sustain it. If it cannot, consider a lower output resolution or frame rate and test that format rather than assuming the minimum will deliver equivalent quality.
Can I copy an FFmpeg bitrate command from another setup?
Not safely without checking the FFmpeg build and selected encoder. The exact flags and rate-control behaviour are version- and encoder-specific, so verify the matching documentation and confirm the resulting stream in a representative test.