For YouTube Live at 1080p and 60 frames per second using H.264, YouTube lists 6 Mbps as the minimum bitrate and 17 Mbps as the recommended bitrate. Treat 17 Mbps as a target only if your upload connection can sustain it reliably; the minimum is not the quality recommendation.
These figures apply to live ingestion, the signal your encoder sends to YouTube. They are not the bitrate settings for uploading a finished video. Start with the live-ingest settings, then adjust the format if your connection cannot carry the stream steadily.
The live-ingest figures: 6 Mbps minimum, 17 Mbps recommended
YouTube’s live encoder table gives two values for H.264 at 1080p60: 6 Mbps minimum and 17 Mbps recommended. The figures describe the video bitrate sent from your encoder to YouTube, not your internet package speed and not a guaranteed viewing bitrate for every person watching.
Use 17 Mbps as the recommended starting point when the connection has enough dependable upload capacity for the stream’s total bitrate. If it does not, do not simply enter 17 Mbps and hope that the connection catches up. A stream that repeatedly exceeds available upload bandwidth can lose stability; reducing the resolution or frame rate may be more useful than holding on to 1080p60 at an unsustainable rate.
The minimum is a floor in YouTube’s settings table, not a promise that every picture will look good at 6 Mbps. Fast motion, detailed scenes, text, and visual noise can be harder to encode clearly than a mostly still devotional image or a static study scene. The content matters, but the listed recommendation remains 17 Mbps for this format.
YouTube’s live encoder settings and bitrate table separates codec, resolution and frame rate. Keep those dimensions together when you choose a number: a bitrate listed for 1080p30 or 720p60 is not the same recommendation as H.264 1080p60.
Confirm resolution, frame rate and codec
Before changing bitrate, check what the encoder is actually sending. A project or canvas set to 1080p does not by itself prove that the outgoing stream is 1080p60. Confirm the output resolution, frame rate and video codec in the encoder’s stream settings, and compare them with the format you intend to use.
For the subject here, the relevant combination is H.264, 1920 by 1080 output and 60 frames per second. YouTube supports other codecs, including H.265 and AV1, but their guidance has separate settings. Do not carry an H.264 figure across to a different codec unless YouTube’s current table says it applies.
A useful comparison makes the trade-off explicit:
| H.264 live-ingest format | Minimum bitrate | Recommended bitrate |
|---|---|---|
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps |
These values are YouTube’s live ingestion guidance, not prerecorded-video upload guidance. If the 17 Mbps target is not sustainable, compare the lower formats against what viewers need. A lecture with a speaker and slides may remain legible at a lower frame rate; a channel showing movement may value 60 fps more. Make a test with the actual content rather than deciding from the numbers alone.
The encoder protocol also matters. YouTube’s guidance covers RTMP/RTMPS, and it recommends RTMPS for the encrypted connection to the live service. If the encoder asks for a protocol, follow the current YouTube setup instructions rather than changing protocol and bitrate at the same time. Its encoder setup guide walks through creating a stream with an encoder.
Set H.264 bitrate and related encoder options
In your encoder, choose H.264 for video and use constant bitrate, usually shown as CBR. Enter the video bitrate in the units the encoder requests. If it asks for kilobits per second, 17 Mbps is 17,000 Kbps; 6 Mbps is 6,000 Kbps. Check that the field is for video rather than a combined audio-and-video total.
YouTube recommends a two-second keyframe interval and says not to exceed four seconds. Set the interval to two seconds where your encoder exposes the setting. YouTube also recommends progressive scan, square pixels, two B-frames, one reference frame and CABAC among advanced H.264 options. Not every simple encoder exposes all these controls, so set what is available and verify the output rather than assuming a hidden default.
Audio uses bandwidth too. YouTube lists AAC or MP3 as supported audio codecs, and 128 Kbps for stereo audio. A 17 Mbps video stream plus audio uses more upload capacity than the video figure alone. In practical terms, leave margin for audio and for ordinary variation in the connection, rather than treating a speed-test result equal to the video setting as sufficient.
Do not confuse a bitrate field with quality presets. A preset can change how much work the encoder does to compress each frame, while bitrate controls how much data it sends over time. If the computer cannot encode smoothly, a slower preset may produce dropped frames even when the connection is strong; a network problem can cause delivery issues even when the computer has spare capacity. Diagnose those separately.
If you use OBS or another desktop encoder, the control names may differ. The principles remain: select the intended H.264 output, configure CBR, set the target bitrate and keyframe interval, then confirm the actual output format. For an always-on music channel, the practical examples in YouTube encoder settings for 24/7 Indian music streaming can help you think through a continuous broadcast, but check the current official values for your own format.
Check available upload bandwidth
The 17 Mbps recommendation is conditional on sustainable upload capacity. YouTube cautions that the total bitrate being streamed cannot exceed the available upload bandwidth. The useful question is therefore not just “What did my connection reach once?” but “Can it hold the stream’s total data rate steadily while other activity continues?”
Run an upload test from the same connection and, as far as possible, the same location and time of day as the planned broadcast. A result from a quiet afternoon may not represent the evening when household devices, a shop’s point-of-sale system or other users are active. Wi-Fi conditions can also change with distance and interference. A wired connection can make testing more consistent, though it cannot create more capacity than the internet connection provides.
Account for competing upload activity: cloud backups, file transfers, security cameras and other streams can consume capacity. Pause or schedule such work during the test. Leave headroom rather than planning to use every measured megabit for the live encoder. If the connection’s performance varies, select a lower target or format that it can sustain instead of chasing its best single result.
If your measured upload is not reliably above the stream’s total bitrate, step down and test again. You can reduce the bitrate, move from 1080p60 to 1080p30, or use 720p60, according to the content’s needs. The comparison table above shows YouTube’s values for those H.264 formats. A smaller frame can be a sounder choice than frequent interruptions at a larger one.
For background on common causes and fixes, see common live-streaming challenges and how to fix them. It is particularly useful to distinguish a limited connection from encoder overload: both can harm a stream, but changing bitrate will not fix a computer that cannot encode its frames in time.
Test before going live
YouTube advises testing before a live stream. Do a private or unlisted test where appropriate, using the same encoder, connection, video, frame rate, bitrate and audio setup you intend to use. Let it run long enough to expose fluctuations or heat-related performance problems rather than checking only whether it starts.
Watch the encoder’s statistics while the test runs. Look for dropped frames caused by network conditions, skipped or lagged frames caused by encoding, and a stable output bitrate. A brief initial connection is not enough evidence that a 24/7 channel will remain steady overnight. Test at a time that resembles the real operating conditions, including any other devices or work that will share the connection.
If the test is unstable, change one factor at a time. First check whether the problem is network-related or encoder-related. For network drops, lower the video bitrate or choose a less demanding format, then repeat the test. For encoding lag, reduce encoder workload or output complexity and test again. Record the settings that worked, so a restart does not require guessing.
A test also checks the material itself. Look at small text, moving titles, transitions and the most detailed part of the video on a normal viewer screen. A rate that remains stable may still not preserve the details you need. Conversely, a still image with gentle movement may not benefit as much from 60 fps as a fast-moving scene. Choose by what viewers need to see, within a stable connection budget.
Monitor stream health during operation
Once live, do not assume the original test settles every later question. Keep an eye on YouTube’s live control room and the encoder’s own status. If the preview reports connection trouble or the encoder shows network drops, compare the actual send rate with the sustainable upload capacity and check whether other traffic has started.
If the signal is stable but the image looks soft, investigate whether the encoder is sending the intended resolution and bitrate before raising the target. Check that the selected profile has not reverted, and that the live stream is not configured for a different frame rate. YouTube’s live settings are ingestion guidance; the platform processes the received stream for viewers, so the number entered in your encoder is not a promise of identical playback quality at every viewing connection.
For a channel that must remain on, consider what happens when the computer, encoder or home connection fails. A desktop setup leaves you responsible for the machine, software and connection, and restarting after a crash can take the stream offline until someone intervenes. The article on what happens when OBS crashes during a church sermon stream explains that operational risk. Where the recurring task is keeping an uploaded video broadcasting while your own computer is switched off, StreamNeo removes the need to keep that computer running and to restart the broadcast manually if it drops.
Whatever operating arrangement you use, maintain a simple note of the chosen format, bitrate and test result. Revisit it after changing the internet plan, router placement, encoder, content or schedule. A result from an earlier setup is not proof that today’s connection has the same capacity.
Keep live settings separate from upload-video settings
A live stream and a prerecorded video upload are different workflows. During a live broadcast, the encoder sends a continuing stream to YouTube, so your outbound connection must carry the total bitrate in real time. Uploading a finished file instead sends a completed video; YouTube publishes a separate set of recommendations for that encoding workflow.
That distinction matters because a number from the upload page does not answer the live-ingest question. For live H.264 at 1080p60, use the live encoder table’s 6 Mbps minimum and 17 Mbps recommended figures. For a finished file, consult YouTube’s recommended upload encoding settings rather than reusing the live table.
Likewise, a 17 Mbps live setting does not mean every viewer receives a 17 Mbps copy. It describes the bitrate you configure for the outgoing live feed, subject to your encoder and connection. YouTube’s processing and each viewer’s playback conditions are separate parts of the delivery path.
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 1080p 60fps on YouTube Live?
For H.264 live ingestion, YouTube lists 17 Mbps as recommended and 6 Mbps as the minimum. Use the recommended target only when your connection can sustain the stream’s total bitrate reliably; otherwise test a lower bitrate or format.
Is 6 Mbps the recommended quality target?
No. It is YouTube’s listed minimum for H.264 at 1080p60, not the recommended target. The recommended figure is 17 Mbps, conditional on available upload capacity.
Does the 17 Mbps setting apply to uploading a finished video?
No. It is a live-ingest recommendation for a particular codec, resolution and frame rate. YouTube publishes separate encoding guidance for prerecorded uploads, so use that page for finished files.
What should I change if my connection cannot sustain 17 Mbps?
Test a lower bitrate or compare 1080p30 and 720p60 using YouTube’s H.264 live settings. Choose the format that preserves the important parts of your content while remaining stable in a test on the connection you will actually use.