What Is Video Bitrate? YouTube Quality & Export Guide

Video Bitrate

Video bitrate is the amount of encoded video data used over time. It is commonly measured in megabits per second, written as Mbps.

A video encoded at 10 Mbps uses an average of about 10 million bits of video data for each second of playback. Higher bitrate gives the encoder more data to describe detail and motion, but it also increases file size and bandwidth requirements.

Bitrate is only one part of video quality. The result also depends on the codec, resolution, frame rate, bit depth, color sampling, source footage, noise, motion complexity, and encoder quality.

What bitrate measures

Bitrate describes a rate of data, not a count of pixels and not a direct quality score.

Common units include:

• bps: Bits per second.
• kbps or Kbps: Thousands of bits per second.
• Mbps: Millions of bits per second.
• Gbps: Billions of bits per second, more common for high-bandwidth production signals than compressed uploads.

Video bitrate normally refers to the video track only. A file can also contain audio, captions, metadata, and container overhead, so its total bitrate may be slightly higher.

Bitrate and approximate file size

A simple estimate is:

File size in megabytes ≈ bitrate in Mbps × duration in seconds ÷ 8

This uses decimal megabytes and does not include audio or container overhead.

Video bitrate	1 minute	10 minutes	1 hour
5 Mbps	About 37.5 MB	About 375 MB	About 2.25 GB
10 Mbps	About 75 MB	About 750 MB	About 4.5 GB
20 Mbps	About 150 MB	About 1.5 GB	About 9 GB
50 Mbps	About 375 MB	About 3.75 GB	About 22.5 GB
100 Mbps	About 750 MB	About 7.5 GB	About 45 GB

Actual files differ because variable bitrate changes over time and audio, metadata, and the container add data.

Does higher bitrate always mean better quality?

Higher bitrate can reduce compression damage when the codec and other settings remain the same, but it does not guarantee a better image.

A higher bitrate cannot restore:

• Detail that was never captured.
• Missed focus.
• Motion blur from the original shutter speed.
• Clipped highlights or crushed shadows.
• Heavy noise reduction or sharpening artifacts.
• Color information removed earlier in the workflow.
• Quality lost through repeated low-quality exports.

At some point, increasing bitrate produces little visible improvement because the codec already has enough data for the content. The extra bits mainly increase storage, export time, upload time, and processing time.

Why codec efficiency matters

Two videos at the same bitrate can look different if they use different compression systems or encoder implementations. A more efficient codec may preserve similar visual quality with fewer bits, although it may require more processing power or have less editing and device compatibility.

Bitrate comparisons are most meaningful when the following are also similar:

• Codec and profile.
• Resolution.
• Frame rate.
• Bit depth.
• Chroma subsampling.
• Keyframe structure.
• Encoding preset and quality mode.
• Source content.

A 12 Mbps H.264 file and a 12 Mbps AV1 file are not equivalent simply because the number matches.

Resolution and bitrate

Higher resolution usually needs more data because each frame contains more pixels. A 4K frame has four times as many pixels as a 1920×1080 frame, although compression efficiency and image complexity mean it does not always require exactly four times the bitrate.

Insufficient bitrate at a high resolution can create a file that has more pixels but less clean detail than a well-encoded lower-resolution version.

Creators should match bitrate to the real resolution and aspect ratio rather than upscaling only to display a larger number.

Frame rate and bitrate

Higher frame rate means the encoder must describe more frames each second. A 60 fps video often needs more bitrate than a 30 fps video at the same resolution and codec, especially when it contains fast movement.

YouTube's current upload guidance therefore provides separate recommendations for standard frame rates—24, 25, and 30 fps—and high frame rates—48, 50, and 60 fps.

Content complexity

Some images compress more easily than others.

Lower-demand content includes:

• A presenter against a clean, static background.
• Slides with limited movement.
• Large flat shapes.
• Locked-off shots with low sensor noise.

Higher-demand content includes:

• Grass, leaves, hair, glitter, smoke, water, or confetti.
• Fast games or sports.
• Handheld camera movement.
• Film grain or high-ISO noise.
• Rapid lighting changes.
• Detailed screen captures with scrolling text.

Noise and grain are difficult to predict and compress because they change across frames. A noisy image may require more bitrate than a clean image at the same resolution.

Constant bitrate vs. variable bitrate

Mode	How it allocates data	Main advantage	Main limitation
CBR	Targets a relatively constant output rate	Predictable bandwidth for live delivery	Can waste bits on simple scenes or starve complex scenes
VBR	Uses more data for complex sections and less for simple sections	Better file efficiency for uploads and stored video	File size and peak rate are less predictable
Average bitrate	Varies while targeting a chosen average	Balances quality and expected size	May require analysis or multiple passes for accuracy
Constant quality	Targets a visual-quality level and lets bitrate vary	Efficient archival or local export	Final size can vary substantially

For normal YouTube uploads, the official recommended H.264 settings specify variable bitrate and say that no bitrate limit is required, while providing reference bitrates. For YouTube Live over RTMP/RTMPS, the current encoder guidance specifies CBR because real-time ingest has different bandwidth needs.

One-pass vs. two-pass VBR

A one-pass encoder makes decisions while moving through the video. It is faster and may be appropriate for quick exports.

A two-pass encoder first analyzes the full video and then allocates data during a second pass. It can be more accurate when the creator needs a target average bitrate or predictable file size, although modern constant-quality and hardware encoders may use different strategies.

Two-pass encoding does not automatically beat every one-pass export. Codec implementation, preset, hardware acceleration, and target constraints matter.

YouTube recommended upload bitrates

YouTube currently publishes the following reference ranges for SDR uploads:

Resolution	24, 25, or 30 fps	48, 50, or 60 fps
720p	5 Mbps	7.5 Mbps
1080p	8 Mbps	12 Mbps
1440p	16 Mbps	24 Mbps
2160p / 4K	35–45 Mbps	53–68 Mbps
4320p / 8K	80–160 Mbps	120–240 Mbps

YouTube gives higher recommendations for HDR. For example, its current table lists 10 Mbps for standard-frame-rate 1080p HDR and 15 Mbps for high-frame-rate 1080p HDR.

These values are recommendations, not hard upload caps. YouTube also advises uploading material close to the original high-quality source and always re-encodes uploaded videos for playback.

Upload bitrate vs. YouTube playback bitrate

The bitrate of a creator's exported file is not the bitrate every viewer receives.

The general workflow is:

1. The creator encodes an upload file.
2. YouTube processes and re-encodes that file.
3. YouTube creates multiple playback versions for different resolutions, devices, codecs, and network conditions.
4. The player selects an appropriate version and can switch during playback.

Uploading a clean, high-quality source gives the platform better material to encode. Uploading an extremely large file cannot force YouTube to deliver that same source bitrate to viewers.

Upload bitrate vs. stream bitrate

Upload video bitrate describes a completed file sent to YouTube for processing. Stream bitrate describes a real-time feed sent by a live encoder.

Consideration	Uploaded video	Live stream
Encoding time	Can use slower, quality-focused processing	Must encode in real time
Bitrate mode	VBR is commonly recommended	CBR is commonly required for RTMP ingest
Network	Affects upload duration	Must sustain the bitrate continuously
Recovery	File can be re-exported and uploaded again	Lost data can create live artifacts or dropped frames
Platform processing	Happens after upload	Happens while the stream is live

A creator should not copy an upload bitrate table into live software without checking the platform's live-ingest guidance.

Common low-bitrate artifacts

When an encoder does not have enough data for the content, viewers may see:

• Blocky or smeared motion.
• Loss of texture in hair, grass, water, or games.
• Banding in gradients, skies, and shadows.
• Mosquito noise around text or high-contrast edges.
• Muddy dark areas.
• Pulsing detail as keyframes and predictions change.
• Color breakup or posterization.
• Softness during camera movement.

Some artifacts come from bit depth, color sampling, scaling, or source noise rather than bitrate alone. Increasing bitrate is one possible fix, not a diagnosis by itself.

Bitrate and repeated exports

Lossy compression removes or approximates information. Re-encoding an already compressed file can compound artifacts, especially when each generation uses a low bitrate.

A stronger workflow is:

• Keep the highest-quality original recordings.
• Edit in a suitable project or intermediate format.
• Avoid downloading a platform copy as the next editing master.
• Export once from the best available timeline or master.
• Use a bitrate appropriate to the chosen codec and delivery target.

A high-bitrate final export cannot fully reverse damage from an earlier low-bitrate recording or render.

Choosing a practical export bitrate

Consider:

1. Destination: YouTube upload, live ingest, archive, client delivery, or social platform.
2. Resolution: Export the actual intended frame dimensions.
3. Frame rate: Preserve the recorded rate unless a deliberate conversion is needed.
4. Codec: Use a supported codec with appropriate efficiency and compatibility.
5. Content: Add headroom for high motion, fine detail, noise, and grain.
6. Color: HDR, 10-bit, or high-fidelity masters may need different guidance.
7. Upload speed and storage: Avoid unnecessary size without starving the image.
8. Processing: Test a representative segment instead of judging only a still frame.

For a straightforward SDR YouTube upload using H.264, YouTube's current table is a useful starting point. A visually complex project may justify more data, while a quality-based encoder may not map neatly to one average target.

Common video bitrate mistakes

• Treating bitrate as the same thing as resolution.
• Comparing bitrates without comparing codecs.
• Using one universal setting for 720p, 1080p, and 4K.
• Ignoring the extra demand of high frame rates.
• Exporting noisy footage at a low bitrate and blaming only YouTube.
• Assuming YouTube's recommended figures are strict maximums.
• Uploading at the platform's playback bitrate rather than preserving source quality.
• Using VBR upload advice for a CBR live stream.
• Increasing bitrate after detail was already lost in recording.
• Confusing megabits with megabytes; eight bits equal one byte.
• Forgetting that audio and container overhead add to total file size.
• Judging quality before YouTube finishes HD or 4K processing.

Frequently asked questions

What bitrate should I use for 1080p YouTube video?

YouTube currently recommends 8 Mbps for SDR 1080p at 24, 25, or 30 fps and 12 Mbps at 48, 50, or 60 fps. These are reference recommendations, not strict limits, and codec and content complexity still matter.

Is 20 Mbps good for 1080p?

It can be more than sufficient for many H.264 1080p uploads, but the result depends on frame rate, motion, noise, encoder quality, and source footage. A larger number does not guarantee that an earlier quality problem is fixed.

Does YouTube reduce video bitrate?

YouTube always re-encodes uploads and creates its own playback versions. The viewer normally receives one of those processed streams rather than the creator's original export file.

Is VBR or CBR better for YouTube?

For normal uploads, YouTube's recommended H.264 settings specify variable bitrate. For RTMP/RTMPS live streams, its live encoder guidance specifies CBR. The correct mode depends on whether the video is a completed file or a real-time feed.