How to Make a Video File Smaller for Email

Renaming a MOV to MP4 does almost nothing. We remuxed the same clip into a new container with -c copy and the file size moved by 0.00% to 0.01%, nowhere near the double-digit drop people expect from a format switch. Getting a real reduction means opening MOV to MP4, or whichever converter matches your file, and setting Bitrate under Advanced options low enough for wherever the video is going.

Shrink a video for email

1. Open MOV to MP4, or AVI to MP4, MKV to MP4, WebM to MP4, whichever matches your file, and drop it in.
2. Open Advanced options and set Bitrate. This is the control that changes the file size. For anything headed to email, the lowest preset, 1 Mbps, is the one to reach for first.
3. Set Resolution to 720p. It will not make the file smaller (our measurements below show why), but at 1 Mbps it is the setting that looks best, ahead of both 1080p and 480p. Go to 480p only if you drop below 1 Mbps.
4. Convert and download the result.

What are the actual email attachment limits?

Outlook.com is worth flagging on its own: several guides still quote 20 MB, but Microsoft's current support page states 25 MB. A workplace account is governed by whatever its administrator set in Exchange, not by the Outlook.com consumer default.

Does changing the container make a video smaller?

Barely, and sometimes it makes the file a few bytes bigger.

We took a 1920x1080 H.264 clip, repackaged it into a MOV and an MKV with FFmpeg's -c copy, then remuxed each back to MP4 the same way, copying the encoded stream rather than decoding and re-encoding it. MOV to MP4 went from 30,704,465 to 30,704,489 bytes, a change of 24 bytes. MKV to MP4 went from 30,703,320 to 30,706,402 bytes, a change of 3,082 bytes, or 0.01%.

Both differences are container bookkeeping. The video and audio inside are untouched; only the wrapper around them changed.

FileFlip does the same thing when it can. When the codec inside your file is one MP4 can already hold, H.264 or HEVC, and you have not touched Resolution, Bitrate or Frame rate, the browser copies the encoded stream into the new container instead of decoding and re-encoding it. That is faster and lossless, and it is also why a container swap alone rarely shrinks anything.

Does a lower resolution make the file smaller?

No. At a fixed bitrate, file size tracks bitrate and duration, not resolution.

We encoded the same source clip at 1080p, 720p and 480p, holding the video bitrate fixed at each of five levels, and measured the output:

Every row stays within about 11% across all three resolutions, mostly much closer than that. Frame rate barely moves it either: the same clip at a fixed 2 Mbps came out 2.11 MB at 30 fps and 2.17 MB at 60 fps over 10 seconds, a 2.4% difference.

Bitrate and duration set the file size. Resolution and frame rate decide what the encoder does with the bits it is given, which shows up as quality rather than as megabytes.

Does a lower resolution look better at the same bitrate?

It depends on how low the bitrate already is.

We measured VMAF for 1080p and 480p at three bitrates, scaling every encode back to the source's 1920x1080 before comparing it:

Below 1 Mbps, dropping resolution is a large, clear win: at 500 kbps, 480p scores 48.3 against 1080p's 32.5, which is the difference between watchable and not. At 2 Mbps the full frame wins, 80.5 against 69.4, because there is enough budget to use the extra pixels.

At 1 Mbps, which is FileFlip's lowest preset and the one an email attachment needs, the best of the three is 720p at 66.8, ahead of 1080p at 62.5 and 480p at 61.9. It is the middle setting rather than the lowest, because 480p throws away pixels the bitrate could still have afforded while 1080p spreads them too thin. That is why the steps above say 720p first.

How long can a clip be and still fit in an email?

Shorter than the arithmetic in most guides suggests once you add real audio and container overhead.

We built a 3-minute test clip and encoded it at FileFlip's lowest settings, 480p, 1 Mbps video, 96 kbps audio, the same combination a straightforward guess at "small enough for email" would reach for. The output was 24.4 MB, which clears Gmail by 600 KB and misses a 20 MB limit outright. The arithmetic agrees once you run it over the whole clip: 1.096 Mbps of video and audio across 180 seconds is 24.7 MB, and the encode landed just under that. A 3-minute clip at the lowest setting FileFlip offers is right at the edge of what you can attach.

These durations assume 96 kbps audio and FileFlip's exact bitrate presets, and they are why a 3-minute phone clip needs the lowest preset and a bit of luck to clear Gmail's 25 MB limit, and will not clear a stricter 20 MB one at all. If your clip runs long, cut it before you convert it. FileFlip has no trim control, so do that in the app that recorded it, Photos on iPhone or Mac has one built in, or a proper editor, then convert the trimmed file.

Does zipping a video file help?

No, and it can even add a few bytes.

We zipped the same MP4 twice. A 30.7 MB clip came out 0.007% larger zipped. A 24.4 MB clip came out 0.89% smaller.

Video is already compressed by its codec, so a general-purpose compressor like zip finds almost nothing left to squeeze. The recipient just gets an extra step of unzipping before they can watch anything.

When shrinking won't be enough

If you have already set Bitrate to 1 Mbps and Resolution to 720p and the file is still too big, the clip is too long for an attachment. Upload it to Google Drive, Dropbox, iCloud or OneDrive and paste the share link into the email instead. The recipient gets the original quality, and nothing about the file has to change first.

The same goes for ProRes or camera raw footage. It runs many times the size of delivery H.264 for the same shot, which is the wrong direction, and most people's players cannot open it anyway. Convert it to MP4 with MOV to MP4 first if it needs to travel, or send the link if it needs to stay untouched for editing.

Common questions

Does converting MOV to MP4 lose quality?

Not if the codec inside is already one that MP4 supports, which our container test above confirms: the stream is copied, not re-encoded. It only loses quality once you set Resolution, Bitrate or Frame rate, because those force a real re-encode, the same kind of generation loss covered in lossy vs lossless compression.

Can I trim a video before converting it in FileFlip?

No. FileFlip has Resolution, Bitrate and Frame rate controls but no cut or trim tool. Shorten the clip in your phone's editor or Photos before you convert it.

What's a typical bitrate for phone video?

Apple does not publish exact encoder bitrates, but third-party measurements put an iPhone's default High Efficiency setting at roughly 170 MB per minute for 4K at 30 fps and around 400 MB per minute at 4K 60 fps, dropping to about 65 MB per minute at 1080p 30 fps, per MacRumors' storage guide. That is 20 to 30 times what fits in a 25 MB email.

Convert between them

FileFlip converts MOV, AVI, MKV and WebM to MP4 entirely in your browser. Nothing uploads, there is no account, and the Advanced options panel is where Resolution, Bitrate and Frame rate live. The video converter covers every other format pair if yours isn't one of these four.

How we measured this

• Source clip: a 10-second, 1920x1080, 30 fps H.264 segment of Big Buck Bunny (Blender Foundation, CC BY 3.0) at roughly 24.5 Mbps, from test-videos.co.uk's sample library. The 3-minute clip used for the size and zip tests loops this segment and pairs it with 3 minutes of the film's own soundtrack, extracted from the Internet Archive's Big Buck Bunny encode. One clip is a single data point; content with more motion or detail will compress differently.
• Tools: FFmpeg 8.1.2 with libx264, libx265, libvpx-vp9, aac and libvmaf, run from the command line. -c copy for the remux tests, libx264 -b:v <target> -maxrate <target> and -r 30/-r 60 for the bitrate and frame-rate grid, and the libvmaf filter, scaling both streams to 1920x1080 before comparing, for the quality table. The 3-minute test file was encoded the same way at 480p and 1080p, 1 Mbps video, 96 kbps AAC audio; the 480p result is the one quoted in the durations table, which extends the other four bitrate presets by the same bits-per-second math rather than a separate encode for each.
• Zip: the standard zip command-line tool on macOS.
• Reproducing it: node apps/nextjs/scripts/benchmark-video-encoders.mjs <clip> prints the container, size and VMAF tables above. node apps/nextjs/scripts/fetch-corpora.mjs downloads the clip.
• Caveat: VMAF and file-size figures both come from one animated source, encoded with libx264's default rate control. A live-action clip with more fine detail, or a different encoder, will land at different absolute numbers, though the size-tracks-bitrate-not-resolution relationship follows directly from how a target-bitrate encoder works and should hold regardless of content.