Video Tools·4 min read

How Video Compression Works: CRF, Bitrate, Limits

Every video that travels the internet has been compressed, usually several times, and the settings chosen decide whether it arrives crisp or as a smear of blocks. Knowing how video compression works, even at the level of one worked example and two tradeoffs, turns the settings panel from guesswork into a set of levers. This article covers what an encoder actually throws away, when CRF beats a target size and vice versa, the bitrate versus resolution decision, and the attachment limits that make all of this necessary in the first place.

Open the tool All insights

How video compression works, minus the math degree

Encoders bet that frames resemble their neighbors.

A video is mostly redundancy. Frame 241 looks almost exactly like frame 240, so instead of storing every frame as a picture, an encoder stores occasional full keyframes and then, for the frames between, only the differences: which blocks moved where, and what small corrections remain. Codecs like H.264 and VP9 spend most of their cleverness on predicting those differences cheaply.

The second trick is throwing away detail your eye won't miss, fine texture in fast motion, subtle gradients in dark areas. How aggressively the encoder discards is the quality setting. CRF, the Constant Rate Factor used in this tool's quality mode, fixes that aggressiveness and lets file size land wherever the footage demands.

When compressing a video becomes urgent

The file is fine until it has to go somewhere.

Nobody compresses video for fun. The trigger is a limit: a two minute phone clip that weighs 300 MB and an email that stops at 25, a screen recording for a bug report that Discord refuses, a lecture upload with a hard cap, a client review link that shouldn't take twenty minutes on hotel Wi-Fi.

The clip's content rarely needs 300 MB. Phone cameras record at generous bitrates to preserve editing headroom, so the same footage recompressed sensibly is dramatically smaller with little visible change. The job is picking sensible.

A video compression worked example: 60 seconds into 10 MB

Target size mode is just arithmetic.

Input: a 60 second 1080p phone clip. Requirement: fit under a 10 MB chat limit. In the Video Compressor, choose MP4, switch to Target size mode, set 10 MB. The tool converts 10 MB into bits, divides by 60 seconds, shaves a few percent for container overhead, and reserves 128 kbps for the audio track. Result: roughly 1200 kbps allocated to video, and an output that lands just under 10 MB.

Whether 1200 kbps looks good depends on the footage. A talking head at 1080p survives it; a handheld action shot won't. That's the cue to add a second lever, dropping Resolution to 720p, so the available bits cover fewer pixels, each one better.

Bitrate vs resolution: which lever shrinks video better

Starved pixels look worse than fewer pixels.

The bitrate vs resolution tradeoff has a consistent answer at the small end: when bits are scarce, reduce resolution before quality. 720p at a healthy bitrate beats 1080p at a starved one, because a starved encoder produces blocking and smearing across the whole frame, while a downscale just softens it. Viewers forgive soft; they notice blocky.

Frame rate is the third, often forgotten lever. Screen recordings and slide walkthroughs lose nothing meaningful at 24 or even 15 fps, and every dropped frame is bitrate handed back to the frames that remain. Save 60 fps for content that actually moves.

Compressing for email limits: Gmail, Outlook, and Discord numbers

Know the cap, then aim below it.

The limits that drive most compressing for email limits sessions: Gmail attaches up to 25 MB before it silently switches to a Drive link, Outlook's default cap is 20 MB, and Discord's free tier currently allows 10 MB per file, a number Discord has changed before, so check it if the send fails. Corporate mail servers are often stricter than any of these.

Practical rule: target about 5 percent under the cap, 24 MB for a 25 MB limit, 9.5 for 10, since container overhead and bitrate variance can push the final file slightly past the arithmetic. Target size mode exists for precisely this situation; CRF mode is for when quality matters and size merely shouldn't be silly.

Video compression mistakes that waste quality

Bits go missing in predictable ways.

The recurring errors, all cheap to avoid:

Recompressing an already heavily compressed file at high quality settings, paying encode time to enlarge it.
Forcing 4K dimensions into a tiny size budget instead of downscaling first, guaranteeing block artifacts.
Compressing the full clip when only 20 seconds matter; the Trim fields are the cheapest compression available.
Re-encoding the same file over and over across edits, stacking generation loss; keep one master and export from it.
Sending WebM to someone whose ancient corporate machine only opens MP4, then compressing again in a panic.

Three settings tips for smaller video files

Order of operations matters.

Trim first, always: cutting a 3 minute recording to the 40 seconds that matter is a bigger win than any encoder setting, and it makes every subsequent target easier to hit. Second, mute when the audio carries nothing; the 128 kbps track costs about 1 MB per minute, which is decisive under a 10 MB cap.

Third, pick the codec by destination: MP4 with H.264 for email, clients, and anything that must open everywhere; WebM with VP9 when it's headed for the web and you want the same quality in a smaller file.

Video Compressor vs Image Compressor and Screenshot Editor

Different media, same instinct.

The Video Compressor is the only tool here that touches moving pictures, and everything runs locally through FFmpeg compiled to WebAssembly, so footage never uploads anywhere. For the still images around a video project, thumbnails, posters, hero frames, the Image Compressor does the equivalent size-for-quality trade on JPGs and PNGs.

And when what you're really sharing is a single moment from the screen, skip video entirely: capture a frame, dress it up in the Screenshot Editor, and send kilobytes instead of megabytes.

Try it now

Open Video Compressor

The tool is one click away. No sign up, no upload, no payment.

Open Video Compressor

Write a review