Bitrate Explained: The Number That Decides Your Video's Quality and Size

Every video compressor exposes a bitrate dial — and almost nobody knows what number to pick. Meanwhile, it’s the single most consequential setting in the entire pipeline: bitrate decides your file size and your quality, simultaneously, for every second of footage.

This is the guide that makes the number make sense: what it measures, the exact targets for each resolution, and the one mental model that ends bitrate guesswork forever.

What bitrate actually measures

Bitrate is the data budget per second of video. Measured in megabits per second (Mbps), it answers: “how many bits may the encoder spend describing each second?”

The math is mechanical:

file size ≈ bitrate × duration ÷ 8   (bits → bytes)

• 10 Mbps × 60 s ÷ 8 = 75 MB for one minute
• 4 Mbps × 60 s ÷ 8 = 30 MB for one minute
• Your camera’s 4K60 at 80 Mbps = 600 MB per minute

(Video dominates the file; audio adds a sliver — a 128 kbps AAC track is about 1 MB per minute.)

Why bitrate beats resolution in importance

Here’s the insight that reorganizes everything else:

Resolution sets how many pixels exist. Bitrate decides how faithfully each pixel is described.

A starved encoder facing a giant frame doesn’t produce “mildly soft 4K” — it produces blocky, smeared garbage, because the bits available can’t cover the pixel count. Concretely:

This is why “shooting in 4K” doesn’t guarantee anything — the bitrate has to feed the resolution. It’s also why compressing 4K footage down to 1080p with a proper bitrate produces such great results: you reallocate the budget from “many poorly-described pixels” to “fewer well-described pixels.”

The quality cliff

For every codec-and-resolution pair there’s a cliff — a bitrate below which quality visibly collapses, and a ceiling above which extra bits buy nothing:

quality
   │                      _______________  ← ceiling: more bits, no visible gain
   │                   __/
   │                __/
   │             __/
   │          __/
   │______＿＿ ← cliff: below this, artifacts appear fast
   └──────────────────────────→ bitrate

Sweet-spot compression = just above the cliff, far below the ceiling.

The numbers: bitrate targets by resolution (H.264)

HEVC equivalent: multiply the H.264 number by 0.6–0.7 (e.g., 1080p sweet spot ≈ 5–6 Mbps HEVC). That’s the whole codec story — why HEVC is 30–50% cheaper at the same quality comes down to smarter prediction, not magic.

Reading notes:

• The floor column is for messaging apps, where platforms re-encode again anyway and small beats pretty.
• The ceiling is not a target. Going above the sweet spot makes files bigger for zero perceptible gain — that’s literally wasted storage.
• Content matters within each band. A talking head compresses beautifully at the bottom of a range; confetti, rain, crowd pans, and foliage push you toward the top. Your camera’s 80 Mbps 4K is the ceiling setting — most footage never needs it.

Frame rate interacts with bitrate

60 fps has twice the frames of 30 fps — at the same per-frame budget that doubles the bitrate. Two honest strategies:

1. Keep total bitrate, halve per-frame spend — what “cap to 30 fps” does: 60 fps footage at a 30-fps ceiling gets every frame well-described. Static and slow scenes look identical; violent motion looks less smooth but stays sharp.
2. Keep frame rate, raise bitrate — for sports and action you care about: 1080p60 wants ~1.3× the 30 fps number.

The mistake is 60 fps at a 30-fps bitrate budget — every frame gets starved, and motion looks both choppy and blocky. If your clips are slow and steady, capping frame rate is the cheapest compression you own. (Kompress’s frame-rate control works as a ceiling and leaves slower clips untouched.)

How to stop guessing: the Kompress approach

Kompress encodes with your phone’s hardware encoder and makes the bitrate question answerable in three ways:

1. Presets sit at the cliff edge, automatically scaled. The Good preset isn’t a fixed number — it picks the bitrate just above the quality cliff for the resolution it outputs. You don’t set 8 Mbps; you set “HD, looks right.”
2. Auto follows the preset. In Advanced mode, Bitrate on Auto tracks your preset — and resolution changes re-scale it coherently, so you can’t build the mismatched 4K-resolution-at-SD-bitrate file by accident.
3. Manual for the precise. Dial an exact Mbps when you have a target file size: want a 3-minute clip under 25 MB for email? 25 × 8 ÷ 180 ≈ 1.1 Mbps… then use the platform limits math to check whether your target is realistic, or trade down resolution instead.

And because the app estimates the output size before compressing and shows a before/after player when it’s done, you never commit blind — the one rule of compression is verify before you replace the original.

The mental model, compressed

• Bitrate × duration = file size. Non-negotiable arithmetic.
• Each resolution has a cliff and a ceiling; live between them, near the cliff.
• Bitrate feeds resolution — never starve 4K, never feed SD like 4K.
• HEVC: same look, 30–40% fewer bits.
• 60 fps costs more; cap it for static scenes.

Bitrate stops being scary the moment you stop thinking “what number is best” and start thinking “what’s the right number for where this video is going.” First run free on the App Store and Google Play.