How to Compress Video for Email (Gmail and Outlook 25 MB Limit)

The 25 MB wall that kills video in email

You record a screen demo or a product clip, hit attach in Gmail, and get bounced: the file is too big to send. Gmail caps attachments at 25 MB, Outlook.com caps them at 20 MB, and a 60-second 1080p screen recording is often 80 to 150 MB. If you send video through email as part of a sales or marketing pipeline, that wall breaks the whole flow.

The usual fix is to open a desktop tool, drag the file in, wait, and re-upload. That works once. It does not work when a Zapier or n8n workflow needs to compress every new recording before it goes out.

Why the limit exists and what actually counts against it

Gmail's 25 MB ceiling is the total size of the message, including all attachments and their encoding overhead. Because email attachments are Base64-encoded, they inflate by roughly 33% in transit. So a file that shows as 24 MB on disk can push the message past 25 MB and bounce. Aim for about 18 to 20 MB of actual video to stay safe.

Each major provider draws the line differently:

Google Drive and OneDrive links are the escape hatch, but links get lower open rates in cold outreach, land in spam filters more often, and add a click. For a demo you want a prospect to actually watch, an inline or attached clip under the limit converts better. Compression is the real answer.

Compress video for email: the manual way vs the API way

The generic advice you find ranking for this query is "use HandBrake" or "use Clipchamp." Both are fine desktop tools. Neither fits an automation.

The manual way (HandBrake, Clipchamp, VLC):

Every step is a human sitting at a laptop. It doesn't scale to a marketing team sending dozens of clips a week, and it can't run inside an automated sequence.

The API way (one call inside your pipeline):

You send the video to a compression endpoint, get back a smaller file, and attach it, all without a server or an FFmpeg install. FFmpeg Micro exposes exactly this as the FFmpeg API: submit a job, poll or receive a webhook, download the output.

curl -X POST https://api.ffmpeg-micro.com/jobs \
  -H "Authorization: Bearer $FFMPEG_MICRO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input": "https://files.example.com/demo.mov",
    "operation": "transcode",
    "options": {
      "codec": "h264",
      "crf": 28,
      "max_width": 1280
    }
  }'

The parameters that matter for email are the codec, the quality target, and the resolution. See the docs for the exact request shape. The concepts below carry over whether you call it from code or from a no-code tool.

The three levers that shrink a video

Combine a CRF of 28 with a 720p downscale and most 1080p clips land under 20 MB without looking rough. If you need a hard size ceiling, two-pass encoding to a target bitrate is the reliable route, since CRF alone doesn't guarantee an exact output size. The same idea drives optimizing videos for the web: pick the quality you can live with, then let the encoder hit it.

Automate video compression before send in Zapier, n8n, or Make

This is where the API earns its keep. Because FFmpeg Micro works with n8n, Make, and Zapier, you can drop a compression step into an existing email workflow.

A content-repurposing or outreach flow looks like this:

No one opens HandBrake. Every video that enters the pipeline comes out under the limit, ready to attach. If you'd rather test the compression before wiring the whole thing up, the free tier lets you run a job and see the output size first.

Running this browser-side with something like ffmpeg.wasm hits a wall on larger files, which is where browser-side FFmpeg breaks and why a hosted job queue handles a 150 MB source without freezing a tab.

Common pitfalls when compressing for email

FAQ

What's the largest video I can attach in Gmail?

25 MB total per message. Anything larger triggers a Google Drive link instead of a true attachment. Target about 18 to 20 MB of video to leave room for Base64 encoding overhead.

Does compressing ruin the quality?

Not at the settings above. A CRF around 28 at 720p is visually clean for screen recordings and talking-head clips watched in an email preview. You lose quality you wouldn't notice at that viewing size.

Can I compress video for email without installing anything?

Yes. That's the point of an API. You call an endpoint with the file and get a smaller one back, so there's no HandBrake install, no FFmpeg binary, and no server to run. It works from code or from n8n, Make, and Zapier.

Why not just send a Google Drive or OneDrive link?

You can, and for very large files you should. But links get lower open rates in cold outreach and land in spam more often. For a demo you want watched, a compressed attachment under the limit performs better.

If your outreach or content pipeline keeps hitting the 25 MB wall, wire a single compression step in front of your Gmail or Outlook send and stop babysitting exports. Try a job free to see the output size on your own clip, then sign up when you're ready to automate it.