Video Compression Guide: Bitrate, Resolution, and Codec
Video compression can feel like a maze of technical jargon — bitrate, codec, keyframe interval, CRF, VBR versus CBR. But at its core, compressing video is about answering one question: how small can I make this file while keeping it looking acceptable for its intended purpose? The answer changes depending on whether you are archiving a family video, uploading to YouTube, sending via WhatsApp, or embedding on a website. This guide cuts through the complexity and gives you a practical framework for choosing compression settings with confidence.
Bitrate: The Most Important Compression Variable
Bitrate is the single most influential setting in video compression. It controls how many bits of data are used per second of video, and directly determines the trade-off between file size and visual quality. Bitrate is measured in kilobits per second (Kbps) or megabits per second (Mbps). A 1-hour video at 5 Mbps will be approximately 2.25 GB. The same video at 1 Mbps will be approximately 450 MB. The question is: does it still look acceptable at 1 Mbps? The answer depends heavily on the content. Video with a lot of motion — sports, action scenes, busy crowds — needs more bitrate to avoid blurring and blocking artifacts. Video with mostly static backgrounds and slow movement (a talking head, a lecture recording, a slow product demo) compresses very efficiently even at low bitrates. As a starting reference: for 1080p video intended for web viewing, 3–6 Mbps is a reasonable target with H.264. For 720p, 1.5–3 Mbps is appropriate. For 480p social clips, 0.8–1.5 Mbps is usually enough. These are starting points — always preview the result and adjust. Two bitrate modes exist: constant bitrate (CBR), which uses the same rate throughout, and variable bitrate (VBR), which allocates more bits to complex scenes and fewer to simple ones. VBR generally produces better quality at the same average file size and is preferred for most use cases.
Resolution: The Hidden Multiplier on File Size
Resolution and bitrate are deeply interlinked. A given bitrate supports a certain pixel density — more pixels at the same bitrate means each pixel gets fewer bits, which means lower quality per pixel. The most common resolutions and their pixel counts are: 4K (3840x2160) at 8.3 million pixels, 1080p (1920x1080) at 2.1 million pixels, 720p (1280x720) at 921,000 pixels, and 480p (854x480) at 409,000 pixels. Going from 4K to 1080p reduces pixel count by 75%. Going from 1080p to 720p reduces it by 56%. This matters because reducing resolution lets you achieve the same perceived quality at a dramatically lower bitrate. A 1080p video at 5 Mbps might look equivalent to a 720p version at 2.5 Mbps when both are displayed on a laptop screen or phone — the 720p version is half the file size. For archiving or content destined for large displays, keeping the original resolution makes sense. For sharing or embedding in contexts where viewers will watch on small screens, dropping to 720p is often a practical size-saving decision with no visible quality penalty. One important caveat: down-scaling resolution is a one-way operation during export. Always keep the original high-resolution source file and export compressed copies for different use cases.
Codecs in 2026: H.264, VP9, H.265, and AV1
The codec is the algorithm that encodes your video data. Different codecs achieve different levels of compression efficiency, and codec choice affects both file size and playback compatibility. H.264 (AVC) is the most universally compatible codec. It plays on virtually every device, browser, smart TV, and platform. For maximum compatibility — especially for content you are sending to non-technical recipients — H.264 in an MP4 container is the right choice. Its compression efficiency is lower than newer codecs, but its ubiquity is unmatched. VP9 is Google's open-source codec used in WebM files. It achieves approximately 30–50% better compression than H.264 at equivalent quality. YouTube uses VP9 extensively. It is well-supported in Chrome, Firefox, and Edge, but has historically had weaker support in Safari and on Apple devices. In 2026, Safari 17+ supports VP9, so it is becoming a viable choice for web-first content. H.265 (HEVC) is a successor to H.264 that achieves roughly 40–50% better compression. It is widely supported on Apple devices and modern smart TVs, but has licensing costs that have slowed browser adoption. It is a strong choice if your target audience is primarily on Apple hardware. AV1 is the newest open-source codec, offering the best compression of the group — up to 50% smaller than H.264 at equivalent quality. Hardware decoding support is growing rapidly, and browser support is strong as of 2026. AV1 encoding is, however, significantly slower than H.264 encoding, making it less practical for quick browser-based compression.
Choosing the Right Settings for Each Use Case
Abstract numbers are less useful than concrete recommendations tied to real-world scenarios. Here is a practical settings guide. YouTube upload: YouTube recompresses every uploaded video, so pre-compressing at a medium-high quality is more important than squeezing every byte. Use 1080p at 8 Mbps or 720p at 5 Mbps with H.264. This gives YouTube enough quality to produce a good final result while keeping upload times manageable. Instagram Reels and TikTok: These platforms strongly recompress, so aim for 1080p at 5–8 Mbps to ensure the platform's compression step starts from good material. Keep aspect ratios to 9:16 for vertical content. Email and messaging: Target files under 25 MB for email and under 16 MB for WhatsApp. For a 5-minute clip this typically means 720p at 0.5–0.8 Mbps, which is aggressive but acceptable for conversational or demo content. Website embedding: Web-embedded video should be as small as possible. Target under 10 MB for clips under 2 minutes. Use WebM (VP9) at 720p and 1–2 Mbps for modern web projects. Personal archive: Use H.264 at 1080p and 4–5 Mbps for a good balance of quality and long-term compatibility. This is roughly half the bitrate of most smartphone originals, with virtually no visible quality loss on screens up to 65 inches.
Frequently Asked Questions
- What is CRF and how does it differ from setting a fixed bitrate?
- CRF stands for Constant Rate Factor. Instead of targeting a specific bitrate, CRF targets a constant level of visual quality across the entire video. The encoder automatically allocates more bits to complex scenes and fewer to simple ones. Lower CRF values mean higher quality and larger files; higher values mean smaller files with more compression. The WikiPlus browser compressor uses a bitrate-based approach because it is simpler to reason about file size targets, but CRF encoding (available in tools like HandBrake and FFmpeg) is superior when quality consistency matters more than hitting a specific file size.
- Does frame rate affect file size, and should I reduce it to compress video?
- Yes, frame rate affects file size roughly proportionally — 60fps video is approximately twice the size of 30fps video at the same resolution and bitrate, all else being equal. Reducing frame rate from 60fps to 30fps can cut file size significantly with no quality loss for content that does not have fast motion. For screen recordings, tutorials, or talking-head videos, 24fps or 30fps is entirely sufficient and noticeably more space-efficient than 60fps originals.
- Can I compress a video that is already compressed without making it worse?
- Re-compressing a video always introduces some quality loss, but the practical impact depends on how aggressively you compress. Re-encoding an H.264 video to another H.264 video at a similar or higher bitrate produces barely perceptible degradation. Re-encoding to a significantly lower bitrate introduces more visible artifacts, but starting from a higher-quality source gives the encoder more data to work with. The key rule is: always re-compress from the highest-quality source available, not from a previously compressed copy.