YouTube Live resolution and frame rate should match what your source, encoder and upload connection can sustain continuously. For most always-on channels, a stable 720p or 1080p stream is more useful than a higher setting that drops frames overnight.
This guide covers the settings YouTube receives through RTMP or RTMPS. YouTube then creates viewer-side versions of the live stream, so your ingest resolution is not a promise that every viewer will receive that same resolution.
Start with live ingest, not upload encoding
A live stream and an uploaded video follow different paths. With a live stream, your encoder sends a continuous sequence of video and audio data to YouTube while the broadcast is running. You choose the output resolution, frame rate, codec and bitrate in the encoder, and YouTube receives that feed through RTMP or RTMPS.
An uploaded video is prepared as a finished file before YouTube processes it. Its recommended encoding settings are therefore not a direct answer to the question of what bitrate to use for a live feed. Do not copy an upload bitrate table into OBS, a hardware encoder or another live encoder and assume that it is suitable for RTMP ingest.
YouTube Help lists RTMP and RTMPS as supported protocols, and recommends RTMPS where the encoder supports it. RTMPS is the secure extension of RTMP. You can find the current YouTube live encoder settings and review the exact options shown for your account and encoder.
YouTube’s default approach is to detect the resolution and frame rate being sent by the encoder automatically. Manual selection is available when you use a custom stream key and configure the manual settings in Live Control Room. Automatic detection is a sensible starting point because it reduces the number of values you must keep aligned.
Manual control is useful when your source changes in an unwanted way, when you need a fixed output for a scheduled programme, or when you are diagnosing a stream that is being sent at the wrong size. It is not a reason to select the highest available setting. The setting still has to be maintained by the source and connection for the whole broadcast.
Choose a resolution suited to the source
Resolution describes the number of pixels in each video frame. A 1920 by 1080 source contains more visual detail than a 1280 by 720 source, but sending a 1080p signal does not create detail that was absent from the original material.
Start with the actual source rather than the largest value in your encoder menu. A devotional loop made from 720p artwork, a fixed camera, and simple text may gain little from being scaled to 1080p. A local news loop with maps, captions and small text may benefit from 1080p if the original graphics are designed at that size. A 4K camera source can justify a higher ingest resolution when the encoder and upload connection can maintain it.
Scaling a smaller source up can also make the feed less efficient. You send more pixels, consume more upload capacity and place more work on the encoder, while the viewer may not see additional useful detail. For a static or gently moving channel, reliability usually matters more than an enlarged canvas.
The shape of the source matters as well. If your programme is vertical or square, decide whether the complete composition needs to be preserved or whether it should be placed inside a horizontal canvas. YouTube will still process the received frame, but stretching the source can make people, letters and devotional artwork look wrong. The guide to vertical and square video on a 24/7 stream covers the layout decisions separately.
A practical resolution choice can look like this:
| Source and programme | Sensible starting point | Main reason to change it |
|---|---|---|
| Artwork, slides or a simple music loop prepared at 720p | 720p | Use 1080p only if the source has more detail and the connection can sustain it |
| Text-heavy news, teaching or business content prepared at 1080p | 1080p | Reduce the setting if the encoder or upload feed is unstable |
| Fast camera footage or detailed production prepared at 1440p | 1440p | Use it only when the connection and encoder remain reliable over a long test |
| Genuine 4K source with a reason to preserve fine detail | 2160p | Choose a lower setting if latency or continuous stability matters more |
These are workflow choices, not universal requirements. YouTube does not require every channel to ingest at one resolution. If the original file is a prerecorded loop, inspect its native dimensions before deciding what the encoder should send. You can also read how to start a sleep music live stream on YouTube from India for a programme-specific example of balancing simple visuals, audio and long running time.
Choose a frame rate suited to the content
Frame rate is the number of video frames sent each second. YouTube’s listed live ingest limit is up to 60 frames per second, but that does not make 60 fps the right choice for every channel.
For a still image, prayer text, a slow ambience scene or a playlist with restrained movement, 30 fps is usually an easier target. There is less data to send than at 60 fps, and the audience is unlikely to gain much from doubling the number of nearly identical frames. It also gives the encoder and connection more room to remain steady.
Higher frame rates are more useful when motion is a central part of the programme. Sports, demonstrations, camera movement, dance, fast scrolling text and some gameplay can look smoother at 60 fps. The gain is visible only when the source itself contains that motion and the whole chain can maintain the selected frame rate.
Do not choose 60 fps merely because the original camera can record it. A 60 fps source can be converted to 30 fps when the programme does not need the extra motion detail. Conversely, converting a 30 fps source to 60 fps does not recreate the missing motion. It usually adds repeated or interpolated frames while increasing the live output requirement.
Frame rate and resolution should be considered together. A 1080p60 feed has a higher recommended bitrate than a 1080p30 feed in YouTube’s live ingest guidance. If a 30 fps stream is visually adequate, using it can simplify the continuous setup. If motion smoothness is important, select 60 fps and apply the corresponding bitrate rather than keeping the 30 fps bitrate.
Keep the frame rate consistent from the source through the encoder where possible. A programme that changes between frame rates can make diagnosis harder, particularly when a long prerecorded playlist contains files made with different settings. Normalise the material before streaming if your workflow allows it, then test the final output rather than testing only one clip.
Match bitrate to resolution and frame rate
Bitrate is the amount of video data sent over time. It is not a quality score by itself. A higher bitrate can preserve more detail, but it also requires more upload capacity and can expose weaknesses in the encoder or network.
YouTube’s current live encoder guidance gives recommended ingest bitrates by resolution, frame rate and codec. The figures below are for live ingest, not file uploads. They are recommended values, not a claim that every connection must use the same setting. The table was retrieved from YouTube Help on 3 October 2026.
| Ingest resolution and frame rate | AV1 or H.265 recommended | H.264 recommended |
|---|---|---|
| 2160p at 60 fps | 35 Mbps | 50 Mbps |
| 2160p at 30 fps | 30 Mbps | 42 Mbps |
| 1440p at 60 fps | 24 Mbps | 34 Mbps |
| 1440p at 30 fps | 15 Mbps | 21 Mbps |
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
| 1080p at 30 fps | 10 Mbps | 14 Mbps |
| 720p at 60 fps | 6 Mbps | 8 Mbps |
| 720p at 30 fps | 6 Mbps | 8 Mbps |
| 480p at 30 fps | 3 Mbps | 4 Mbps |
| 360p at 30 fps | 3 Mbps | 4 Mbps |
The codec column matters. Do not select the H.264 figure for an AV1 or H.265 stream, or treat the AV1/H.265 column as a general target for every encoder. Confirm which codec is actually being sent. H.264 remains a practical choice when compatibility is more important than codec efficiency, while a supported H.265 or AV1 workflow may use a different recommended bitrate.
YouTube lists CBR, or constant bitrate, as the encoder mode. CBR keeps the outgoing rate more predictable than a mode that varies widely with scene complexity. YouTube also recommends a keyframe interval of two seconds and says not to exceed four seconds. Apply those values in the encoder if it exposes them.
The frame rate, resolution, codec and bitrate are a single group of decisions. For example, a 1080p30 H.264 feed corresponds to YouTube’s 14 Mbps recommended value, while a 1080p60 H.264 feed corresponds to 17 Mbps. Moving from 1080p30 to 1080p60 without changing the bitrate can leave less data available for each frame.
YouTube’s advanced guidance also refers to progressive scan, square pixels, Rec. 709 for SDR and 8-bit SDR, along with other codec-specific settings. These are documented recommendations rather than a checklist that every simple channel must recreate manually. For HDR, YouTube lists H.265 and 10-bit settings and does not list AV1 as supported for HDR. Treat HDR as a separate workflow and check the current official documentation before building around it.
Check upload capacity and test the feed
Your internet plan’s advertised download speed is not the number that matters here. The encoder must send a sustained upload stream, and the available upstream capacity can change with Wi-Fi conditions, other devices, congestion and the behaviour of the connection provider.
Run an upload speed test as YouTube recommends, then leave practical headroom instead of treating the test’s peak result as a guaranteed continuous rate. Headroom is operational advice rather than a numeric YouTube requirement. If your selected video bitrate already consumes nearly all of the measured upload capacity, a brief reduction in available bandwidth can produce dropped frames or a disconnected feed.
Audio also uses part of the outgoing stream. Keep the audio setting included in your planning, along with any other traffic sharing the connection. A household connection used for a live channel should not be tested only when every other device is idle if those devices will be active during the broadcast.
Test with representative content. A still image may confirm that the connection can send data, but it will not expose problems caused by camera movement, scrolling captions, scene changes or busy graphics. Include the real audio as well. YouTube Help says, “Make sure to test before you start your live stream.”
During the test, check the encoder’s dropped-frame and connection messages, then inspect stream health in Live Control Room. YouTube also advises monitoring stream health and reviewing messages during the event. A test that runs briefly without an obvious error is useful, but a longer test with the same source and settings gives you more confidence in the workflow.
For a continuous channel, decide what happens if the connection fails. If the encoder is running locally, a power cut, operating-system update or household network interruption can stop the broadcast even when the settings are correct. An unattended cloud workflow can remove the need to leave your computer running; StreamNeo is designed for the specific case where you upload the video once, provide the YouTube stream key, and need the broadcast to continue with automatic monitoring and restart rather than maintaining a local machine overnight.
Do not treat automatic restart as a substitute for checking YouTube stream health, permissions, content rights or the stream key. It only addresses a particular operational failure. You still need to confirm that the outgoing resolution, frame rate, audio and codec are the values you intended.
Use RTMPS when your encoder supports it
RTMP is the protocol family commonly used to send an encoder feed to YouTube. RTMPS adds transport security. YouTube recommends RTMPS, but the encoder must support it and must be configured with the correct secure ingest URL.
You can follow YouTube’s instructions for revealing the RTMPS URL in Live Control Room. The exact fields vary between software and hardware encoders, but the workflow remains the same: choose the protocol, enter the server URL, enter the stream key, and then apply the video and audio settings.
If an older encoder supports only RTMP, check its documentation and YouTube’s current requirements before relying on it for a long broadcast. Do not assume that changing the URL alone will make an encoder compatible with RTMPS. The encoder needs to support the protocol and its connection method.
Keep the stream key private. If it is exposed, someone else may be able to send a feed to your live event. Regenerate it through YouTube if you believe it has been shared accidentally, then update the encoder before the next test.
Understand what viewers receive
The resolution you send is the input to YouTube’s live processing, not a fixed promise about the viewer’s playback menu. YouTube automatically transcodes the received stream into multiple output formats. A viewer’s available quality can depend on the device, connection, screen, browser and YouTube’s delivery decisions.
This is why ingesting at 2160p does not mean every viewer watches at 2160p. Someone on a small mobile screen or a constrained connection may receive a lower-quality version. Conversely, sending a clean 1080p feed gives YouTube a useful source from which to create other viewer options, but it does not force every viewer to select or receive 1080p.
The same distinction applies to frame rate. Sending 60 fps does not guarantee that every viewer receives 60 fps. The source can still benefit viewers whose devices and connections can use the additional motion detail, but YouTube’s processing and the viewer’s playback conditions remain part of the final result.
4K and 2160p deserve a further caution. YouTube says that 4K/2160 streams do not have the low-latency improvement option and are optimised for quality at normal latency. If your channel depends on quick interaction, a lower ingest resolution may suit the programme better even when the source can technically support 4K.
For a devotional, music or ambience channel, normal latency may be acceptable because the programme is not built around rapid replies. For a live class, product demonstration or local news discussion, the delay can affect how you communicate with viewers. Choose resolution and frame rate alongside the purpose of the channel, not as an isolated quality setting.
A repeatable setup for a continuous channel
Use this order when preparing a new stream:
- Inspect the source files or live camera output. Note the native resolution, frame rate, aspect ratio and whether the content is mostly still or contains frequent motion.
- Choose the lowest resolution that preserves the detail your viewers need. Do not upscale a low-detail source just to make the number larger.
- Choose 30 fps for content that does not need smooth fast motion, or 60 fps when the source and programme genuinely benefit from it. YouTube’s listed maximum is 60 fps.
- Confirm the codec being sent, then use the corresponding YouTube recommended bitrate for the selected resolution and frame rate.
- Set CBR and a two-second keyframe interval. Keep the keyframe interval at or below four seconds.
- Prefer RTMPS when the encoder supports it. Add the stream key carefully and keep it private.
- Run an upload speed test and test the actual programme, including representative audio, motion and text.
- Watch stream health during the test and early in the live event. If the feed is unstable, reduce the resolution or frame rate rather than repeatedly increasing bitrate.
If you are moving from a local OBS setup to an always-on arrangement, preserve this checklist even when the computer is no longer running the stream. A different operating method does not change the need to match the source, bitrate and connection. For channels that repeatedly stop after long periods, the separate guide to keeping a 24/7 devotional YouTube stream running past 12 hours may help you examine the wider workflow.
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 resolution should I stream at on YouTube?
Choose the resolution that matches the source and that your encoder and upload connection can sustain. For many continuous channels, 720p or 1080p is a practical starting point. A higher ingest resolution does not create missing detail and does not guarantee that every viewer will receive that resolution.
What frame rate does YouTube Live support?
YouTube’s live encoder guidance lists up to 60 fps. Use 30 fps for mostly static content when it is visually sufficient, and choose 60 fps when the source contains motion that benefits from smoother movement. Test the complete programme rather than judging the setting from a still image.
What bitrate do I need for 1080p60 streaming?
According to YouTube Help’s live ingest table retrieved on 3 October 2026, the recommended bitrate for 1080p60 is 12 Mbps with AV1 or H.265 and 17 Mbps with H.264. Confirm the codec actually being sent, use CBR, and make sure the upload connection can sustain the chosen rate with practical headroom.
Should I use RTMP or RTMPS for YouTube Live?
YouTube recommends RTMPS when the encoder supports it, because it is the secure extension of RTMP. Check the current YouTube guidance for encoder settings and protocols, then confirm that your encoder supports RTMPS before changing the server URL.