For 1080p at 60 frames per second, YouTube’s current live-ingest recommendation is 17 Mbps with H.264, or 12 Mbps with AV1 or H.265/HEVC. The codec matters, so there is no single best bitrate for every 1080p60 encoder.
Those figures are settings for the video encoder sending your broadcast to YouTube. They are not a guarantee that your internet connection can sustain the stream, nor a promise that every viewer will receive the same quality.
The quick answer: choose by codec
Start by checking which codec your encoder is using. For the same 1080p60 output, YouTube lists different minimum and recommended bitrates for H.264 and for the newer AV1 or H.265/HEVC codecs.
| 1080p at 60 fps | Minimum bitrate | Recommended bitrate |
|---|---|---|
| H.264 | 6 Mbps | 17 Mbps |
| AV1 or H.265/HEVC | 4 Mbps | 12 Mbps |
These are the current figures in YouTube Help’s live encoder settings guidance, checked on 3 October 2026. The page does not display a publication date, so the date here records when the guidance was verified rather than when YouTube first published it.
If you are using H.264, set the video bitrate to 17 Mbps when your connection can reliably support it. If you are using AV1 or H.265/HEVC, set it to 12 Mbps. Do not use 12 Mbps simply because it is a commonly repeated 1080p60 figure: at this frame rate, YouTube’s listed H.264 recommendation is 17 Mbps.
The recommendation is not a target for your broadband package in isolation. Your connection must carry the encoder’s output continuously, along with normal network activity and any audio being sent. A speed test can show available upload capacity at one moment, but it cannot by itself prove that an overnight or 24/7 broadcast will remain stable.
The codec also affects what your encoder and playback devices can handle. H.264 is widely supported and may be the practical choice for older hardware. AV1 or H.265 can use a lower listed bitrate for this YouTube ingest setting, but you need an encoder that supports the chosen codec reliably and a workflow that has been tested from end to end.
Minimum is not the recommended setting
YouTube lists 6 Mbps as the minimum for H.264 at 1080p60, and 4 Mbps as the minimum for AV1 or H.265 at the same resolution and frame rate. A minimum is a lower boundary in the encoder guidance, not the setting you should choose automatically.
At a minimum bitrate, detailed or fast-moving pictures have less data available for each frame. A devotional channel with a largely static artwork screen may look acceptable at a lower rate in some scenes, while a gaming stream, moving camera, dance performance or local news loop may show more visible compression. The frame rate remains 60 fps, but bitrate and motion still affect the amount of detail preserved.
The recommended figure gives YouTube’s ingest process more room than the listed minimum. It still does not guarantee a clean picture for every viewer. YouTube processes a live stream for delivery, and viewer quality can vary with the viewer’s device, connection and available playback version.
There is also a practical difference between a stream that looks acceptable in a short test and one that runs through changing network conditions overnight. If you select the minimum merely because a speed test reached that level, a small reduction in upload performance can leave the encoder unable to send its full output. That is why the bitrate recommendation and the connection test should be considered together.
Do not reduce the bitrate as a first response to every quality problem. First check the selected codec, resolution, frame rate, keyframe interval, dropped frames and stream-health messages. If your connection cannot reliably sustain the recommended value, choosing a lower output resolution or frame rate may be more dependable than forcing 1080p60 at a rate your network cannot maintain.
For a 24/7 channel, this distinction matters particularly because the stream is not judged only by the first few minutes. A short test can miss congestion that appears later, a household upload task, a router issue or an encoder process that gradually stops sending correctly.
Set the encoder bitrate and related live settings
In your encoder, create a 1080p60 profile and select the codec before entering the bitrate. Use 17 Mbps for H.264 or 12 Mbps for AV1 or H.265/HEVC when following YouTube’s current recommended live-ingest settings. Enter the bitrate as a constant value rather than allowing it to vary freely.
YouTube’s live encoder guidance lists constant bitrate encoding, usually shown in software as CBR. It also recommends a keyframe interval of two seconds and says not to exceed four seconds. A two-second interval is therefore the sensible starting point for this setup.
If you use OBS, the keyframe setting is easy to overlook because it sits away from the main resolution controls. This guide to setting keyframes in OBS for YouTube Live explains where to look and why the interval affects the way YouTube receives the stream.
Use a progressive scan and square pixel aspect ratio for a conventional 1080p live output. YouTube’s advanced guidance also lists two B-frames, one reference frame, CABAC and Rec. 709 for SDR. These are secondary to selecting the correct codec and bitrate, but they help you avoid a profile that is unusual or unnecessarily difficult for the platform to process.
For audio, YouTube lists AAC or MP3 as options. Keep the audio setting stable throughout the broadcast. A silent or broken audio track can make a technically healthy video stream feel faulty, particularly for bhajan, lofi, ambience, lecture and news channels where sound is part of the main reason viewers stay.
The protocol options listed by YouTube include RTMP and RTMPS. YouTube recommends RTMPS and describes it as an encrypted option. Use the protocol supported by your encoder and follow YouTube’s current instructions when creating or copying the stream key. Never place a stream key in a public screenshot, blog post or shared document.
If you are repeating a file rather than capturing a live camera or desktop, check the source before deciding that the encoder is at fault. A source video with a lower frame rate cannot gain real motion detail merely because the output profile says 60 fps. Likewise, scaling a small source up to 1080p does not create the detail of a native 1080p recording.
Check upload capacity and leave practical headroom
YouTube advises choosing a quality level that your internet connection can reliably support and running an upload-speed test. It does not provide a universal upload-headroom formula in the cited live encoder guidance, so do not treat a particular margin as an official YouTube rule.
The useful question is not whether your connection briefly reports more than 17 Mbps. It is whether the connection can keep sending an H.264 stream configured at 17 Mbps while other traffic, protocol overhead and normal variation are also present. The same principle applies to a 12 Mbps AV1 or H.265 stream.
Run the test on the same connection and, where possible, the same network arrangement that will carry the broadcast. Test at the time you expect to stream, since a connection that looks comfortable during a quiet afternoon may behave differently when other people in the home or workplace are online.
Pause large uploads, cloud backups and software updates while testing. Then repeat the test rather than relying on a single result. A wired connection can be a sensible troubleshooting step when Wi-Fi is fluctuating, but a Cat 6 cable does not guarantee that your internet service can sustain a bitrate. It only removes one possible source of instability between the encoder and the router.
If your available upload capacity is close to the configured video bitrate, treat the setup as fragile. You may see dropped frames when other traffic starts, even though the encoder settings are correct. If the connection is shared, ask what else is using the upload path before increasing the bitrate or blaming YouTube.
A local news loop or study channel may not need 60 fps at all. If the content is mostly slides, a talking head, scripture pages or slow ambience, 30 fps may be a better fit for the actual material and connection. That is a change to the production requirement, not a claim that YouTube’s 1080p60 recommendation is wrong.
For a channel that must continue while your computer is off, moving the repeated file to a cloud-based workflow can remove the need to keep a home upload connection and desktop running continuously. StreamNeo is designed for this particular hand-off: you upload the file once, add your YouTube stream key, and the broadcast can continue with automatic monitoring and restart handling. You still need to select and test an appropriate YouTube encoder profile, and the service is for YouTube only.
Test with a representative stream before going live
YouTube’s direct advice is simple: “Make sure to test before you start your live stream.” The important detail is what you test. Use audio and video movement similar to the planned broadcast, rather than checking only a still image or a few seconds of silence.
For a 24/7 bhajan stream, test a section containing music, artwork changes and any transitions that will repeat. For a gaming channel, include actual game movement. For lectures, include slides changing and speech. For a local news loop, include the most detailed ticker, map or lower-third graphics. A quiet opening scene may hide a problem that appears when the picture becomes busy.
Before the public broadcast, confirm the output resolution is 1920 by 1080, the frame rate is 60 fps, and the codec matches the bitrate you selected. A setting copied from an old profile can silently change one of these values. The number in the bitrate box is meaningful only alongside the codec, resolution and frame rate.
Use YouTube Studio’s preview and stream-health information during the test. Look for messages about the incoming stream, dropped frames, unstable upload performance or missing audio. YouTube’s official live streaming help centre is the appropriate place to check current product instructions if the Studio interface changes.
Keep the test running long enough to observe the complete path from source to YouTube. The exact duration of a useful test depends on your setup and content, and YouTube’s cited guidance does not set a universal testing duration. The aim is to expose repeatable problems before viewers find them, not to satisfy an arbitrary timer.
During the event, continue watching stream health and messages rather than assuming that a successful start means the problem is solved. If the encoder reports that it cannot send data quickly enough, first check whether the upload path is busy or fluctuating. If the connection is stable but the encoder is overloaded, check CPU or hardware-encoder load and the source format.
A healthy stream can still have a poor source. Inspect the file or camera feed for black frames, frozen sections, clipped audio and incorrect aspect ratio. YouTube can receive a stable signal while faithfully delivering a source that was already wrong.
Live ingest bitrate is not uploaded-video bitrate
The 17 Mbps and 12 Mbps figures in this article are for live ingestion at 1080p60. They tell your encoder how much video data to send to YouTube while the broadcast is happening. They are not universal export settings for a video file that you upload to YouTube in advance.
An uploaded video has a different workflow. You prepare the file, upload it, and YouTube processes it for playback. A live broadcast has to be encoded and delivered continuously while the event is taking place. Treating a live-ingest table as an upload-export table can lead to a file that is unnecessarily large, a live stream that uses the wrong rate, or both.
The distinction is especially important for people who publish a long looping video and then send it as a live channel. The source file may have been exported at one bitrate, while the live encoder creates a separate output stream at another. Changing the file’s export bitrate does not automatically change the live encoder’s bitrate.
Similarly, increasing the live bitrate cannot restore detail that was removed when the source was compressed. If a devotional artwork was exported with muddy text or a lofi animation was scaled from a small file, sending that source at 17 Mbps will not recreate missing detail. Improve the source separately from the live-ingest profile.
Keep a record of the working settings for each channel. Write down the source resolution and frame rate, output codec, live bitrate, audio format, keyframe interval and connection used for testing. That makes it easier to distinguish a change in the video file from a change in the internet connection when the next broadcast behaves differently.
If the channel runs on a playlist, also check what happens at the transition between files. A black frame, silence or unexpected resolution change may be a playlist or source issue rather than a bitrate issue. This guide to running a playlist continuously on YouTube Live covers the operational side of repeated video sources, while the bitrate remains a separate encoder decision.
A practical setup for an always-on channel
Begin with the content rather than the number. Decide whether 60 fps genuinely helps the viewer. Fast gameplay and moving camera work can benefit more from 60 fps than a static prayer image, a study timer or a slowly changing ambience loop. If 60 fps is part of the channel’s purpose, keep it consistent from source through encoder.
Next, identify the codec currently selected by the encoder. Write it down before changing the bitrate. H.264 means the YouTube recommended figure for this exact 1080p60 case is 17 Mbps. AV1 or H.265/HEVC means the listed recommendation is 12 Mbps. The minimums are 6 Mbps and 4 Mbps respectively, but they should not be confused with the recommended values.
Then configure CBR and a two-second keyframe interval, confirm the audio track, and check that the protocol and advanced settings are compatible with the encoder. Run an upload test on the actual network, then perform a representative test through YouTube Studio.
Once the stream is live, watch the health messages and dropped-frame indicators. Do not change several settings at once. If you lower the bitrate, change only that first and observe the result. If you change the codec, resolution and frame rate together, you will not know which change solved or caused the problem.
For a home-run channel, investigate the reason for every interruption. This troubleshooting guide for OBS stopping after a few hours is relevant when the local encoder stops even though the internet connection appears available. It is separate from a YouTube ingest problem, and the remedy may involve the computer, source, software or network rather than bitrate.
For a channel serving a specific audience, make the choice in context. A study channel may value a steady, readable picture over maximum motion smoothness. A music channel may need clean audio and uninterrupted delivery more than a high frame rate. A gaming channel may reasonably prioritise 1080p60, but only after its encoder and upload path have passed a representative test.
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 YouTube Live?
Use 17 Mbps when the encoder is using H.264. Use 12 Mbps when it is using AV1 or H.265/HEVC. These are YouTube’s current recommended live-ingest settings, not a guarantee that your connection or every viewer can support them.
Is 12 Mbps enough for a 1080p60 YouTube stream?
It is YouTube’s listed recommendation for AV1 or H.265/HEVC at 1080p60. For H.264, YouTube lists 17 Mbps as the recommendation, so 12 Mbps should not be presented as a codec-independent answer.
What is the minimum bitrate for 1080p60?
YouTube lists 6 Mbps as the H.264 minimum and 4 Mbps as the AV1 or H.265/HEVC minimum. Minimum does not mean ideal, and you should test representative movement and audio before relying on either value for a live broadcast.
Does a 17 Mbps bitrate guarantee good YouTube quality?
No. The bitrate is an encoder setting for the stream sent to YouTube. Connection stability, encoder performance, source quality, YouTube processing and the viewer’s playback conditions can all affect the result, so monitor stream health and test before going live.