Guide
How to compress a video without wrecking it
Updated 2026-08-28 · 9 min read
Every smaller file throws information away. “Lossless” 4K at 8 MB is a myth. What you can do is spend every leftover bit on the parts of the picture people actually notice. This is the practical version, not a codec thesis.
File size is bitrate × time
A video file is a stream of bits. If you must hit 25 MB in 60 seconds, you get a fixed allowance of bits per second. That allowance is the bitrate. Quality is how well the encoder spends it. Resolution is how many pixels those bits have to paint.
People blame “the compressor” when the math is the problem. A five-minute 1080p clip in 16 MB will look soft. A 20-second 1080p clip in 25 MB can look nearly identical to the original. Duration is a quality setting, whether you treat it that way or not. Trim before you encode.
Resolution is a quality tool, not a brag
1080p at a starved bitrate looks worse than 720p at a healthy one. The encoder is spreading peanut butter over a bigger slice of bread. For Discord 25 MB and WhatsApp 16 MB, Auto should often pick 720p or 480p for anything longer than a minute.
Never upscale. If the source is 720p, “export 1080p” invents fake pixels and wastes bits. Shrink Clip will not upscale. Other tools will, and you will pay for it.
Why two-pass encoding exists
One-pass encoding guesses as it goes. Easy scenes (a still talking head) get too many bits; explosions and screen-text get too few, or the file overshoots the cap. Two-pass encoding watches the whole clip first, then spends bits where motion and detail actually happen. It is slower. It is why a 24.6 MB Discord file can look cleaner than a 24.6 MB file from a “fast” slider.
Constant quality (CRF) modes in desktop ffmpeg are excellent when you do not care about an exact size. They are the wrong tool when the platform will reject 26 MB. Size-targeted two-pass is the right tool for Discord, WhatsApp, Gmail, and TikTok’s app cap.
Audio, motion, and other quiet killers
Stereo AAC at 128 kbps is enough for speech. 96 kbps is fine if you are desperate. 320 kbps on a 16 MB WhatsApp clip is vanity — that is 20% of the whole file on sound. Strip audio only when there is no sound worth keeping.
High motion (sports, games, handheld walking) needs more bits than a static interview. If the clip is a screen recording of a spreadsheet, you can get away with a lower bitrate than a football match of the same length. If it still looks blocky, shorten it or drop resolution before you crank mysterious “quality” sliders to 100.
What “good enough” looks like
On a phone in a chat bubble, most people cannot tell a well-spent 25 MB clip from the 200 MB original. On a 27-inch monitor, they might. Match the destination. Discord, WhatsApp, and email are not Netflix. Spend the budget. Do not pretend you can keep 4K HDR for a sticker-sized player.
If someone needs archive quality, send a link to cloud storage. Compression is for the message that has to arrive now.
Ready to try it? Compress a video in your browser— nothing is uploaded.