Best Bitrate for YouTube: How to Configure Your Encoder Settings

According to Streams Charts, tens of thousands of channels are live on YouTube at any given second. If you’re one of them and you feed YouTube through an encoder, bitrate is the setting you’ll second-guess most.

Video bitrate is the amount of data your encoder sends for each second of video which is measured in kilobits per second (kbps) or megabits per second (Mbps). 

A higher bitrate preserves more detail, while a lower bitrate uses less bandwidth.

Higher bitrates = better video quality and larger file sizes.

Lower bitrates = smaller files but compromise on visual fidelity.

That number changes with every resolution and every frame rate, so a setting that looks clean at 1080p30 falls apart at 4K60. Your upload speed and encoder configuration decide how much of the recommendation you can actually hold. If your bitrate is too low, fast motion looks blurry or blocky. If it’s too high, your connection may struggle to keep up and start dropping frames.

For H.264, YouTube recommends 12 Mbps for 1080p at 60fps, 6 Mbps for 720p at 60fps, and 35 Mbps for 4K at 60fps. YouTube then transcodes your stream into multiple playback renditions, though that process can’t restore detail your encoder already lost.

Let’s explore the best bitrate for YouTube and how to configure it in your encoder. You’ll learn how Castr keeps playback stable when your viewers have different internet speeds.

What Bitrate Does YouTube Recommend for Live Streaming?

YouTube’s recommended H.264 live bitrate runs from 4 Mbps at 720p30 up to 35 Mbps at 4K60. The platform publishes two sets of numbers: a single recommended value for H.264, and a minimum-to-maximum window for the newer AV1 and H.265 codecs.

Source: YouTube Help, Choose live encoder settings, bitrates, and resolutions.

AV1 and H.265 reach the same picture quality at a lower bitrate, which is why their minimums sit well below the H.264 recommendation. The trade-off is decoder support, since fewer viewer devices can play those codecs back.

One exception applies at the top of the table. YouTube disables the low-latency option for 4K, so every 2160p stream runs at normal latency and gets optimized for quality instead.

Best Bitrate for 4K / 2160p at 60fps

4K60 needs 35 Mbps in H.264. Plan for about 53 Mbps of sustained upload, because your connection needs headroom above the video bitrate for audio, protocol overhead, and short dips in throughput.

Switching the encoder to H.265 or AV1 brings the same stream into a 10–40 Mbps window. That’s the largest bandwidth saving available to you, though older hardware decoders may not play it back.

Use this combination for high-motion 4K: concerts, sports, and anything with a moving camera.

Best Bitrate for 4K / 2160p at 30fps

4K30 needs 30 Mbps in H.264, on about 45 Mbps of sustained upload. Halving the frame rate saves only 5 Mbps at this resolution, because the pixel count dominates the data requirement at 4K.

Fixed-camera UHD fits here: worship services, lecture halls, venue cameras, and product demos on a tripod.

Best Bitrate for 1440p at 60fps

1440p60 calls for 24 Mbps, on roughly 36 Mbps of upload. This combination sits between 1080p and 4K, which suits gaming setups where 1080p looks soft on a large monitor and 4K exceeds most home upload connections.

YouTube serves a native 1440p rendition to viewers, so the extra pixels reach your audience instead of being downscaled on arrival.

Best Bitrate for 1440p at 30fps

1440p30 drops to 15 Mbps, on about 23 Mbps of upload. That’s the largest single reduction in YouTube’s recommendations: 9 Mbps saved by halving the frame rate at the same resolution.

Choose this combination when your content is detailed but slow, such as a design walkthrough, a code review, or a static wide shot of a stage.

Best Bitrate for 1080p at 60fps

1080p60 needs 12 Mbps, on roughly 18 Mbps of upload. Most live streams use this combination, and most encoder defaults sit well below the recommendation.

One detail is worth noting. YouTube’s H.264 recommendation of 12 Mbps sits above the 10 Mbps ceiling it sets for AV1 and H.265, because those codecs need less data to reach the same result.

Best Bitrate for 1080p at 30fps

1080p30 needs 10 Mbps, on about 15 Mbps of upload. Low-motion content belongs here: interviews, webinars, panel discussions, and webcam broadcasts where the frame changes little between cuts.

Dropping from 60fps to 30fps saves 2 Mbps at 1080p. If your upload can’t hold 18 Mbps reliably, reduce the frame rate before you reduce the resolution.

Best Bitrate for 720p at 60fps

720p60 runs at 6 Mbps, on roughly 9 Mbps of upload. This combination suits motion-heavy content on a limited upload: bonded cellular, mobile encoders, and venues with shared Wi-Fi.

A stable 720p60 stream looks better than an under-provisioned 1080p60 stream, because your encoder spends its full bitrate on fewer pixels.

Best Bitrate for 240p–720p at 30fps

4 Mbps covers everything from 240p up to 720p at 30fps. YouTube collapses that entire range into one row, so you don’t need a separate number for 360p or 480p.

Audio-led broadcasts and backup feeds fit here. YouTube already generates the lower renditions from a higher ingest, so streaming natively at 360p only makes sense when your upload leaves you no choice.

How Does Resolution and Frame Rate Affect YouTube Bitrate?

Resolution and frame rate together decide how many pixels your encoder compresses each second, and bitrate is the budget it gets to do the job. A 4K60 feed asks the encoder to handle 18 times the pixels per second of a 720p30 feed, yet YouTube only asks for about 9 times the bitrate.

Compression closes that gap. Your encoder stores one full frame and then describes the changes, so predictable images cost far less than a raw pixel count suggests.

60fps vs. 30fps Bitrate

Doubling your frame rate raises the bitrate requirement by 17% to 60%, not 100%. YouTube’s recommendations show the spread clearly:

• 4K: 30 Mbps at 30fps, 35 Mbps at 60fps (+17%)
• 1080p: 10 Mbps at 30fps, 12 Mbps at 60fps (+20%)
• 720p: 4 Mbps at 30fps, 6 Mbps at 60fps (+50%)
• 1440p: 15 Mbps at 30fps, 24 Mbps at 60fps (+60%)

Inter-frame prediction explains the difference. At 60fps, consecutive frames sit half as far apart in time, so each one differs less from the one before it, and the predicted frames between keyframes carry smaller change data.

Motion determines where you land inside that range. A static lecture at 60fps costs almost nothing extra, while a hockey game at 60fps sits at the top of the recommendation.

Resolution and Bitrate Requirements

Bitrate scales with pixel count, but slower than the pixel count itself. Here’s what each resolution asks your encoder to handle per frame:

• 720p (1280×720): 921,600 pixels
• 1080p (1920×1080): 2,073,600 pixels
• 1440p (2560×1440): 3,686,400 pixels
• 2160p (3840×2160): 8,294,400 pixels

4K carries 4 times the pixels of 1080p, yet YouTube recommends only 3 times the bitrate at 30fps. Larger images contain more neighboring pixels that look alike, and spatial compression uses that redundancy.

The practical rule runs the other way. When your upload can’t hold the recommended number for a resolution, step down to the next resolution instead of running the current one under-provisioned, because an underfed encoder produces macroblocking and YouTube’s transcode carries those artifacts into every rendition it creates.

What Are the Best YouTube Encoder Settings for Live Streaming?

Your bitrate only works when the rest of your encoder configuration matches YouTube’s ingest specification. The platform publishes these requirements:

• Protocol: RTMP or RTMPS
• Video codec: H.264, H.265 (HEVC), or AV1
• Frame rate: up to 60fps
• Keyframe interval: 2 seconds recommended, 4 seconds maximum
• Audio codec: AAC or MP3
• Bitrate encoding: CBR

RTMPS is worth the switch from plain RTMP. It’s the same protocol secured with TLS, so your stream key and video stay encrypted all the way into Google’s servers.

Bitrate Mode

Set your encoder to CBR, or constant bitrate, for every YouTube stream. CBR holds the data rate steady regardless of what’s on screen, which is what a live ingest expects.

VBR does the opposite. It spends more data on complex scenes and less on simple ones, so a sudden camera pan can push your output well above target and exceed the upload capacity you planned for. Those spikes appear as dropped frames on your end and buffering on the viewer’s.

CBR uses some bandwidth inefficiently on static scenes. In exchange, you get a predictable data rate.

Keyframe Interval

Set your keyframe interval to 2 seconds. YouTube accepts up to 4 seconds, but its ingest is tuned for 2.

A keyframe is a complete image, and the frames after it only describe what changed. YouTube segments its HLS output on keyframe boundaries, so a long interval produces long segments, and long segments delay how quickly a viewer’s player can start and switch quality.

Encoder Selection

Choose a hardware encoder if your streaming machine also runs the game, and x264 if it doesn’t. NVENC on NVIDIA cards, Quick Sync on Intel chips, and AMF on AMD cards all move encoding onto dedicated silicon, which leaves your CPU free.

x264 runs on the CPU and delivers more quality per bit at matched settings. That advantage matters most when you’re constrained to a low bitrate.

At YouTube’s recommended bitrates, the difference is small. 12 Mbps for 1080p60 gives any modern encoder enough room that hardware and software output look close to identical.

Video Codec

Encode in H.264 unless you have a specific reason not to. Every browser, phone, smart TV, and console decodes it, which makes it the safe default when you can’t predict your viewers’ devices.

H.265 and AV1 both cut your bandwidth requirement substantially, and both narrow the set of devices that can decode your ingest. HDR forces the choice: YouTube wants H.265 over RTMPS for HDR streams and doesn’t support AV1 for HDR at all. AV1 streams at 3840×2160 and above also need at least 2 tile columns configured.

H.264 Profile and Level

Set your H.264 profile to High. YouTube’s advanced specification asks for CABAC entropy coding and 2 B-frames, and Baseline profile supports neither, so Baseline costs you compression efficiency at the same bitrate.

Level is the other half of the setting, and it caps the resolution and frame rate the stream can carry. Level 4.2 covers 1080p at 60fps, while 4K needs 5.1 or 5.2.

Most encoders set the level automatically from your resolution and frame rate. The profile dropdown is the one to check by hand.

Audio Bitrate

Encode audio in AAC at 128 kbps for stereo, sampled at 44.1 kHz. That combination covers speech, music, and everything between for a live broadcast.

5.1 surround needs different values: 384 kbps at a 48 kHz sample rate, and AAC specifically, since YouTube only accepts surround over RTMP and RTMPS in that codec.

Add your audio bitrate to your video bitrate when you size your connection. A 1080p60 stream at 12 Mbps plus 128 kbps of audio needs 12.13 Mbps before overhead.

How Do You Set the Best YouTube Bitrate in OBS Studio?

Six settings in OBS Studio control everything above. The whole configuration takes about two minutes once you know where those settings live.

Open OBS Output Settings

Open Settings → Output and switch Output Mode from Simple to Advanced, then select the Streaming tab. Simple mode hides the keyframe interval and the H.264 profile, so you can’t meet YouTube’s specification from it.

Select the Streaming Encoder

Pick your encoder from the Encoder dropdown at the top of the Streaming tab. OBS lists what your hardware supports, typically software x264 alongside hardware Apple H.264.

The fields below the dropdown change with your choice, so set this first. Rate control and bitrate appear underneath.

Set the Video Bitrate

Set Rate Control to CBR, then enter your target in the Bitrate field. OBS asks for kbps, so multiply YouTube’s Mbps figure by 1,000: type 12000 for 1080p60, 6000 for 720p60, and 35000 for 4K60.

Check the number against your measured upload speed before you save. Run a speed test at the time of day you plan to broadcast, since shared connections slow down during peak hours.

Choose the Keyframe Interval

Set Keyframe Interval to 2. OBS defaults this field to 0, which lets the encoder decide, and encoders often choose intervals far longer than YouTube’s 4-second maximum.

Configure the Audio Bitrate

Open the Audio tab inside Output settings and set Track 1 to 6. OBS encodes in AAC by default, so the codec needs no change.

Confirm that Track 1 is the track your streaming output uses. OBS assigns tracks separately for streaming and recording.

Apply and Test the Settings

Click Apply, then run a test broadcast to an unlisted YouTube stream before the real one. Open View → Docks → Stats in OBS and watch two counters while it runs:

• Dropped frames (network) point to your connection, so lower the bitrate
• Skipped frames (encoding) point to your CPU or GPU, so use a faster preset or switch encoders

YouTube’s Live Control Room shows the same picture from the other side. Its stream health panel reports the bitrate YouTube actually receives, which catches instability your encoder never sees.

Further Reading: Connecting OBS To Castr and Recommended Settings

How Does Castr Handle Bitrate and Adaptive Streaming?

Your encoder sends one bitrate, and your audience never has one connection. A viewer on fiber and a viewer on a weak mobile signal receive the same feed, and the second one buffers throughout your broadcast.

Castr solves that split with adaptive bitrate streaming. It takes your single ingest and produces a ladder of renditions at Source, 1080p, 720p, 480p, 360p, and 240p, then lets each viewer’s player switch between them automatically as their available bandwidth changes.

Those renditions map directly to what your audience can pull. Playback needs about 7 Mbps for 1080p, 3 Mbps for 720p, 1 Mbps for 360p, and 0.5 Mbps for 240p, so a mobile viewer on a weak signal keeps watching at a lower rendition instead of buffering.

You can shape the ladder yourself. Castr gives you four controls over it:

• Toggle individual renditions on or off
• Set each rendition anywhere from 250 to 15,000 kbps
• Pick a custom output frame rate of 25, 30, 50, or 60fps
• Choose an audio bitrate between 64 and 512 kbps

Adaptive bitrate is available on Premium plans and above, with the customizable bitrate ladder on Ultra.

Castr’s Transcoder handles the cases where your source feed doesn’t match what a destination accepts. It re-encodes your stream in the cloud to H.264 at 250–15,000 kbps and 24 to 60fps, which matters when your camera outputs H.265 and a platform like X refuses it.

Multistreaming reuses the encoder configuration you just set. You point one encoder at Castr over RTMP, RTMPS, SRT, or WHIP, and Castr relays that single input out to YouTube alongside Facebook, Twitch, LinkedIn, TikTok, and custom RTMP endpoints simultaneously. Starter includes 6 destinations and Ultra includes 30.

The YouTube destination connects through OAuth and carries the settings you’d otherwise fill in inside the Live Control Room: your event, stream title, description, and privacy status. Delivery runs across Akamai, Fastly, and CloudFront, so your encoder produces one output no matter how many platforms you distribute to.

Our Take

Match YouTube’s recommended bitrate to the resolution and frame rate your upload can sustain, then leave the encoder settings alone and go live. Castr handles the rest of the chain: adaptive renditions for viewers on slower connections, cloud transcoding for mismatched codecs, and simultaneous delivery to YouTube and 30 other destinations from a single ingest. 

Start streaming with Castr and go live in minutes.