How To Send A Large Video Through Email
Learn how to send a large video through email using links, permissions, and compression. Avoid size limits, bounces, and access issues with clear wording.
How to send a large video through email (without bounced messages or awkward follow ups)
Most email providers limit attachments to about 20 to 25 MB per message. Large videos usually exceed that limit. Sending a link is the standard approach for videos over the attachment cap.
The mistake I see most often is not the file size. It is the assumption that “attached” means “received.” I have watched a 12 second clip (shot in 4K on an iPhone) trigger a bounce, then the sender resends it three times, then IT blocks their account for suspicious activity. Meanwhile the recipient is waiting, slightly annoyed, and nobody says it out loud.
So yes, you can send a large video through email. You just rarely do it as a raw attachment.
First, check the hidden limits that actually decide success
Before you touch compression settings, verify the constraints on both sides. The sender’s limit is only half the story.
- Attachment cap: Gmail and Outlook.com are typically around 25 MB. Some corporate Exchange environments are 10 MB. Some are 35 MB. It varies.
- Inbound filtering: Security tools sometimes quarantine messages with large attachments, even if they are under the cap.
- Recipient mailbox quota: I have seen attachments “deliver” but not download because the recipient’s mailbox is full.
- Mobile reality: A 200 MB file on cellular can be a non-starter, even if the recipient technically can download it.
Users should verify the recipient’s attachment policy before sending sensitive content or repeatedly resending large files.

The option that works most often: upload the video, email a link
If you work with clients, recruiters, editors, or anyone outside your company, links are the cleanest. They avoid attachment caps, reduce bounces, and give you one URL you can correct if you uploaded the wrong cut.
The part people skip is the link context. I routinely get emails that say: “Here’s the video” with a naked URL. No filename. No runtime. No instructions. That email ages badly the moment it gets forwarded.
What I send instead is closer to this (you can steal the phrasing):
Subject: Video file (2:14) for approval. Link expires Friday
Body:
Hi Maya,
Here’s the 2:14 MP4 (1080p). Download link: [link]
Password: 4827 (if prompted)
If you want a smaller version for mobile, tell me and I’ll send a compressed cut.
Thanks,
Name
Notice what it does. It predicts the questions. It reduces the “can you resend?” thread to near zero.
Choosing where to host the video (and what I have seen go wrong)
You have three common buckets: cloud storage, video platforms, and file transfer services. The “right” one depends on how the recipient will use it.
- Cloud storage (Google Drive, OneDrive, Dropbox): Good for download and revision control. The failure mode is permissions. The recipient clicks, sees “Request access,” and you lose a day.
- Unlisted video platforms (YouTube unlisted, Vimeo private): Good for streaming and fast review. The failure mode is corporate filters that block video sites, or reviewers who need the original file.
- File transfer services (WeTransfer, similar): Good for one time delivery. The failure mode is expiry. I have seen links die right before a deadline review call.
If you do not know what the recipient prefers, ask one simple question in your email: “Do you need a downloadable MP4, or is streaming fine?”
How to avoid the permissions trap (the most common real world failure)
I cannot count how many times I have heard: “I shared it, but they still can’t open it.” Usually the sender shared it to “Anyone in my organization,” which is useless for external recipients.
- Set sharing to Anyone with the link (or invite the recipient’s exact email address).
- Choose the minimum access level needed: Viewer for review, Editor only if they must upload changes.
- Open the link in an incognito or private window. Confirm you can view it while signed out.
- Label the file clearly: ProjectName_ReviewCut_v03_1080p.mp4. “final_final2.mp4” causes confusion in real workflows.
If you want to keep the thread polished (especially when you are sending to a client), an AI Email Generator can help you format the message cleanly and consistently. I still edit the output, but it saves me from retyping the same “runtime, resolution, password” checklist every time.

If you must attach the video: compress it the right way
Sometimes the recipient demands an attachment because their environment blocks external links. If that happens, compression is your only move. The trick is to reduce size without making it look like a 2007 webcam clip.
- Export 1080p instead of 4K for review. Most approvals do not need 4K.
- Use H.264 or H.265 in an MP4 container. These are widely compatible.
- Lower the bitrate. For talking head video, 6 to 10 Mbps at 1080p often looks fine. For fast motion, you may need more.
- Trim the dead time. I see 45 seconds of “camera starts recording” at the beginning more often than you would expect.
Then check the file size. If it is still over the limit, stop trying to force it. You will waste time and still bounce.
Splitting across multiple emails (only when you have no other choice)
Some people try to split a video file into parts and send multiple attachments. It works technically, but it is fragile. The recipient has to download every part and recombine them. If one message is quarantined, the whole thing fails.
If you do this anyway, be explicit:
Subject: Video attachment 1 of 3 (please download all parts)
Body:
Hi Sam,
Your system blocks external links, so I split the MP4 into three ZIP parts. Please download all three attachments and extract Part 1. It will rebuild the full file automatically.
Part 1 of 3 attached (23.6 MB). Parts 2 and 3 follow in separate emails.
Thanks,
Name
This is one of those moments where a Professional Email Writer style template matters. Confusion here leads to “I only got one file, is that all?” and you will be back in the thread explaining basics.
What I send when I want zero back and forth
When the stakes are high (legal review, executive approval, a candidate portfolio), I include a tiny “receipt checklist” so the recipient can confirm quickly without sounding fussy.
- Filename and version
- Runtime
- Viewing method (stream or download)
- Access notes (password, expiry, permissions)
- What feedback you need (approve, timestamped notes, or general reaction)
Here is an actual structure I have used that gets fast replies:
Subject: Review link. 1:08 product demo (v5)
Hi Jordan,
Video: ProductDemo_v5.mp4 (1:08, 1080p)
Link: [link]
Access: anyone with the link can view. No download needed unless you prefer it.
Could you confirm by EOD whether: (1) messaging is correct, (2) pacing feels right, (3) any changes needed before we export 4K.
Thank you,
Name
If you want help drafting messages like that quickly, the AI Email Writer on EmailAI.me is useful for generating a clean first pass, especially when you have to send the same kind of “video link + review request” email repeatedly. I still recommend you add the human details (who needs what by when), because that is what keeps the thread moving.
Quick troubleshooting (based on the problems people actually email me about)
- They say the link “doesn’t work”: Open it in a private window, then check permissions and expiry.
- They can view but cannot download: You set viewer-only or disabled downloads. Decide if they truly need the original.
- Video plays blurry: The platform is streaming a low quality preview. Ask them to select 1080p, or provide a download link.
- Email bounces: You are over the attachment cap or hitting an outbound policy limit. Switch to a link.
- They never respond: Add one sentence that makes the ask specific: “Can you approve this cut by Thursday 2 PM?”
Sending a large video through email is mostly about reducing uncertainty. File size is math. Approval workflows are human. If you give the recipient a link that opens, a filename they can reference, and a clear next step, you will stop living in the follow up loop.