For a 1080p stream at 60 frames per second, YouTube’s live encoder guidance recommends 17 Mbps for H.264 or 12 Mbps for AV1 or H.265 (HEVC). Those are codec-specific recommendations, not interchangeable presets; your encoder, connection and actual stream should be checked before you rely on either figure.
The listed minimums are lower—6 Mbps for H.264 and 4 Mbps for AV1 or HEVC—but a minimum is not a promise of good-looking video. Set the stream for the codec you will actually send, use CBR and the prescribed keyframe interval, then run a representative test and watch YouTube’s stream-health messages.
Choose the bitrate for the codec you send
YouTube’s live encoder table gives these figures for 1080p at 60 fps:
| Ingestion codec | Recommended video bitrate | Listed minimum | Practical reading |
|---|---|---|---|
| H.264 | 17 Mbps | 6 Mbps | Use the H.264 recommendation as the starting point when your encoder sends H.264. |
| AV1 | 12 Mbps | 4 Mbps | Use the AV1 recommendation when the encoder and the chosen ingest path send AV1. |
| H.265 (HEVC) | 12 Mbps | 4 Mbps | Use the HEVC recommendation when the incoming stream is H.265. |
The settings come from YouTube’s live encoder guidance. Keep resolution, frame rate and codec together when reading it: the row is for a 1080p60 live stream, and the recommendation is not a general bitrate for every 1080p broadcast. If your feed is 30 fps, a different resolution, or a different codec, consult the matching entry rather than carrying these numbers across by assumption.
Bitrate is the amount of encoded video data sent each second. It is a setting on the outgoing feed, so the practical question is not merely “What bitrate is best for 1080p?” but “What codec and format is this encoder sending to YouTube?” A preset labelled 1080p60 is incomplete if you do not know its codec or rate control mode.
Treat the recommended value as YouTube’s starting point for that specified format, not a guarantee that the image will suit every source or that the connection will hold. A detailed, fast-moving picture can make compression more visible than a mostly static scene. A quiet devotional image, a lofi animation, a news loop and a moving concert shot do not present identical material to the encoder, even when all are set to 1080p60.
That does not justify choosing a lower number by guesswork. First match codec, resolution and frame rate to the table; then test the actual scene and check both local encoder statistics and YouTube’s stream health. If a setting causes dropped frames or unstable delivery, investigate the connection and configuration instead of treating a lower figure as automatically acceptable quality.
Minimums are not quality targets
The 6 Mbps H.264 and 4 Mbps AV1/HEVC figures are listed minimums for the same 1080p60 format. They are useful as a boundary in YouTube’s guidance, but they should not be mistaken for the recommended rate or a threshold at which every picture will look clean. The minimum does not account for your content, encoder behaviour, network variation or what viewers will consider acceptable.
A stream can be technically connected and still show blockiness, smeared motion or other compression artefacts. Conversely, seeing a number above the listed minimum does not prove that the feed is configured correctly. Resolution, frame rate, codec, rate control, audio and connection all matter to the delivered result.
If your upload connection cannot carry the recommended setting reliably, do not assume that selecting the minimum fixes the underlying problem. Lowering the bitrate can reduce the amount of data the encoder sends, but it may also make the picture less detailed. You can also choose a lower resolution or frame rate and use the corresponding YouTube guidance, rather than claiming a 1080p60 stream while using an unsupported combination of assumptions.
A sensible decision is to decide what the channel needs first. If 60 fps is important for fast movement, test it at the recommended codec-specific rate. If the channel is a largely static image and the connection is constrained, compare a different supported output format in a test. Do not present either compromise as equivalent without checking the resulting picture.
For a continuous playlist, a fixed image and a scene with motion may put different demands on the encoder. The guide to keeping a 24/7 rain stream smooth across loops is relevant when the source itself changes at loop points: bitrate cannot hide a visible cut or a badly joined transition. Inspect a full loop rather than judging a single still frame.
Why the codec changes the target
H.264, AV1 and H.265 are different ways of encoding the picture. YouTube lists a distinct 1080p60 bitrate recommendation for H.264 and a lower listed figure for AV1 or H.265. That is why a codec-blind answer such as “use this bitrate for 1080p60” leaves out the setting that determines which row applies.
Do not infer from those figures that AV1 or HEVC will always look better at a particular rate, or that a lower number is inherently preferable. The source guidance supplies encoder settings; it does not establish a universal quality ranking for all encoders, scenes and viewers. Compatibility also matters: the encoder and chosen stream path must support the codec you intend to send.
Before changing a codec, confirm what the encoder is actually outputting. An option may be available in software but not used by the active profile, or the stream may be configured for a different ingest workflow than expected. Set the codec deliberately, check the outgoing stream information, and then use that codec’s row in the live guidance.
Keep live ingestion separate from uploading a finished video. YouTube’s upload encoding recommendations list 12 Mbps for 1080p high-frame-rate SDR uploads. That figure belongs to file encoding for an upload, not the live H.264 recommendation of 17 Mbps at 1080p60. The upload page discusses a different workflow and should not be used to replace live-stream settings.
This distinction matters when you repurpose a recorded file as a live loop. The file’s export bitrate is not automatically the bitrate of the outgoing live stream; the encoder can decode and re-encode the file for its live output. Check the live output profile rather than assuming the file’s properties dictate the stream settings.
Set CBR and the keyframe interval
YouTube’s live guidance specifies constant bitrate encoding (CBR) and recommends a keyframe interval of 2 seconds, not exceeding 4 seconds. In an encoder, rate control may be labelled CBR, while the keyframe interval can be labelled keyframe distance or GOP length. Read the unit carefully: some encoders ask for seconds and others for frames.
At 60 frames per second, a two-second interval corresponds to 120 frames. If the application asks for frames, enter the value that represents the two-second interval at the configured frame rate; if it asks for seconds, use two seconds. Do not confuse the frame count with a bitrate or type a frame count into a field that expects seconds. YouTube’s ceiling is no more than four seconds, so do not set a longer interval.
CBR aims to keep the encoded output at a steady target rate over time. That makes the stream’s upload demand more predictable than a variable-rate setting that can rise and fall with scene complexity. It does not mean every frame contains the same picture information, nor does it guarantee a stable internet connection. CBR is the encoder setting; your connection still needs to sustain the outgoing feed.
In OBS or another encoder, check the active profile rather than relying on the name of a saved preset. Confirm output resolution and frame rate, select the intended codec, set CBR, enter the bitrate for that codec, and set the keyframe interval. Then verify that the profile is actually selected for the live output. A correct value in an unused profile has no effect on the broadcast.
For a channel that runs unattended, configuration discipline matters because a profile change can quietly alter the outgoing stream. Keep a written record of codec, bitrate, frame rate and keyframe interval, especially if more than one person operates the channel. The OBS playlist loop troubleshooting guide can help you separate an encoder or scene-change problem from a general network issue when a stream drops during a transition.
Check the picture format and encoder options
YouTube’s encoder guidance also lists progressive scan, square pixels, two B-frames, one reference frame and CABAC among its advanced settings. For SDR it lists Rec. 709 colour and 8-bit depth. Treat these as format guidance to compare against your encoder, not as a reason to enable unrelated options or to change the codec-specific bitrate.
Progressive scan means the picture is encoded as complete frames rather than interlaced fields. Square pixels are the ordinary pixel-shape assumption for typical computer and online video content. If your encoder exposes these choices, match the listed guidance and confirm that the resulting output is still 1080p at 60 fps. An unexpected aspect ratio or interlaced output can make a nominal resolution misleading.
The B-frame, reference-frame and CABAC entries are encoder parameters, most commonly visible in an advanced profile. Their presence in YouTube’s guidance does not mean every app exposes them in the same way. If a setting is unavailable, consult the encoder’s documentation and avoid forcing a profile or command-line value you cannot verify. The important thing is to check the actual output and stream health rather than assume a preset name represents every parameter.
For SDR, use the Rec. 709 colour space and 8-bit depth listed by YouTube. Keep HDR advice separate from this article’s 1080p60 SDR comparison: YouTube’s guidance treats HDR as a distinct workflow and notes codec considerations for it. Do not switch an SDR devotional loop or news graphic into HDR simply because an encoder offers the option. Make sure source and output colour settings agree so the stream does not arrive washed out or unnaturally saturated.
Inspect a representative scene after setting the profile. Look for text edges, gradients, moving details and changes in brightness, not only a static thumbnail. A local preview can reveal colour or scaling errors, while a YouTube test can show whether the signal is reaching the platform as expected. For a live event with overlays, the virtual event streaming guide is useful for planning the production around the feed, but its content choices do not override the encoder settings above.
Configure audio for the stream
YouTube lists stereo audio at 44.1 kHz and 128 kbps. For 5.1 audio, the listed guidance is 48 kHz and 384 kbps, and 5.1 over RTMP or RTMPS is supported only with AAC. These are audio settings, separate from the video bitrate table; do not add them to the video bitrate when choosing the video target.
For a typical two-channel devotional, study or ambience stream, stereo is usually the relevant configuration. Select the sample rate and audio bitrate in the encoder, then listen to the output rather than relying solely on the numbers. Check for clipping, silence, channel imbalance and an audio-video sync problem. A clean video setting cannot correct a poor source mix or a cable that has become disconnected.
Choose 5.1 only when the programme is genuinely mixed for it and the full encoding path supports it. A stereo source does not become useful surround audio by selecting a 5.1 output mode. If the stream uses RTMP or RTMPS, follow YouTube’s AAC condition for 5.1, and test the channel layout at the receiving end.
Audio also belongs in the preflight. A test with music, voice or ambient sound like the planned programme can catch issues that a silent test misses. Keep a short checklist: is the right input selected, are levels clear, does the stream remain in sync after a scene change, and does it still sound right after the programme loops?
Test upload capacity and watch stream health
YouTube advises choosing a stream quality that is reliable for the available internet connection and recommends running an upload-speed test. A speed-test result is a snapshot, not proof that a connection will hold a continuous stream through congestion or a router interruption. Run it on the connection and at the location you plan to use, and repeat the test if the result varies substantially.
The guidance does not specify a universal upload-speed margin above the video bitrate. Do not attribute a made-up buffer figure to YouTube. Instead, test whether the actual connection can sustain the configured stream, including audio, and whether performance remains stable during the hours and conditions that matter to your channel. Other traffic on the same connection can affect what is available to the encoder.
Before going live, test with audio and movement similar to the planned programme, as YouTube recommends. For a bhajan channel, test a section with vocals and instruments; for a local news loop, test scrolling text or a clip with movement; for a lofi station, include the animation and audio that will run overnight. A still desktop capture is not a useful substitute if the real content contains motion or overlays.
During the test, check the encoder’s dropped-frame and connection indicators, then check YouTube’s stream health and messages. The guide to diagnosing buffering with OBS stats and dropped-frame counts helps distinguish local encoding or network trouble from viewer-side playback symptoms. If YouTube reports a problem, address the message and repeat the test rather than assuming a bitrate change alone will solve it.
For a 24/7 channel, make a test long enough to include the routine conditions that could matter: loop transitions, scheduled scene changes, audio variations and the machine’s normal background workload. If the live feed must continue while your own computer is off, StreamNeo removes the specific burden of leaving that computer running for a file-based YouTube stream; it does not remove the need to choose and test the stream’s picture and audio settings. Keep a contact route and an operating checklist for whoever will respond if the stream-health status changes.
YouTube recommends RTMPS, describing it as a secure extension to RTMP. Use it when your encoder supports it. HLS may be relevant where an encoder cannot provide the needed capabilities over RTMP, but do not change protocol casually: verify the encoder and YouTube setup match. These protocol notes do not alter the 1080p60 bitrate figures above.
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 1080p60 on YouTube Live?
YouTube’s live guidance recommends 17 Mbps for H.264 and 12 Mbps for AV1 or H.265 at 1080p60. Use the figure for the codec your encoder sends, and test the output; neither number guarantees a particular picture quality or an uninterrupted connection.
Are YouTube’s listed minimums enough for a good stream?
The listed minimums for this format are 6 Mbps for H.264 and 4 Mbps for AV1 or HEVC. They are minimum figures, not assurances of good quality, and the result depends on the scene, encoder and connection. Check the stream in a representative test before relying on it.
Should the keyframe interval be two seconds or 120 frames?
YouTube recommends a two-second interval and says not to exceed four seconds. At 60 fps, two seconds is 120 frames, but enter the value in the unit your encoder requests. Check the field label before applying the setting.
Does the 12 Mbps upload recommendation apply to a live H.264 stream?
No. YouTube’s separate upload guidance lists 12 Mbps for 1080p high-frame-rate SDR file uploads, while its live H.264 guidance recommends 17 Mbps for 1080p60. Use the live encoder table for a live broadcast and the upload page for an uploaded file.