Compress a video for WhatsApp without a visible quality hit

Why you’d do this

WhatsApp will send almost any video — right up until it hits its own 16 MB limit for a chat attachment. Cross that line and one of two things happens: the send fails outright, or WhatsApp quietly re-encodes the file itself to squeeze it under the cap. That second option is the one worth avoiding. Its own compressor does not know which part of your clip matters, so it applies the same blunt bitrate cut everywhere — faces blur, text becomes unreadable, fast motion turns to mush. You send a video you were happy with and the person on the other end gets a worse copy of it, with no say in the trade-off.

Compressing the file yourself, before you attach it, flips that. You choose the target size, the tool picks a bitrate that actually fits it, and you get to look at the result before you send it — rather than finding out what WhatsApp decided after the fact.

How, with the named tool

Dzzz’s Compress Video tool runs entirely in your browser — the video never leaves your device, so there’s no upload step to wait on and nothing sent anywhere.

1. Add your video. Drop an MP4, MOV or WebM file onto the dropzone. A preview loads so the tool can read its duration.
2. Pick a target. Choose “WhatsApp (16 MB)” directly — it’s one of the built-in presets alongside “Email (25 MB)” and “Custom MB” — or switch to “Quality” if you’d rather compress by picking Low, Medium or High instead of hitting a specific file size.
3. Set the value. With a Custom MB target, type the number of megabytes you’re aiming for. With Quality, just pick the preset.
4. Compress and save. Tap “Compress Video”. The progress bar tracks ffmpeg’s own real encoding progress — not a fake animation — so what you see is what’s actually happening. When it finishes, the tool shows the size before and after side by side. Tap “Save / Share” to get the file, then attach it in WhatsApp as normal.

If you’re sending a WhatsApp Status or a video meant to fill a phone screen vertically, run it through Aspect Ratio for Social first — pick 9:16, fit or fill the frame, and drag the focal point if you’re cropping — then compress the result. Doing the crop before the compression pass means the compressor isn’t wasting bitrate on parts of the frame you were going to cut anyway.

What to watch for

Target-size mode uses a two-pass bitrate calculation, not a single guess. The tool works out from your target size and the clip’s duration what bitrate will land inside that size, encodes once to check, then finishes with that number. It will never hand you back a file larger than the one you started with — if a run would do that, your original is kept and nothing is overwritten.

There’s a floor. If your target is too small for the video’s length — say, 16 MB for a ten-minute clip — the tool refuses the job outright rather than producing something ugly to hit an impossible number. Trim the clip or raise the target.

Target-size presets also scale the video down to 720p. That’s part of how they hit small file sizes without the bitrate collapsing — a lower resolution at a livable bitrate looks better than the original resolution starved down to nothing.

There’s a duration cap, and it’s different on phone and computer. Videos longer than 5 minutes (300 seconds) on a phone, or 15 minutes (900 seconds) on a computer, are refused rather than attempted. Re-encoding is CPU-bound work happening on the device you’re holding, and a phone doing several minutes of video encoding is a genuinely slow, battery-draining task — the tool is upfront about this and always shows a note that it’s faster on a computer. If you’re on a laptop or desktop, that’s the better place to run a long clip through.

FAQ

Will the compressed video look noticeably worse?

Not if you leave headroom. Compression is a real trade-off between file size and detail, and there’s no way around that — but a two-pass bitrate calculation targeted at 16 MB usually holds up fine for a phone-shot clip under a minute or two. If you can see banding or mush in the result, try a Custom MB target a couple of megabytes above 16 (still under most chat limits) rather than trusting WhatsApp’s own re-encode to do better; it won’t.

Why does WhatsApp still make it blurry sometimes even after I compress it?

Two compression passes rarely help each other. If your file is already close to 16 MB when you send it, WhatsApp should pass it through with little or no extra re-encoding. But sending something already-compressed at, say, 20 MB still crosses the cap, and WhatsApp will compress it a second time on top of your first pass — and a second lossy pass on already-lossy footage is where real quality loss shows up. Aim comfortably under the cap, not right at it.

Does any part of this upload my video anywhere?

No. Compression and any aspect-ratio cropping both run locally in your browser using ffmpeg compiled to WebAssembly — the file is read from your device, processed on your device, and saved back to your device. Nothing is sent to a server at any point in the process.