Resolution gets all the attention, but bitrate is what actually decides how a video looks and how big it is. Here is how to think about it when compressing footage.
When people talk about video quality, they usually talk about resolution — 1080p, 4K, 720p. But resolution is only half the story. The number that actually determines how clean a video looks and how large the file is, is the bitrate: the amount of data used per second of video. Two videos at the same resolution can look completely different because they have different bitrates.
What bitrate measures
Bitrate is expressed in bits per second — kilobits (kbps) or megabits (Mbps). A video at 5 Mbps uses 5 million bits of data for every second of footage. Multiply by the duration and you get the approximate file size: a 5 Mbps video that runs 60 seconds is roughly 37 MB. Raise the bitrate and the file grows; lower it and the file shrinks but quality drops.
Bitrate, resolution, and framerate
Bitrate does not exist in isolation. A given bitrate has to cover every pixel of every frame. At 1080p and 30 frames per second, the encoder has about 62 million pixels per second to describe; at 720p and 30 fps, about 28 million. So 5 Mbps at 720p can look crisp, while 5 Mbps at 1080p may show compression artefacts, because the same budget is spread over more than twice as many pixels. Higher resolution and higher framerate both demand a higher bitrate to look equally clean.
Constant vs variable bitrate
Constant bitrate (CBR) uses the same data rate throughout, which is simple but wasteful — a static talking-head shot gets the same budget as a fast pan through a forest. Variable bitrate (VBR) spends more bits on complex motion and fewer on simple scenes, which produces better quality at a smaller average size. Most modern encoders use VBR by default, often in a two-pass mode that analyses the whole video first to allocate bits optimally.
Where artefacts come from
When the bitrate is too low for the content, the encoder has to throw away detail. The result is visible artefacts: blocking (square chunks around edges), banding (stair-stepping in gradients), smearing during motion, and a general softness. High-motion content — sports, water, confetti, fast pans — needs a much higher bitrate than static content to avoid these. A webinar with a still speaker looks fine at 1.5 Mbps; the same bitrate on a basketball game looks terrible.
Choosing settings when compressing
When you shrink a video with the Video Compressor, the quality preset maps to a target bitrate. Start with a medium preset and check the result. If it looks clean, try a lower preset to save more space. If you see blocking or smearing, step back up. For footage destined for a specific platform, match the platform’s recommended bitrate rather than guessing — most social platforms re-encode uploads anyway, so sending an enormous file just wastes upload time.
Resolution vs bitrate: which to cut first
- If the video looks fine but is too large, lower the bitrate first — it is the biggest lever on file size.
- If lowering the bitrate introduces artefacts, lower the resolution instead so the remaining bitrate covers fewer pixels.
- Cut framerate only for content with little motion (slides, screen recordings); it harms smoothness on real footage.
- For web delivery, 1080p at a moderate bitrate usually beats 4K at a starved bitrate.
- Always compress once from the highest-quality source; re-compressing compounds artefacts.
Audio matters too
Audio has its own bitrate, usually 128–256 kbps for stereo. It is small compared to video, but a 256 kbps audio track on a video with a 1 Mbps video track is a meaningful fraction of the total. Dropping audio to 128 kbps is often inaudible for speech content and saves bytes. The Video Compressor routes the original audio through the Web Audio API so the soundtrack survives the re-encode at a sensible rate.
Bitrate is the dial that decides the trade-off between quality and size. Understand it, and you can shrink a video predictably instead of guessing and re-encoding over and over.