How to Send a Video File That's Too Large for Email

The quickest way to send a video that's too large for email is to stop attaching it. Upload the file to a secure transfer service and email the download link instead. Every major email provider caps message size somewhere between 20 MB and 35 MB.
Attaching still works for short, low resolution clips. Anything shot on a recent phone or exported from an editor will bounce, so the practical answer to how to send a video through email is a delivery method that keeps the file out of the message.
Below are the real limits for each provider, why a file that looks small enough still fails, and the fastest way to get a large video to a client without a failed delivery.

Email Attachment Size Limits for Gmail, Outlook and iCloud

Every provider measures the entire message, not the individual file. That ceiling covers your video, the message body, inline images and everything else attached to the same email.

Personal Gmail allows 25 MB of attachments per message. Microsoft 365 defaults to 35 MB for sending. Outlook desktop running a standard internet account stops at 20 MB unless the registry value is changed. Google's attachment guidance for Gmail also confirms what happens above the cap, which is that Gmail strips the file out and inserts a Drive link on your behalf.

One minute of 4K phone footage runs to hundreds of megabytes before you've trimmed a frame. A two minute client review cut is already twenty times the Gmail ceiling, which is why compression rarely rescues a video file on its own.

How to Send a Video Through Email Without Hitting the Size Limit

Upload the video to a file transfer platform, then paste the secure link into your email. Your message stays small, the recipient downloads at full quality, and nothing depends on the receiving server's attachment rules.

• Export at delivery quality first. Decide the final resolution and codec before uploading, because re-exporting after you've sent the link means sending a second one.
• Upload to a transfer service. Use a secure file transfer tool that delivers by email or link. Free transfers here run up to 10GB, which covers most single video exports.
• Set an expiry and a password on sensitive work. Anything under client confidentiality or NDA should not sit on an open link indefinitely.
• Send the link in a plain email. No attachment, no zip, no inline preview. One sentence of context and the link.
• Check the download confirmation. Delivery alerts tell you the file actually arrived, which beats chasing a reply three days later.

That whole sequence takes about as long as attaching the file would have, and it works regardless of what mail client the recipient uses.

Why Video Files Fail to Send Even When They Look Small Enough

Two things make the published limit misleading. Email encodes attachments before sending, which inflates them by roughly a third, and the receiving mail server applies its own cap on top of yours.

A 20 MB video travels as around 27 MB once encoded. Send that to a mailbox that accepts 25 MB and it bounces, even though the file on your desktop looked comfortably under the line.

How Base64 Encoding Inflates Video File Size

Email cannot carry raw binary data, so attachments are converted to Base64 text, which turns every three bytes into four characters. That's a fixed overhead of about 33% on top of the original file, applied to every attachment in the message.

The practical rule follows from the arithmetic. If your ceiling is 25 MB, keep the actual file under roughly 18 MB. If your ceiling is 20 MB, keep it under 15 MB.

Why the Recipient's Mail Server Decides What Arrives

The lower of the two limits always wins. You might be able to send 35 MB, but if the recipient's mail gateway rejects anything over 10 MB, the message never lands and the bounce notice often arrives hours later.

This is common in regulated organisations, where legal, financial and healthcare mail gateways are deliberately tightened. Microsoft's own Exchange Online message size limits show how far an administrator can move those defaults in either direction, so you have no reliable way to guess what the other side accepts.

When Compressing a Video Is Worth It Before Emailing

Compression only helps when you're already close to the limit. Shaving a 30 MB file to 18 MB is realistic. Getting a 2 GB export under 25 MB means destroying it.

Compression is worth trying when:

• The file is within about 50% of the cap and the recipient just needs to review, not archive.
• You're still on an older codec and can re-encode to HEVC at the same visual quality.
• The clip is longer than it needs to be and can be trimmed to the section that matters.

Skip it when the video is a final deliverable, a colour-graded master, or anything a client will republish. Squeezing a paid deliverable through a size cap costs you the quality the client is paying for, and they will notice it on a large screen.

Choosing Between Cloud Storage Links and Secure Transfer Links

Storage links and transfer links solve different problems. Cloud storage is built for files you keep and manage over time. A transfer link is built for one-off delivery of a finished file, which is what a video handover usually is.

The difference shows up in three places:

• Recipient friction. Drive and OneDrive links often prompt for an account or a permission request. Transfer links generally download without any sign-in.
• Permissions drift. A storage link stays live until someone remembers to revoke it. A transfer link expires on a date you set.
• Visibility. Storage tells you a file exists. Delivery tools tell you who downloaded it and when, which matters when a client claims they never received the cut.

Apple's Mail Drop limits sit somewhere in between, handling up to 5 GB with automatic expiry after 30 days, though it only works from Apple Mail and iCloud Mail.

For files beyond the free tier on most transfer platforms, higher transfer limits on paid plans are usually cheaper than splitting a master into parts.

5 Mistakes to Avoid When Sending Large Video Files by Email

1. Splitting the video across multiple emails. Multi-part archives fail constantly, get quarantined by security filters, and put the burden of reassembly on your client.

2. Sending the password in the same email as the link. It removes the protection entirely. Separate the two, and if you handle sensitive footage regularly, it's worth reading how to share password protected files properly before your next handover.

3. Assuming the file went because nothing bounced. Some gateways silently quarantine oversized messages. No bounce is not confirmation of delivery.

4. Uploading to personal cloud storage. Client work sitting in a personal Drive account creates a data protection problem that nobody wants to explain during an audit, particularly where EU data residency matters to the client.

5. Leaving links live forever. A link with no expiry is an open door to a finished deliverable, months after the project closed.

Sending video by email stopped being an attachment problem years ago. It's a delivery problem, and the fix is the same whether the file is 50 MB or 50 GB. Upload the video once, send a secure link with an expiry set, and let the download confirmation tell you it landed.