The Complete Guide to Bitrate: The First Dial of Video Quality

The same 5 Mbps is generous for a locked-off lecture but falls apart on a football match — the "right" bitrate for 1080p can differ by a factor of 5 to 10.

"What bitrate should this video use?" The question comes up every time you compress a video, convert a format, or configure a screen recorder. Video sites recommend 8 Mbps for 1080p; a movie from your collection is only 2 GB; yet a one-minute clip from your phone already weighs 200 MB. How do these numbers relate? And what do the "high quality / balanced / high compression" presets in compression tools actually adjust?

Every one of these questions points to the same parameter: bitrate. It is the master valve between file size and picture quality—the true "first dial" of video technology. This article explains it thoroughly.

What Bitrate Is: Bits Spent Per Second

The definition is refreshingly simple: the number of bits of video data consumed per second, commonly measured in kbps (kilobits per second) and Mbps (megabits per second, where 1 Mbps = 1000 kbps).

Bitrate directly determines file size. The conversion formula is worth memorizing:

File size (MB) ≈ total bitrate (Mbps) × duration (seconds) ÷ 8

(The ÷ 8 converts bits to bytes.)

Example: a 5-minute video at a total bitrate of 10 Mbps is roughly 10 × 300 ÷ 8 = 375 MB.

One easily overlooked detail: video files also carry audio. Total bitrate = video bitrate + audio bitrate. Audio typically runs at 96–320 kbps, a modest 5–15% of the total—but it matters in low-bitrate video: in an ultra-low 500 kbps video, audio can consume nearly half the budget.

Why There's No Single Answer to "How Much Bitrate Is Enough"

This is the most important lesson about bitrate: the same 5 Mbps produces dramatically different quality on different videos. The bitrate a codec needs depends on four variables:

1. Content complexity: fast-paced sports, rain, crowds—every frame is packed with fine, changing detail that takes a lot of data to describe. A locked-off lecture or a slide-deck recording barely changes between frames and needs very little. At the same resolution, the "sufficient" bitrate for these two can differ by 5–10×.
2. Resolution: more pixels, more information to describe. 1080p needs roughly 2× the bitrate of 720p (note: not the 2.25× pixel ratio, because encoding efficiency improves with size).
3. Frame rate: 60fps has twice the frames of 30fps, but because adjacent frames are more similar, the required bitrate rises only about 30–50%.
4. Codec: newer codecs are more efficient. At equal quality, H.265 saves about 40–50% bitrate over H.264, and AV1 saves roughly another 20–30% over H.265.

So anyone quoting a "recommended bitrate" without knowing the content is oversimplifying—recommendations can only be a starting point for "moderately complex content."

Rate-Control Modes: How to Spend the Budget

A codec needs a "budget allocation strategy" while compressing—that's what rate-control modes are. There are five mainstream ones:

CRF in Depth: The Quality-Centered Philosophy

CRF (Constant Rate Factor) is the signature mode of the x264/x265 encoders and deserves its own section. Its logic inverts traditional bitrate thinking: you specify "what quality I want," and the encoder decides how many bits to spend.

• CRF typically ranges from 0 to 51; lower values mean higher quality and larger files;
• x264 defaults to CRF 23, and the practical range is 18–28: 18 is nearly visually lossless, 23 is the balance point, and visible loss sets in around 28;
• Rule of thumb: every +6 CRF roughly halves the bitrate (e.g., CRF 23 → CRF 29 cuts the size about in half);
• Complex content automatically gets more bits, simple content fewer—quality stays uniform throughout the video.

Why recommend CRF for everyday compression? Because what you actually care about is "does it look good enough," not "is it exactly 8 Mbps." CRF lets the encoder manage the budget, eliminating misallocation where easy scenes waste bits and climactic moments turn to mush.

Two-Pass Encoding: The Best Answer When Size Is a Hard Target

When the scenario is reversed—"the file must be under 500 MB; maximize quality within that"—2-pass VBR is the tool: the first pass produces no file, only a complexity map of the whole video; the second pass spends the fixed budget with that map in hand. It's the way to squeeze the most out of a strict size limit, at the cost of roughly double the encoding time.

Recommended Bitrates by Resolution (H.264, Moderately Complex Content)

These reference values synthesize upload recommendations from major platforms and common industry practice (use roughly 60% for H.265/VP9, about 50% for AV1):

Three caveats when using this table:

• High-motion content (gameplay, sports): take the upper end or add 50%; static content (lectures, slides): 50–70% of the lower end is fine;
• These are upload/distribution bitrates with generous headroom; for local archiving, CRF 18–20 usually yields smaller files at better quality;
• Audio bitrate is separate—128–192 kbps AAC stereo is plenty.

Perceptual Quality: Can "Good Picture" Be Measured?

"Quality" sounds subjective, but the industry has long tried to quantify it:

• PSNR (Peak Signal-to-Noise Ratio): the oldest objective metric, comparing the compressed picture to the original pixel by pixel. Easy to compute, but only loosely correlated with human perception.
• SSIM (Structural Similarity Index): compares luminance, contrast, and structure—closer to the human eye than PSNR.
• VMAF: a metric developed by Netflix that uses machine learning to fuse multiple features into a predicted human score (0–100). Widely regarded as the best match to human perception and the de facto standard in streaming.

You don't need to compute these metrics yourself, but knowing they exist helps set a correct expectation: quality can be evaluated scientifically, and bitrate is only one of its ingredients—codec generation, tuning, and content characteristics all play a role. That's also why "doubling the bitrate doesn't double the quality."

Platform Re-Compression: What You Upload Is Not What Viewers See

A little-known fact with huge consequences: nearly every video platform re-encodes your upload (secondary compression)—to normalize formats, generate multiple quality tiers, and save bandwidth. The implications:

• No matter how high your source bitrate is, viewers see the platform's recompressed version;
• A higher-quality source gives the platform's encoder better "raw material," so the final result looks better—uploading a high-bitrate version is still worthwhile;
• Some platforms route high-spec sources (1440p and above) through more efficient codec tiers (e.g., YouTube's VP9/AV1 pipeline), visibly improving quality at the same content—this is the origin of the "upload your 1080p footage as 4K" trick;
• Platform target bitrates are usually lower than your source, so a 2 Mbps video that looks perfect locally may show visible damage after re-compression.

The strategy: upload a high-quality version slightly above the platform's recommended bitrate (e.g., 10–12 Mbps for 1080p), leaving headroom for the platform's recompression to consume—instead of squeezing the file to its limit yourself beforehand.

Common Misconceptions

1. "Higher bitrate always means better quality." Beyond what the content needs, extra bits just inflate the file. Critically, exceeding the source file's bitrate is meaningless—information can't be created out of thin air.
2. "CBR is stable, therefore professional." CBR's stability serves live bandwidth constraints. For file storage, the on-demand allocation of VBR/CRF is strictly better.
3. "One-pass and two-pass VBR are about the same." One-pass VBR can't see "what happens later," so its allocation is short-sighted; when size is a hard target, two-pass has a clear advantage.
4. "1080p requires exactly 8 Mbps." Every "recommended bitrate" is a reference for moderately complex content; the real requirement comes from the content itself—which is precisely why CRF exists.
5. "Compress aggressively before uploading to help the platform." The platform will re-encode anyway, and the detail you threw away is gone forever. Giving the platform a high-bitrate source is being responsible for your viewers' quality.

Practical Tips

• Everyday compression/archiving: use CRF mode—20–23 for x264, 24–28 for x265. Single pass, consistent quality.
• Hard size targets (email attachments, platform limits): work backward with the formula (target size × 8 ÷ duration) to get the target bitrate, then encode with 2-pass VBR.
• Uploading to video platforms: provide a high-quality source around 10–12 Mbps for 1080p and about 45 Mbps for 4K, leaving plenty of headroom for re-compression.
• High-motion content (games, sports): add 30–50% on top of the recommended values, or simply use CRF 18–20.
• Live streaming: only CBR or capped VBR works; keep the bitrate under 70–80% of your upload bandwidth.
• Always check the source bitrate: there's no reason to exceed it. Glance at the source in MediaInfo before choosing parameters.

Further Reading

• Video Compression: Finding the Balance Between Quality and Size — compression fundamentals and quality presets
• Containers vs. Codecs: The Packaging and the Contents of a Video File — the codec determines what your bitrate can "buy"
• Resolution and Clarity: From 480p to 4K — bitrate's other partner in crime

The "high quality / balanced / high compression" presets in this site's video compression tool are, behind the scenes, different combinations of bitrate and CRF strategy—and after reading this article, you can judge for yourself which preset suits your content, and even estimate the output file size in advance.

Related Tools

• Compress Video
• Video Converter