How to compress video for email without using google drive
- Step 1Drop the clip — Add an
MP4,MOV,MKV,WebM,AVI,M4V, orTS. A quick<video>probe reads the duration so the compressor can size the bitrate to land under the inline cap. - Step 2Pick the recipient's client — Set
Targetto GMAIL (24 MB) or OUTLOOK (19 MB) based on whoever you're sending to — or where the Drive/OneDrive swap keeps happening. If you don't know the recipient's client, OUTLOOK's smaller target is the safe choice for staying an attachment everywhere. - Step 3Run the compressor — Click Run Email Fit. JAD computes the bitrate, reserves 128 kbps for audio (96 kbps under 30 s), and encodes to MP4 entirely on your machine — no upload to Drive or anywhere else.
- Step 4Download the MP4 — The result card shows the before → after size. Download the under-cap file.
- Step 5Attach it directly — Drag the file into compose. Because it's under the inline cap, Gmail/Outlook keep it as an attachment instead of offering a link — the message is now fully self-contained.
- Step 6When a link is genuinely the right call — If the clip is long or quality is paramount, an attachment isn't ideal — 24 MB can't carry 10 minutes well. For those, a link is the better tool. This compressor is for the (common) case where you specifically want to avoid one.
Attachment vs Drive link — when each wins
The compressor exists for the left column. The right column is where a link is genuinely better.
| Situation | Attachment (this tool) | Drive / OneDrive link |
|---|---|---|
| Short clip in a thread | Best — plays inline, no click | Adds a click and a permissions risk |
| External / cold recipient | Best — no access request, no domain block | Often blocked or looks like phishing |
| Archived for the long term | Best — lives in the message forever | Risk of a later 404 if the file is moved/deleted |
| Long clip / quality-critical | Limited — 24 MB can't carry long footage well | Best — bypasses compression entirely |
What the targets do (no custom field)
Two presets, both keeping the file an attachment. There is no per-MB control.
| Target | Internal byte target | Keeps it an attachment for |
|---|---|---|
| GMAIL | 24 MB | Gmail (under the 25 MB Drive-swap threshold) |
| OUTLOOK | 19 MB | Outlook.com (under 20 MB) — and a safe choice for any client |
| Smaller cap needed | use a sibling | whatsapp-compressor 15 MB · discord-compressor 25/50 MB |
Cookbook
Real 'I want it as an attachment, not a link' situations and how the targets handle them. Sizes approximate.
Gmail kept swapping in a Drive link
A 50-second 1080p clip at 52 MB triggered Gmail's Drive-link insertion every time. Compressing to GMAIL keeps it a true attachment.
Before: drag 52 MB clip -> Gmail inserts a Drive link Target: GMAIL (24 MB) Output: clip.mp4 · ~23 MB After: drag the 23 MB file -> stays an attachment, plays inline
Cold outreach where a Drive link looks like phishing
Sending a product demo to a prospect outside your org — a Drive link from an unknown sender often gets ignored or flagged. An inline MP4 just plays.
Audience: external prospect, no shared domain Link risk: 'request access' or spam-filtered Fix: email-compressor (OUTLOOK, 19 MB) -> attach demo.mp4 Result: prospect sees the demo in-thread, no sign-in
Recipient on Outlook got an access-denied OneDrive link
A OneDrive link shared with default org-only permissions denied an external recipient. The fix is to not use a link at all.
Before: OneDrive link -> recipient gets 'access denied' Target: OUTLOOK (19 MB) Output: walkthrough.mp4 · ~18 MB After: real attachment, no permissions, no link
Privacy: keep the clip off Google entirely
For a sensitive internal recording, you don't want it sitting in Drive even briefly. The encode is local, so nothing is uploaded to Google.
Goal: clip must never touch Drive / a server Path: WebCodecs HW H.264 in the browser (no upload) Output: internal-clip.mp4 · ~23 MB attached directly Result: zero copies on Google's servers
When a link really is the right answer
A 12-minute training video can't be a good 24 MB attachment. Here a link wins — the honest recommendation.
Input: training.mp4 · 12 min
24 MB attachment -> 200 kbps floor -> blocky, unwatchable
Better: share via a link, OR
trim to the key 90 s with lossless-trimmer, then attach
Lesson: attachments shine for SHORT clipsEdge cases and what actually happens
Gmail still inserted a Drive link
Over the targetGmail only swaps in a Drive link when the file is over 25 MB. If it still did after compressing, the output landed over the cap (a short, busy clip can overshoot the 24 MB target). Re-run with the OUTLOOK target for more headroom, or trim a few seconds with the lossless trimmer.
Recipient's mailbox cap is below 19 MB
Provider-sideAn attachment only stays an attachment if it clears the recipient's inbound cap too. If they're on a corporate Exchange limited to 10 MB, even a 19 MB file may bounce. Trim the clip shorter and re-run to get under their limit.
You actually want it streamable, not downloaded
Use a linkAn attachment downloads to the recipient's device; a link streams. For long content or where you want play-without-download, a link is the right tool. This compressor is specifically for keeping short clips as inline attachments.
Output overshot the target slightly
Soft overshootThe compressor solves a bitrate rather than guaranteeing a byte count, so a motion-heavy short clip can land just over. It still hands you the file with a warning. If it's over the cap, the OUTLOOK target or a quick trim fixes it.
HEVC clip downloads as a blob instead of previewing
Fixed by re-encodeSome clients won't preview HEVC inline and force a download — which defeats the 'plays in the thread' goal. Because the output is always H.264 MP4, the compressed file previews inline rather than downloading as an opaque blob.
Long clip can't be a good attachment
Quality limitAt 24 MB, anything past ~10 minutes hits the 200 kbps video floor and looks bad. The 'no Drive' goal conflicts with long footage; either trim to the part that matters or accept that a link is the better medium for that clip.
On mobile with a large source
Mobile capWithout hardware encode, the FFmpeg.wasm fallback on mobile won't take sources over 80 MB and asks you to trim or move to desktop. It also downscales above-720p sources to 720p to fit the phone's memory.
Already under the cap
No link neededIf your clip is already under 25 MB (Gmail) or 20 MB (Outlook), it'll attach without a link as-is — you don't need to compress. The tool will still re-encode it smaller if you run it.
Frequently asked questions
How do I stop Gmail turning my video into a Drive link?
Gmail inserts a Drive link only when the attachment exceeds 25 MB. Compress the clip to the GMAIL target (24 MB) first and Gmail keeps it as a real inline attachment instead of offering the link.
Why avoid a Drive link at all?
Links can trigger 'request access' walls, get blocked for recipients outside your domain, look like phishing in cold outreach, and 404 later if the file is moved or deleted. An attachment lives inside the message — viewable forever, no permissions.
Does the video get uploaded to Drive or a server during compression?
No. The encode runs entirely in your browser via WebCodecs or FFmpeg.wasm. The clip never touches Google's servers or any JAD server, so there's no copy in the cloud to manage.
What size will the attachment be?
About 24 MB on the GMAIL target, or about 19 MB on OUTLOOK — each a megabyte under the client's inline cap so it stays an attachment rather than a link.
The recipient is on Outlook — will the attachment work for them?
Yes, as long as it's under their inbound cap. Use the OUTLOOK target (19 MB). If their corporate mailbox is limited lower (e.g. 10 MB), trim the clip first so it clears their limit.
Can I choose an exact size to guarantee it stays an attachment?
There's no custom MB field — only GMAIL (24 MB) and OUTLOOK (19 MB). For a smaller guaranteed size, trim the clip first, or use whatsapp-compressor (15 MB).
Will the recipient be able to play it in the email?
Yes — the output is H.264 MP4, which Gmail and Outlook preview inline. They click play in the thread; no download or sign-in required.
When should I use a link instead?
For long videos or quality-critical content. A 24 MB attachment can't carry 10+ minutes well. If the clip is short, the attachment route this tool enables is the better experience.
What input formats are supported?
MP4, MOV, MKV, WebM, AVI, M4V, and TS. The output is always an email-friendly H.264 MP4.
It still became a Drive link after compressing — why?
The output landed over 25 MB (short busy clips can overshoot the 24 MB target). Re-run with OUTLOOK (19 MB) for more headroom, or trim a couple of seconds with the lossless trimmer and try again.
How big a file can I compress?
On the free tier, sources up to 1 GB, one at a time. The only hard reject is on mobile without hardware encode, where the FFmpeg.wasm fallback won't accept sources over 80 MB.
Can I script this so it never uploads?
Yes. Pair the @jadapps/runner and POST to http://127.0.0.1:9789/v1/tools/email-compressor/run (schema at GET /api/v1/tools/email-compressor). It runs locally — no Drive, no upload, in a pipeline.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.