Beginner's Guide to Online Video Compression

Video compression sounds technical, but the underlying idea is simple: most of the data in a raw video file is redundant, and compression removes that redundancy in ways the eye barely notices, if it is done properly. Understanding roughly how it works — rather than just clicking a "compress" button and hoping — makes the difference between a file that looks fine at a fraction of the size and one that looks noticeably worse for barely any savings.

What Compression Actually Does

An uncompressed video is enormous — a single minute of raw 1080p footage can run into gigabytes. Compression works in two layers. Intra-frame compression reduces redundancy within a single frame, similar to how a JPEG compresses a photo. Inter-frame compression is where the bigger savings come from: rather than storing every frame in full, the encoder stores a complete "keyframe" periodically and then, for the frames in between, stores only what changed. A static shot of someone talking with a still background compresses far more efficiently than a fast pan across a crowd, because there is simply less changing between frames.

This is also why the same bitrate can look great on one video and blocky on another — a talking-head interview and a skateboarding video at identical settings will produce very different results, because one has far more inter-frame change for the encoder to capture.

Lossy vs. Lossless

Nearly all video compression for sharing purposes is lossy — it permanently discards some information to save space, and that information cannot be recovered afterwards. Lossless compression (formats like FFV1) preserves everything perfectly but achieves far smaller size reductions, and is mainly used for archival masters or intermediate editing files, not for anything you plan to upload or send. For everyday sharing, the goal with lossy compression is not to avoid quality loss entirely — that is not the tradeoff on offer — but to lose only the detail a viewer would not notice anyway.

The Settings That Matter

Bitrate

The single biggest lever. Higher bitrate means more data allocated per second of video, which generally means better quality but a bigger file. Halving the bitrate roughly halves the file size, though the relationship between bitrate and perceived quality is not linear — there is usually a point below which quality drops sharply, and above which extra bitrate barely improves what the eye can see. For most 1080p content, that sweet spot sits around 4–8 Mbps depending on how much motion is in the footage.

Resolution

Downscaling from 4K to 1080p, or 1080p to 720p, cuts the amount of data the encoder needs to represent per frame substantially — often more effective for reducing file size than simply lowering bitrate at the original resolution, and it avoids the soft, blocky look that comes from squeezing too much resolution into too few bits.

Frame rate

Dropping from 60fps to 30fps removes half the frames the encoder needs to store, and for most non-action content the difference is barely perceptible. This is one of the easiest, most overlooked wins in casual compression.

Codec

Different codecs compress the same visual quality into different amounts of data. H.264 is the reliable, universally compatible baseline. H.265 (HEVC) and AV1 achieve meaningfully smaller files at equivalent quality but need more processing time to encode and are not universally supported for playback, particularly HEVC on older Android devices and some browsers.

Constant vs. Variable Bitrate

A constant bitrate (CBR) encode allocates the same amount of data to every second of footage regardless of complexity, which is simple but wasteful — it spends bits on simple scenes that did not need them and starves complex scenes that did. A variable bitrate (VBR) encode allocates more data to complex, high-motion sections and less to static ones, generally producing better quality at the same average file size. Most modern compressors, including browser-based ones built on ffmpeg, default to VBR or offer it as an option — use it unless you have a specific streaming requirement that calls for constant bitrate.

Doing It in the Browser

Online compressors built on WebAssembly ports of ffmpeg can process a video entirely inside the browser tab, meaning the file never leaves your device for processing — a meaningful difference from older server-upload compressors, particularly for anything personal or unpublished. The typical workflow:

• Upload or select the source file in the tool.
• Choose a target resolution matching where the video will be viewed.
• Set a bitrate or quality level — many tools offer named presets like "Web," "Social," or "High Quality" that map to sensible bitrate ranges rather than requiring you to pick a number blind.
• Run the compression and compare the result against the original at actual viewing size before deciding it is acceptable.

For a deeper technical breakdown of file-size targeting and platform-specific limits, our companion guide on optimising video files for faster sharing covers bitrate ranges by resolution and platform upload caps in more detail. If your source is a video you have already published somewhere and need a local copy of to compress further, the YouTube downloader retrieves the file so you can re-encode it.

How to Tell If Compression Went Too Far

• Blockiness in areas of flat colour or gradients is the clearest sign the bitrate is too low for the resolution.
• Motion smearing, where moving objects lose detail and blur into the background, suggests the encoder does not have enough bitrate to capture inter-frame changes properly.
• Banding in skies or gradients indicates insufficient bit depth or bitrate for smooth colour transitions.

If any of these appear, the fix is almost always to raise the bitrate slightly or reduce the resolution rather than trying to fix it after the fact — compression artefacts cannot be removed by a second compression pass; they can only be masked or made worse.

Common Beginner Mistakes

• Compressing an already-compressed file repeatedly. Each pass is a fresh lossy encode; always work from an original master where possible.
• Assuming a smaller file is always better. The goal is the smallest file that still looks acceptable for its purpose, not the smallest file possible.
• Ignoring audio. A high video bitrate paired with uncompressed audio wastes space; match audio bitrate to content type (128 kbps for speech, 192–256 kbps for music).

The Bottom Line

Compression is a set of tradeoffs between bitrate, resolution, frame rate, and codec, not a single button that magically shrinks a file with no cost. Understanding what each setting does lets you choose deliberately — matching the compression to what the footage actually contains and where it is going — rather than accepting whatever a default preset happens to produce.