YouTube’s published live encoder guidance lists frame rates up to 60 fps and bitrate recommendations for incoming streams from 360p through 2160p (4K). For 2160p60, YouTube recommends 35 Mbps for AV1 or H.265 (HEVC), and 50 Mbps for H.264; those are encoder input recommendations, not a promise that each viewer will receive 4K.
For most streams, leave YouTube’s resolution and frame-rate detection on automatic. Choose manual settings only when you have a reason to control the incoming mode and can configure the encoder to match it; YouTube still creates multiple output formats for viewers.
What encoder resolution and frame-rate limits mean
An encoder takes your source video and sends an encoded live stream to YouTube. The input resolution is the size of the video you send, such as 1920 × 1080 for 1080p. Frame rate describes how many frames per second the encoder sends. These are properties of the incoming signal, not a list of playback choices that will necessarily appear identically for every viewer.
YouTube’s current encoder settings guidance lists frame rates up to 60 fps and shows bitrate recommendations for resolutions as high as 2160p. That is useful when deciding what mode to configure in software or hardware, but it is not a blanket statement that every combination of resolution, codec, and feature is available in every workflow. Follow the documented modes and the requirements of your encoder.
The bitrate table specifies a minimum and a recommended bitrate for each listed resolution and frame rate, split by codec. A minimum is not a target that guarantees a clean broadcast. A recommended value is YouTube’s published setting for that input mode, not a guarantee that a connection, encoder, or source will perform reliably at that rate. You still need to test the complete path before relying on it overnight.
For example, a channel that sends a 1080p30 H.264 input is working with a different table row from a 1080p60 stream or a 2160p60 AV1 stream. Changing only the bitrate does not turn one of those modes into another: resolution, frame rate, codec and bitrate work together as encoder settings.
YouTube lists RTMP and RTMPS as input protocols and recommends RTMPS. Its settings page also recommends constant bitrate encoding and a two-second keyframe interval, and says not to exceed four seconds. These settings are related to how the encoder sends the stream; they do not alter the published resolution and frame-rate scope. See YouTube’s live encoder settings and bitrate guidance when choosing a configuration.
YouTube’s listed resolutions and frame rates
The settings table covers 360p and 480p at 30 fps; 720p, 1080p and 1440p at 30 or 60 fps; and 2160p (4K) at 30 or 60 fps. YouTube describes frame rates up to 60 fps. The page does not list a 120 fps encoder mode, so do not configure a stream on the assumption that a higher frame rate is documented for YouTube Live.
The table below transcribes YouTube’s published bitrate values. All values are Mbps. “Minimum” and “recommended” are YouTube’s labels for encoder bitrate settings. They are not independent measurements of the upload speed needed in every household, nor guarantees of stream stability.
| Incoming mode | AV1 / H.265 minimum | AV1 / H.265 recommended | H.264 minimum | H.264 recommended |
|---|---|---|---|---|
| 2160p60 | 10 | 35 | 14 | 50 |
| 2160p30 | 8 | 30 | 11 | 42 |
| 1440p60 | 6 | 24 | 8 | 34 |
| 1440p30 | 5 | 15 | 7 | 21 |
| 1080p60 | 4 | 12 | 6 | 17 |
| 1080p30 | 4 | 10 | 5 | 14 |
| 720p60 | 2 | 6 | 3 | 8 |
| 720p30 | 2 | 6 | 3 | 8 |
| 480p30 | 0.3 | 3 | 0.4 | 4 |
| 360p30 | 0.3 | 3 | 0.4 | 4 |
The figures in the table are current YouTube guidance accessed in 2026; the Help page does not show a publication date. YouTube’s table distinguishes AV1 and H.265 together from H.264, so keep the right column for the codec your encoder actually sends. Do not treat an AV1/H.265 figure as an H.264 recommendation simply because the resolution and frame rate match.
The appropriate row depends on the mode you can produce and sustain. A still devotional image with a gentle visual loop may not benefit from 60 fps in the same way as fast movement or gameplay. A news loop with scrolling text may need careful checking for legibility and motion. Choose based on your source and the encoder’s supported output, not only on the largest number in the table.
2160p60: bitrate depends on codec
The clearest case for keeping codec distinctions visible is 2160p60. YouTube recommends 35 Mbps for AV1 or H.265, and 50 Mbps for H.264. The corresponding minimum settings are 10 Mbps and 14 Mbps. Those are different settings for different codecs, not interchangeable ways of describing a single 4K60 target.
If you intend to send H.264, use the H.264 column when configuring bitrate. If your encoder sends H.265 or AV1, use the AV1/H.265 column, provided that codec is supported in the chosen workflow. YouTube’s guidance says AV1 is not supported for HDR. For HDR over RTMP(S), it recommends H.265; if your encoder cannot provide those capabilities with RTMP, YouTube says HLS may be considered. Check the current official instructions and your encoder’s own documentation before choosing a protocol or HDR setup.
A table recommendation is not a substitute for a stable upload connection. The outgoing stream has to be sent continuously, and a line that reaches a speed in a brief test may not behave the same way while other devices are using it or when the stream runs for hours. YouTube advises testing with audio and movement similar to the planned broadcast, checking stream health and messages during the event, and selecting settings that are reliable for the available connection. Do not invent a universal extra percentage or margin: the reviewed guidance does not establish one.
A useful preflight starts with the actual content and intended encoder. Confirm the codec and output mode in the encoder, set the bitrate from the matching row, and test while the connection is in the conditions you expect during the broadcast. If health warnings or interruptions appear, consider a less demanding mode and test again. For a longer-running loop, this is more informative than assuming that a 4K-capable encoder will necessarily hold 4K60 reliably on a particular connection. Practical issues such as inconsistent output can also matter; the guide to fixing stuttering when FFmpeg uses hardware decoding is relevant when the encoder pipeline, rather than the table choice, is the problem.
Automatic detection is the usual starting point
YouTube recommends automatic detection of resolution and frame rate for most encoder streams. In practical terms, send the mode you intend to use from your encoder and let YouTube detect the incoming resolution and frame rate, rather than manually forcing a setting in the live control workflow without a specific need. Automatic detection does not choose a better source for you or remove the need to set the encoder correctly.
Keep the pieces aligned. If the encoder output is 1080p30 but you have selected a manual 2160p60 input expectation, the settings do not describe the same stream. Likewise, using a bitrate associated with one codec while the encoder sends another can lead you to configure against the wrong row. Check the encoder’s output status as well as YouTube’s stream health information when testing.
YouTube automatically transcodes the incoming stream into multiple output formats so people using different devices and network conditions can watch. That happens after the input reaches YouTube. It is a separate operation from the encoder choosing the resolution and frame rate it sends. The distinction is especially useful when setting expectations for a 24/7 channel: your own encoder mode is one input to a delivery system, not a viewer-by-viewer playback guarantee.
Automatic detection is not a reason to skip testing. YouTube recommends a test before going live, using audio and movement like the real programme. Check that the picture and sound arrive as expected and watch for messages in stream health. For an ongoing channel, test the actual playlist or loop rather than a short static screen if the live programme will include movement, transitions or changing audio. A loop workflow can introduce its own problems, as covered in this guide to looping videos on YouTube Live with FFmpeg.
When manual settings and a custom stream key help
Manual selection is relevant when you have a clear operational reason to specify the input mode rather than letting YouTube detect it. YouTube says that manual settings are available with a custom stream key: create or select a custom key, then enable manual settings under Stream Resolution. The labels in the current YouTube interface may change, so consult the official setup page if the controls differ from what you see.
For a manually specified mode, match the encoder’s output to the selected resolution and frame rate. Then use the bitrate recommendation for the same mode and codec. This gives you a defined configuration to test, which can be helpful when you are documenting a repeatable setup across a regular programme or troubleshooting a known mismatch. It does not make the connection more reliable by itself, and it does not force every viewer to receive the input resolution.
For many small channels, manual selection adds little. If the encoder is producing a documented mode and YouTube detects it correctly, automatic handling is the simpler default. Avoid changing settings simply to make a dashboard show a larger resolution. A higher input mode can call for a higher bitrate and more capacity from the encoder and connection; it is only useful if the source and delivery path can support it.
If you are deciding between software and hardware encoding, YouTube’s encoder setup page lists products and software examples, including OBS and Blackmagic Web Presenter 4K. A standalone hardware unit may suit a production that depends on cameras and dedicated equipment, while software can fit a computer-based workflow. The hardware example does not change YouTube’s stated frame-rate scope; it is a way to produce and send a stream. YouTube advises evaluating which encoder fits your own needs rather than treating its list as a comparative test. See YouTube’s encoder setup instructions for its current list and workflow.
If you are sending a prerecorded programme for long periods, decide separately how the file is played, how the encoder keeps running, and what happens after a disconnect. Resolution and frame-rate guidance answers only the input-format question. For a Hindi education channel, for example, the guide to running a 24/7 YouTube live stream covers the broader operational setup rather than the codec table alone.
Input settings are not viewer playback formats
The encoder sends one incoming stream mode to YouTube. YouTube then transcodes that input into multiple output formats for viewers. A viewer’s available playback choice can depend on YouTube’s processing and the device or network being used. Therefore, do not describe a 2160p60 input as a promise that every viewer will see 2160p60, or claim that all viewers receive the encoder’s exact resolution.
This distinction changes what you should optimise. The encoder settings determine what you submit; the viewer experience depends on the formats YouTube makes available and the conditions on the viewer’s side. If a viewer reports that a lower resolution is selected, that does not on its own prove the incoming stream was configured at that lower resolution. Check the live input and processing information in YouTube Studio, then consider the viewer’s device and connection separately.
The same distinction applies to frame rate. Sending 60 fps does not mean every viewer’s playback will be at 60 fps. It means your encoder is sending the selected input mode, if the configuration and stream health indicate that it is. A 30 fps source should not be treated as improved merely by selecting a 60 fps output; it may add encoding demand without adding source motion.
For a 24/7 channel, a sensible target is a mode that fits the source and can be sent consistently, rather than the maximum listed resolution for its own sake. A bhajan stream built from a static image and audio may have different needs from a local news loop with moving footage and text. Keep the source quality, encoding load, codec, bitrate and available upload capacity in view together. The practical question is not only “Can this encoder make 4K?” but “Can this complete setup send the chosen mode reliably, and is that mode useful for this programme?”
If an always-on prerecorded channel is interrupted because the computer or file playback process needs constant attention, the resolution table will not solve that operational problem. StreamNeo turns an uploaded video into a YouTube live stream that can continue with your computer switched off, which addresses that specific burden of keeping a local machine running. It is YouTube-only, and you should still choose an appropriate input mode and verify the live stream in YouTube’s tools.
A practical configuration and test sequence
Start by identifying the source: its native resolution, whether it contains fast motion, and whether the material is HDR. Avoid upscaling a small source solely to select 2160p. Upscaling changes the output dimensions but does not create detail that was not present in the original, and it can increase the demand on the encoding and upload path.
Next, confirm what the encoder can actually send. Check codec, resolution and frame rate in its output settings or status panel. If a device only offers H.264 for the workflow you are using, use H.264’s bitrate recommendation rather than assuming it sends H.265 because that codec appears in YouTube’s table. If you are using OBS or another software encoder, consult the software’s own documentation for where those controls are exposed; YouTube’s table does not prescribe a particular encoder’s menu layout.
Then use the matching table row, run a test with the real content, and inspect YouTube’s stream health messages. Repeat under realistic network use if the first test was done in unusually quiet conditions. Do not infer a sustainable live configuration from a single upload-speed reading. YouTube specifically recommends checking connection capacity and testing before going live; the test should reveal whether your actual combination is workable.
For a local news loop, test transitions and scrolling text; for a study or lofi station, test long sections of the real audio and image; for a devotional stream, include the material that will play across a normal programme period. The purpose is to expose issues that a short blank-screen test cannot show. If a setting fails, reduce demands or correct the encoder configuration and retest rather than treating the published minimum as an assurance of stability.
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 is the highest frame rate YouTube lists for an encoder stream?
YouTube’s published live encoder guidance lists frame rates up to 60 fps. Its bitrate table includes 30 and 60 fps rows for several resolutions, up to 2160p. The guidance reviewed here does not list a 120 fps encoder mode.
What bitrate should I use for 2160p60?
YouTube recommends 35 Mbps for AV1 or H.265 and 50 Mbps for H.264 at 2160p60. Use the figure that matches the codec your encoder actually sends, and treat it as a recommendation for the incoming stream, not a guarantee of stable transmission or viewer playback quality.
Should I set resolution manually in YouTube Studio?
YouTube recommends automatic detection for most streams. Manual settings are available with a custom stream key when you have a reason to control the incoming resolution and frame rate; keep those selections aligned with the encoder output and test them before relying on them.
Does a 4K encoder input mean every viewer watches in 4K?
No. YouTube transcodes the incoming stream into multiple output formats, and viewer playback depends on what is available for that viewer’s device and network. The encoder’s resolution describes the input you send, not a promise about every viewer’s rendition.