We’ve all been in that situation. You attach a video, press send, and the email won’t go. Gmail offers to put it in Drive instead. Outlook says the attachment is too large. Or worse: it sends, and bounces back an hour later because the other end refused it. When this happens, you are often left clambering for the nearest tool to hand, or if you’re not in possession of one, you have to find one fast.
Video is almost always the filetype where people run into this kind of issue. A minute of video from a modern phone is comfortably over 100 MB, and email was never built to carry it. But what are the limits and how do different email providers deal with them?
Here’s what the limits actually are, and the three ways round them.
Why a 20 MB video won’t fit a 25 MB limit
Attachments aren’t sent as they are. Email encodes them as text for transit, which makes them roughly 37% bigger on the way. A 20 MB video can be counted as about 27 MB by the time it’s measured, which is how a file that looks safely under the limit can get refused… not necessarily by the sender, but by the receiver.
Providers differ on where they measure, so the safe size isn’t the same everywhere:
| Sending from | Its limit | Aim for |
|---|---|---|
| Gmail | 25 MB of attachments, counted as the files are | 25 MB |
| Outlook.com, Yahoo | 20–25 MB a message, possibly counted after encoding | 18 MB |
| The Outlook app | 20 MB a message | 14 MB |
| Work email (Exchange) | often 10 MB a message | 7 MB |
Every other platform’s limits (Discord, WhatsApp, Instagram, YouTube and the rest) are on our video size limits page, with what each one does to your video after it arrives. We update this every 2 weeks, so you can be sure that the information is up to date and accurate.
Of all the email providers, gmail is the generous one: we tested it in September 2026 and 25 MB of video went as real attachments, not a Drive link, so its 25 MB is 25 MB of file. The others keep a margin because their limit may be the encoded size.
And the limit that matters is the smaller of two. Yours decides whether the message leaves; the recipient’s decides whether it arrives. A 24 MB video sent happily from Gmail can bounce off a work server that stops at 10 MB. If you don’t know where it’s going it’s best to aim lower.
The quick fix: make the video smaller
Most videos are far bigger than they need to be. Phones record at a bitrate meant for editing, not for sending, and a clip can usually lose 90% of its size before anyone can see the difference on the screen it’ll be watched on.
- Open Compress video for email.
- Choose your video, or drop it on the page. One video, or several you want to send together.
- Pick who you’re sending from. Gmail, Outlook.com or Yahoo, the Outlook app, or a work account. The size to hit is set for you.
- Press Export, and save the file when it’s done.
- Attach it to your email as usual.
The processing and exporting all happens on your own device in the browser. Your video isn’t sent anywhere, there’s no account, nothing is watermarked, and the file you get back is an MP4 that plays on any phone, computer or webmail preview.
Two things worth knowing about the result:
- It will never be over the limit. The size you pick is a ceiling, not a target.
- It often comes in well under size. A short clip that doesn’t need the whole allowance doesn’t get padded out to fill it: a ten-second video for email typically lands around 8 MB rather than 18. Smaller file, same picture.
Sending several videos at once
If you’re sending multiple clips on Gmail (where the limit is 25MB) then it’s not enough for each video to be under 25MB. The combined total has to fit under 25MB. In the compress for email tool, choose them all together and select the option “all in one email”, and the allowance is shared out between them: each video gets a share based on how much picture it actually has. Anything already small enough is left alone, and whatever one video doesn’t use goes to the ones still to be made. Three videos totalling 43 MB came to 17.79 MB in one email when we tested it.
If it has to stay full quality: send a link
Sometimes the video can’t be compressed. A client needs the original, or it’s going into an edit. In these situations, don’t use email at all. The best option is to use cloud storage - put it in Google Drive, Dropbox or OneDrive and send a link. Gmail offers to do this for you if you go over 25 MB, but bear in mind that for large amounts of storage there is a fee to pay with Google drive.
Be aware of what that costs: the file is uploaded to a server, the wait is on your connection rather than your computer, links expire or get revoked, and the recipient has to click through and download it rather than just watching it in the message. For anything confidential for example client work, interviews, anything with people in it who didn’t agree to be on a third-party server, think about whether it needs to go there at all.
If the video is long, consider trimming it first
One option to consider to save on file space is trimming the clip down. Most videos that are too big to email are too long to watch, too!
Trimming it cuts the start and end without re-encoding, so the part you keep is bit-for-bit the original quality, and it’s instant. A one-minute cut from a five-minute video is a fifth of the size before you’ve compressed anything. Trim first, then compress what’s left if it’s still too big.
Things that don’t work
- Zipping it. The video is already compressed. A zip of an MP4 saves you a percent or two, and now the recipient has to unzip it. The only benefit here is keeping multiple files in neat single folder download.
- Splitting it into parts. Some providers count the whole message, so several attachments hit the same wall. And now someone has to reassemble it.
- Sending it from your phone instead. Same limits, same server.
To conclude
Check the limits with which provider you are sending from, use tools to get the video under that number, and send it as a normal attachment. It arrives as a video in the message, which is what the person on the other end wanted. Not a link, not a download, and not a bounce.
