Video bitrate and compression settings: how to choose

Video compression looks like a wall of settings — codec, CRF, preset, profile, GOP — but for the everyday job of "make this file small enough to send", one equation and three decisions do nearly all the work. The equation: file size ≈ bitrate × duration. Everything else is choosing how to spend the bits that equation allows you. This guide works through the maths with real limits (email, Discord, WhatsApp), then covers the three decisions — resolution, bitrate strategy, audio — and the mistakes that produce files that are still too big or needlessly ugly. You can apply the result immediately in the video compressor, which targets a file size directly.

The bitrate equation, with real numbers

Divide the target size in megabits by the duration in seconds and you get the total bitrate you can afford. Worked examples (using size in MB × 8 = megabits, and reserving a little headroom):

• 10 MB for a 60-second clip: 10 × 8 ÷ 60 ≈ 1.33 Mbps total. Budget 0.13 Mbps for audio (128 kbps), leaving about 1.2 Mbps for video. That is a 720p budget; 1080p at 1.2 Mbps will look soft on detailed scenes.
• 25 MB for a 3-minute video: 25 × 8 ÷ 180 ≈ 1.11 Mbps total, so about 1.0 Mbps video after audio. Again 720p territory, and near the floor for detailed content — expect visible compression on fast motion.
• 8 MB (Discord's entry-level attachment limit) for a 30-second clip: 8 × 8 ÷ 30 ≈ 2.1 Mbps total, about 2.0 Mbps video — enough for decent 720p or modest 1080p.
• 16 MB (WhatsApp's media limit) for 90 seconds: 16 × 8 ÷ 90 ≈ 1.42 Mbps total, about 1.3 Mbps video.

Two lessons hide in these numbers. First, duration is destiny: doubling the length at the same target size halves the bitrate, and no setting can repeal that. Trimming dead air is compression — the trimmer often buys more quality than any encoder knob. Second, when the affordable video bitrate falls below roughly 1 Mbps for 720p or 3–4 Mbps for 1080p, reducing resolution beats starving the higher resolution of bits.

Decision 1: Resolution

Pixels are what bitrate is spent on. As a practical floor for typical real-world footage (faces, rooms, streets — not static slides):

• 1080p (1920 × 1080): comfortable at 5–10 Mbps, acceptable down to about 3 Mbps for low-motion content.
• 720p (1280 × 720): comfortable at 2.5–5 Mbps, acceptable down to about 1.2 Mbps.
• 540p or 480p: the right answer for sub-1 Mbps budgets and small phone screens; acceptable around 0.6–1 Mbps.

Static content breaks these floors happily — a screen recording of slides can look crisp at half the bitrate of a football clip, because the encoder spends bits on change, and slides barely change. Judge by content type, and when in doubt, encode ten seconds of the busiest scene as a test before committing twenty minutes to a full export.

Decision 2: Bitrate strategy — target size, CRF, or two-pass

Target-size (bitrate) encoding is the right mode when the limit is a number: an upload cap, an attachment limit, a client's spec. You (or the tool) divide size by duration and encode to that bitrate; a two-pass encode hits the target most accurately because the encoder surveys the whole file before spending bits, favouring complex scenes. CRF (constant quality) mode is the right choice when there is no size cap and you just want "good quality, whatever it weighs": with the common x264 encoder, CRF 18 is near-transparent, 23 is the balanced default, and 28 is visibly compressed but small. The trap is mixing the modes up: CRF cannot promise a size (a noisy clip at CRF 23 can be three times a clean clip's size), and a strict bitrate cap cannot promise quality. Pick the mode that matches your actual constraint.

Decision 3: Audio — small, but not free

Audio is easy to forget and it comes off the same budget. Stereo AAC at 128 kbps is transparent for most listeners; 96 kbps is fine for speech-focused clips; 64 kbps mono is acceptable for pure voice notes and saves real space in tiny targets — in the 10 MB example above, dropping audio from 128 to 64 kbps hands the video track about 5% more bits. Never leave a 320 kbps music track riding on a video you are squeezing to 8 MB: that is a quarter of a short clip's entire budget spent where nobody asked for it.

Codec choice in 2026

H.264 remains the safe default: everything plays it, everywhere, including the messaging apps and old TVs your recipients actually use. H.265/HEVC delivers roughly 25–40% smaller files at the same quality and is well supported on phones, but still trips some Windows PCs and web players without the right extensions. AV1 compresses better again and is growing fast in browsers, but encodes slowly and is the riskiest for recipient compatibility. Rule of thumb: if you know the playback device, choose the newest codec it supports; if the file is going to strangers, H.264 at a slightly higher bitrate is the professional choice.

Common mistakes

• Compressing an already-compressed file again. Every generation of lossy encoding discards more detail. Always compress from the original export or camera file.
• Keeping 4K "for quality" under a tiny cap. A 4K frame starved to 1 Mbps looks worse than a clean 720p encode of the same scene. Resolution you cannot afford is not quality.
• Upscaling or sharpening before compressing. Both add high-frequency detail that the encoder must then spend bits preserving — the opposite of the goal.
• Judging by the first frame. Encoders give early frames generous bits. Scrub to the busiest motion in the middle before you declare a setting good.
• Forgetting the container overhead and message limits. Leave 3–5% headroom under a hard cap; when a platform re-encodes uploads anyway (most social apps do), delivering slightly under its documented threshold avoids a second, uncontrolled compression.

Frequently asked questions

What bitrate should I use for 1080p?

For general footage with no strict cap, 8–12 Mbps H.264 looks clean; streaming platforms operate in this region. Under a size cap, the equation decides — and if it decides below ~3 Mbps, drop to 720p instead.

Why did my compressed video come out bigger than the original?

The original was already encoded below the bitrate you asked for, or you re-encoded a low-bitrate screen recording at "high quality" settings. Compression cannot beat a file that is already small without losing quality; check the source bitrate (file size × 8 ÷ duration) before choosing settings.

Is two-pass encoding worth the wait?

When hitting an exact target size matters, yes — it is the most accurate way to land just under a cap with the best distribution of bits. For quick one-off clips with slack in the budget, a single pass is fine.

Should I change the frame rate to save space?

Rarely as a first move. Halving 60 fps to 30 fps does roughly halve motion detail to encode, and is acceptable for talking-head and screen content; it visibly harms sports and gaming footage. Try resolution and bitrate first.

What does the compressor on this site do for me?

You give it a target size; it works the equation, picks the bitrate (in the browser, with the FFmpeg engine), and encodes locally — your video is never uploaded, which is the point when the footage is a client's, a child's, or unreleased.