Video Too Big for Email or WhatsApp? Size Limits and How to Beat Them
tldr:
- “Gmail’s 25 MB applies to the base64-inflated wire size — keep actual video files under ~18-19 MB.”
- “WhatsApp re-encodes videos sent as videos; send as a Document to skip their encoder entirely.”
- “Formula for any size target: Mbps = target MB × 8 ÷ seconds.”
- “Pre-compress on-device so you control quality — not the platform’s encoder.” faq:
- q: “How do I send a video through email if it’s too big?” a: “Compress it to fit: a 1-minute clip at ~2 Mbps 1080p lands around 15 MB, under Gmail’s effective limit. Longer clips need 720p or a cloud link — email genuinely only suits clips under about 2 minutes.”
- q: “What’s the video size limit for WhatsApp?” a: “Documents up to 2 GB. Videos sent through the video picker get re-encoded by WhatsApp regardless of size — their compressor decides the quality. Send as a document to preserve your exact encode.”
- q: “How big can an iMessage video be?” a: “Around 100 MB before iMessage degrades it to a low-quality clip. Compress under that threshold to send your own encode, not Apple’s.”
- q: “How do I calculate what bitrate fits a size limit?” a: “Bitrate (Mbps) = target size (MB) × 8 ÷ duration (seconds). For 25 MB in 60 seconds: 25 × 8 ÷ 60 ≈ 3.3 Mbps. Kompress shows the estimated output size before you compress.”
You compressed your video, attached it, hit send — and the app refused. Every platform has its own size limit, and 4K phone footage blows through all of them. Here’s the complete map of attachment limits, why they exist, and how to actually get your video through.
The size limits, platform by platform
| Platform | Limit for video | What happens when you exceed it |
|---|---|---|
| Gmail (incoming) | 25 MB | Attachment refused |
| Gmail (outgoing, with Drive link) | Larger via link | Works, but the recipient needs a Google click-through |
| Outlook/Exchange | 10–20 MB (server-dependent) | Bounce-back email |
| Apple Mail (iCloud) | ~20 MB | Send fails or falls back to a Mail Drop link |
| WhatsApp (documents) | 2 GB | Fine — but the recipient downloads the full file |
| WhatsApp (as video) | No hard limit — WhatsApp re-encodes it | Your quality is destroyed by their compressor |
| Telegram | 2 GB (4 GB premium) | Fine, but slow to upload |
| iMessage | ~100 MB | Sends as a low-quality clip if larger |
| Instagram Feed | ~15 minutes, but re-encoded | Their compressor decides your quality |
| Discord | 10 MB free / 500 MB Nitro | Upload refused |
Two lessons hide in this table:
- 25 MB is the de facto email standard. Base64 encoding inflates attachments by ~33%, so a video file must be under ~18–19 MB actual size to reliably clear Gmail’s 25 MB wire limit.
- Messaging apps that “accept” big videos re-encode them anyway. WhatsApp and Instagram run your upload through their compressor with their settings. If you send a 700 MB 4K clip, you don’t get to decide what it looks like — their server does.
The right fix: compress before you send
Compressing before sending solves three problems at once:
- The file fits under the limit.
- You control the quality, not a server.
- Upload is faster (and cheaper on cellular).
For email: target ~15 MB
Email attachments need the base64 safety margin. Aim for ~15 MB:
- A 1-minute clip: 1080p at ~2 Mbps ≈ 15 MB ✔
- A 3-minute clip: 720p at ~0.6 Mbps, or trim the clip — email genuinely wasn’t built for video.
For WhatsApp-as-video: beat their compressor
When you send a video as a video (not a document), WhatsApp re-encodes it — historically to aggressive, blocky settings. Two strategies:
- Send it as a document. WhatsApp skips its video re-encoding for documents, so your file arrives with your quality. Compress to a sensible 30–100 MB first.
- Pre-compress to a size their compressor respects. If it’s already lean (say 20 MB for a minute), WhatsApp’s re-encode has less to destroy.
For iMessage: stay under 100 MB
iMessage will send larger video as a degraded clip. Compress to <100 MB and you send your encode, not Apple’s.
Doing it on the phone, in under a minute
The scenario is always the same: you have the video on your phone, and you want to send it from your phone. Uploading to a web compressor, downloading back, and then attaching is a slow, privacy-leaking detour — if the site even accepts a 500 MB file on mobile data.
Kompress runs the compression where the video already is:
- Pick the video from your gallery.
- Choose a preset. For messaging, the Good preset (HD) covers nearly every app; for email, go to Small or Advanced and dial the bitrate until the estimate fits your target. The app estimates the output size before compressing, so you don’t play guessing games.
- Share straight from the result screen. Kompress hands the compressed file to the share sheet — WhatsApp, Mail, Telegram — without a round trip.
The whole flow is: pick → preset → share. Under a minute, on cellular, with nothing uploaded to anyone’s server. (Full walk-throughs: iPhone · Android.)
What about cloud links?
Gmail offers to attach big files as Google Drive links; Apple Mail has Mail Drop. Links work — but:
- The recipient needs to click through to another service (and sometimes sign in).
- Videos in cloud links get streamed at whatever quality the player picks, or re-encoded on upload (Google Photos will happily re-encode for you).
- The file is now on a third party’s servers with a share URL.
A compressed attachment is direct, plays offline, and keeps exactly the quality you chose. When it fits — and with 15–20 MB of well-compressed video, a lot fits — it’s the better experience.
The general recipe
- Know the limit (table above).
- Match bitrate to duration: MB target × 8 ÷ seconds = Mbps. For 20 MB in 60 s: 20 × 8 / 60 ≈ 2.7 Mbps.
- Compress on-device, share from the result.
- Save the original — never send your only copy anywhere.
Kompress is on the App Store and Google Play — no upload, no account; first run free, then Kompress Pro. Same video, smaller file, sent.