Mail was never designed to carry video. Most providers cap a message at somewhere between 20MB and 25MB in total — attachments, text and encoding overhead together — and a phone shooting 4K writes roughly 300 to 400MB per minute. A clip you filmed without thinking about it can be twenty times the limit before you have finished saying "I'll just send it over".
There are only three real levers, and they are not equally powerful:
Most people reach for the second one, get a disappointing result, and conclude the video "can't be compressed". It can. They just pulled the weakest lever.
Halving the height of a frame also halves its width, which removes about three quarters of the pixels. Going from 1080p to 720p drops roughly 55% of them; 1080p to 480p drops about 80%. Nothing you can do to the quality slider comes close to that, because the quality setting is only deciding how carefully to describe pixels that resolution has already deleted.
The reason this feels wrong is that we think of resolution as the measure of quality. For a video watched full-screen on a desktop monitor, it is. For a video watched in a mail client, in a preview pane, or on a phone held at arm's length, 720p is indistinguishable from 1080p — and it is a third of the size.
The one-setting answer. If you only change one thing: open Advanced options in Compress Video and set Limit resolution to 720p. For most phone footage that alone lands you inside a mail limit, with a result nobody will notice is smaller.
Two things the tool does here that are worth knowing. It never enlarges — a clip that is already 480p and asked to cap at 720p keeps its own resolution rather than being blown up into a bigger, blurrier file. And it forces the output dimensions to even numbers, because the encoder refuses odd ones outright; an oddly-sized screen recording would otherwise fail the whole run.
If your mail provider allows 20MB, you do not have to guess your way there. Turn on Compress to a target file size and type the number.
The useful part is what happens before any encoding starts. The tool reads the clip's length the moment you choose the file, works out the bitrate that would land near your target, and checks whether that bitrate is still enough for a watchable picture. If it isn't, it refuses immediately and tells you the smallest size worth asking for — rather than spending two minutes of your laptop's CPU producing a smear you would throw away.
Roughly, with audio kept, the floor is about 4.5MB for a three-minute clip and about 1.5MB with the audio removed. Ask for 2MB on a three-minute video and you will be told so up front, with the real number, before you have waited for anything.
Two more honest touches in that flow:
-compressed to something it never compressed.The audio track is encoded at a fixed 128 kbps, which is about 1MB per minute regardless of what you do to the picture. That sounds trivial until you are 1.5MB over a 20MB limit on a five-minute clip.
And a great deal of the video people email has audio nobody will ever play: screen recordings, timelapses, dashcam clips, silent product shots, anything filmed in a quiet room by accident. Ticking Remove the audio track is frequently the single change that closes the last gap — and unlike the quality slider, it costs the picture nothing at all.
Nothing is uploaded. The video is decoded, re-encoded and handed back entirely inside your browser tab, using a WebAssembly build of FFmpeg. No copy reaches a server and no account is needed — which for family footage, client work, medical or legal recordings is not a nicety but the only version of this task that is safe to do on a website at all.
The first time you compress anything, the page has to fetch the video engine itself — a WebAssembly build of FFmpeg, around 30MB. That download happens before a single frame is encoded, so on a slow connection there is a stretch of ten to thirty seconds where the encoder has not started and cannot report any progress at all.
The progress bar is deliberately indeterminate during that window — a sweeping bar rather than a percentage — because a bar parked at 2% reads as broken, and people close the tab. Once real encoding begins it switches to a true percentage. Compress a second clip in the same session and the engine is already in memory, so that part disappears entirely.
The output is always an MP4 (H.264, widely-compatible colour) with its index moved to the front of the file, so it starts playing before it has finished downloading — which is the entire point of a video you are sending to someone else.
Compressing a nine-minute recording to email someone a forty-second moment is the expensive way round. Cut it first with Trim Video — length is a bigger multiplier on file size than any encoder setting, and a shorter clip then compresses from a far smaller starting point. Trim first, compress second, if at all.
If you are sending an interview, a lecture, a voice memo or a rehearsal, the picture is dead weight. Video to Audio pulls the track out as an audio file, which is usually a small fraction of the video's size and is the correct thing to attach anyway.
A common instinct, and it usually makes the file bigger. GIF has no modern video compression and no audio; a few seconds of real footage can outweigh the MP4 it came from. GIFs are the right answer for short silent loops that must autoplay inline — Video to GIF does that well, and GIF Optimizer will shrink one you already have — but reach for them because you want a loop, never because you want a smaller file.
Video is already compressed, so putting it in an archive typically saves a percent or two while making the attachment harder for the recipient to open on a phone. Zip Tool earns its place bundling many different files together — not shrinking one that is already dense.
Free, no sign-up, nothing uploaded. Cap the resolution, compress to an exact size in MB, or drop the audio track.
Open Compress Video