How to compress video for email and messaging

Video attachments can exceed an email or chat app's limit even when the clip is short. Check the current limit for your account and sending method, then choose a smaller size target or share a link. Compression trades quality for size; it does not guarantee that every clip will fit or remain equally sharp.

Check the attachment limit

Gmail's attachment guidance lists 25 MB for personal accounts; work and school limits are administrator-controlled. The limit applies to the total attachments, not just the video. Other providers and chat apps can vary by plan, account, and whether you send media or a document, so use their current instructions rather than a fixed cross-platform table.

Motionix targets are in MiB, while a provider may state a decimal MB ceiling. 1 MiB = 1,048,576 bytes; 1 decimal MB = 1,000,000 bytes. Thus 25 MiB = 26,214,400 bytes, which is over a decimal 25 MB ceiling. A custom 20 MiB target is 20,971,520 bytes, leaving some room below that ceiling for other attachments. Verify the actual exported byte count and the provider's handling of message overhead.

Compress for messaging apps

Check the app's current limit for the exact sending method. Media messages may be re-encoded, and sending as a document may behave differently; neither route guarantees unchanged playback or quality.

• Start from the original rather than repeatedly compressing previous exports.
• Choose a target below the stated ceiling, accounting for MB versus MiB.
• Preview the file on a recipient-compatible device before sharing.
• A cloud-drive link can avoid recompression, but check access permissions and upload privacy first.

How video compression works

Video compression removes redundant data:

• Temporal compression. Stores many frames as differences from other frames, alongside independent keyframes.
• Spatial compression. Encodes patterns within a frame; lossy settings can remove visible detail.
• Audio compression. Lower audio bitrate saves space but can affect voice or music quality.

Choosing an output: MP4 or WebM

The container holds the video and audio tracks; codecs determine how those tracks are encoded. Video Compressor offers these output choices, subject to browser encoder availability:

Being able to play an input does not guarantee that the browser can encode the chosen output. MDN's WebCodecs API reference explains that devices and browsers support different codec subsets. The tool reports unavailable decoders or encoders; try Automatic, WebM, smaller dimensions, or another current browser. H.265 and AV1 are not selectable output codecs here, and no format plays on every device.

Target bitrate and resolution

File size is driven by bitrate, not resolution alone. A rough rule:

• Total bitrate (kbps) ≈ target size (decimal MB) × 8000 ÷ clip length (seconds).
• For MiB targets, use approximately 8389 instead of 8000.

For example, 14 decimal MB over 60 seconds allows roughly 1,867 kbps total before container overhead. Audio and overhead need part of that budget. This is arithmetic, not a measured tool result; the compressor reserves headroom and checks the actual output size.

These are rough starting examples, not quality guarantees or bitrate controls exposed by this tool. The same bitrate can look very different on a static talking head and fast-moving footage.

Two more knobs:

• Resolution. A smaller frame can help preserve readable detail within a tight bitrate budget, but reduces output dimensions. Motionix's 720p and 1080p choices cap the longest edge at 1280 and 1920 px while preserving aspect ratio; they are not fixed dimensions for every orientation.
• Frame rate. Motionix outputs up to 30 fps. Higher-frame-rate input may lose motion smoothness; this does not imply a fixed percentage saving. There is no separate frame-rate slider.

Step-by-step compression

1. Check the original file size. Right-click → Properties (Windows) or Get Info (Mac).
2. Open Video Compressor. It reads MP4, MOV, WebM, or MKV when the browser can decode their tracks, within its stated limits: 200 MiB, 10 minutes, and up to 4096 px per side with a pixel-count cap. Those limits do not guarantee enough device memory.
3. Set a size target. Choose a preset or Custom in MiB. Convert any decimal provider ceiling to bytes and leave room below it. The 2 Mbps option has no size target and may produce a larger file.
4. Choose dimensions and output format. Select a maximum edge and MP4, WebM, or Automatic. Original dimensions remain subject to the tool's limits; the tool does not upscale.
5. Decide whether to keep sound. Audio is retained by default. Check Remove audio only if you want a silent result; unavailable audio support is reported, not silently discarded.
6. Compress, inspect, and download. Review the measured bytes, dimensions, duration, format, and audio state, then play the result before attaching it. Processing time varies by clip, browser, and hardware.

A target is a maximum, not an exact size or a success promise. If the budget is too small or encoding exceeds it, the tool reports a failure rather than labeling an oversized file as compliant. Lower the resolution, choose a larger target only if the destination allows it, or trim the original in a separate editor. Cancel, choose another file, or reset if you need to recover from an error.

Quality settings

If the email only needs a few seconds of silent motion, compare the GIF workflow with keeping the clip as MP4. A GIF is not automatically smaller. For the repeated logo or portrait below your message, use the separate email signature image-size guide.

There is no High/Medium/Low quality slider in this workflow. The size target, clip duration, dimensions, and retained audio determine the encoding budget. Re-encoding is lossy; keep the original for archiving and compare fine text, faces, and motion in the output.

What gets sacrificed

• Resolution. Lowering a 4K source to a smaller frame removes pixel detail; actual file savings depend on the encoding budget.
• Bitrate. Lower bitrate = smaller file, but more compression artifacts.
• Audio. Retained audio is re-encoded; choosing Remove audio makes the clip silent rather than merely quieter or lower quality.
• Frame rate. Input above 30 fps can lose frames in the output.
• Extra tracks and metadata. Only the primary video and audio tracks are used; subtitles, alternate tracks, and descriptive metadata are not an archival preservation promise.

Common mistakes

• Expecting every re-encode to shrink. Similar or higher bitrate can produce a file as large as, or larger than, the original.
• Over-compressing. Tight budgets can make text unreadable or motion blocky; inspect the content rather than assuming a universal quality threshold.
• Not checking the result. Always preview before sending.

Frequently Asked Questions

Why is my video still too big after compressing?

The no-size-target option can produce a larger file, and a preset in MiB may exceed a provider's decimal MB ceiling. Use Custom with an appropriate byte budget and a lower resolution cap, then inspect the measured output. If the target cannot be met, the tool reports an error; trim elsewhere or use a sharing link rather than assuming another attempt must succeed.

What is the best video format to send by email?

MP4 with H.264 and AAC is a broadly supported choice when the browser can encode it. WebM is an alternative if both your encoder and recipient support it. A mail client may require downloading the attachment to play it, and no codec is universal.

How do I compress a video for WhatsApp without wrecking the quality?

Check WhatsApp's current limit for media versus document sending, then choose a target below it and preview a lower-resolution export. The app may re-encode media; document sending is not a blanket guarantee of unchanged quality. Share the original through an appropriate file link if preserving it matters more than attachment size.

Should I use H.265 (HEVC) just to make files smaller?

Only use it in a separate encoder when you know the recipient can play it. Savings depend on content and encoder settings, not a fixed percentage. Motionix's output choices are MP4 with H.264 or WebM with VP9/VP8, not H.265.

Is it safe to compress video in the browser?

Motionix performs this compression on your device and provides a local file download. That does not mean every browser tool is local, the page works offline, or all data stays only in RAM. Site requests can still use the network; the separate cloud-upload action sends the selected result if you choose it. Attaching the file to an email also uploads it to your mail service. Review privacy and storage policies for sensitive footage.

Related guides

• Video formats compared: MP4, MOV, WebM — pick the right container and codec
• WebCodecs vs FFmpeg.wasm — how in-browser video processing works
• Make a GIF from a video — when a short loop beats a heavy clip

Related tools

• Video Compressor — target specific file sizes, runs in browser
• GIF Maker: turn a short silent clip into a loop; compare its size and quality rather than assuming it is smaller