Guide
How to send large files through email
Most providers cap attachments between 20 and 25 MB, and the cap is smaller than it looks once encoding overhead is counted. Here is how to send large files through email in practice: what makes attachments bounce, which workarounds hold up, and the link-in-email pattern that makes file size stop mattering.
Plans from $12/mo with a 30-day money-back guarantee
Everything is ready. The full package is 4.2 GB, so it travels as a link instead of an attachment:
Link expires Oct 3. No account needed to download.
The problem
Why email rejects large attachments
Most major mail providers cap a message somewhere between 20 and 25 MB, and plenty of company mail servers are set lower than that. The cap covers the whole message: body, headers, and every attachment together.
The cap is also smaller than it reads. Attachments travel as encoded text, and the encoding inflates them by roughly a third. A 25 MB limit fits an 18 MB file, give or take, which is why a 20 MB attachment can bounce under a limit it appears to clear.
There are two gates, not one. Your provider checks the message on the way out, and the receiving server checks it on the way in. Their limit can be lower than yours, so the bounce often arrives from a server you have never heard of, hours after you hit send.
And when a large attachment does get through, it gets through many times: copied into every reply in the thread and into everyone's storage quota. Email carries messages well. It was never built to carry gigabytes.
The workarounds
Four ways to get a large file through email
1. Compress or split the file
Zipping earns its keep on text-heavy files. Spreadsheets, database exports, and uncompressed design files can shrink by half or more, and if the original was 30 MB, that may be the whole fix. Photos, video, and audio are already compressed, so zipping them saves single-digit percentages. A 400 MB video does not become an 18 MB attachment.
Splitting a file into multi-part archives technically ships anything in attachment-sized slices, and it is almost always a mistake outside IT circles. The other person needs the right tool to reassemble the parts, one lost part breaks the whole set, and plenty of mail filters quarantine split archives on sight.
2. Upload to cloud storage, share the link
This is the default reflex, and it works more often than not. The file goes to the drive you already have, the email carries a share link, and nobody thinks about attachment caps.
The friction lands on the other end. Get one permission setting wrong and your client hits a request-access screen, the request lands in an inbox nobody watches, and Tuesday goes to relitigating folder permissions. Stricter settings can require a sign-in with an account the client may not have. Fine for occasional sends between people in the same ecosystem; wobbly as a client-facing workflow.
3. Use a free transfer service
For a one-off personal send, free one-shot transfer tools are genuinely the right call. Upload, get a link, paste it into the email, done. Our broader guide on sending large files says the same thing: do not pay for a single personal send.
The limits are business limits. Free tiers cap sends at a few gigabytes, links expire within days, and the download page carries the service's brand and advertising around your work. When a client opens Friday's email on Monday and the link is dead, the resend is your job and the impression is yours to repair. The comparison with WeTransfer sets the two price lists side by side if you are weighing that route.
4. Move to a branded workspace
When file exchange is part of the job, stop treating each send as an event. Upload once to a workspace, and the email carries a short download link: a 6-character code served from your own subdomain, with an expiration date you choose. The message weighs a few kilobytes and clears every server on the route, because the files are no longer inside it.
The same workspace covers the direction email handles worst: receiving. An upload request link gives clients one place at your subdomain to drop files from the browser, no account needed, and it lasts a year by default. Your team gets email digests as files arrive. The full workflow is covered in share files with clients; teams moving raw footage have a video production page of their own.
Side by side
Sending large files through email: every method compared
Ceilings and lifetimes are typical for each category. The honest catches are in the last column, including ours.
| Method | Size ceiling | Lifetime | The other person needs | The catch |
|---|---|---|---|---|
| Standard attachment | About 20-25 MB per message | Permanent copies in every mailbox | Nothing | Encoding overhead cuts the usable size to roughly 18 MB |
| Compress and split | Anything in theory; a few hundred MB in practice | Permanent | An archive tool and patience | Media barely compresses; split archives confuse people and trip mail filters |
| Cloud storage share link | A few GB to 15 GB of space on free tiers | Until someone deletes or unshares it | Sometimes an account | Permission mistakes surface on the client side and come back as your support call |
| Free transfer service | A few GB per send | Days | Nothing | Send caps, expiring links, another company's brand on the download page |
| Paid one-shot transfer | Much larger; some charge per gigabyte sent | Days to weeks | Nothing | Cost scales with volume and nothing persists for the next project |
| WebUploads workspace | Your storage plan: 500 GB to 10 TB | You set expirations; upload request links last a year by default | Nothing; no account to create | Paid only, from $12/mo; there is no free tier |
Transfer volume is unlimited on every WebUploads plan. Platform rate limits apply to prevent abuse; there is no monthly send cap to watch.
When attaching is still the right call
None of this means abandoning attachments. Under about 10 MB, a document should simply be attached: a contract, an invoice, a two-page brief. The other person expects it, archiving works, and no link can rot. Some workflows also require attachments, court filing inboxes and procurement systems among them. The rule is boring and reliable: documents travel inside email, gigabytes travel as links.
How it works
The link-in-email pattern, step by step
Upload once
Drop the deliverables into your workspace. They stay organized by project instead of scattering across sent-mail threads.
Create a short download link
Pick the files, set an expiration date, and get a 6-character link like acme.webuploads.net/download/k7x2qd.
Send a normal email
Paste the link into the message. The email weighs a few kilobytes, so no server on either end has a reason to bounce it.
Choosing a method for a job that was never going to fit email? The broader guide to sending large files sorts every option by scenario, free tools included.
FAQ
Frequently asked questions
What is the maximum file size you can send through email?
Most major providers cap a message at 20 to 25 MB, and corporate mail servers are often configured lower. Attachments are also encoded for transport, which inflates them by roughly a third, so a 25 MB cap fits about an 18 MB file. Anything larger should travel as a link inside the email rather than as an attachment.
How do I send files larger than 25 MB through email?
Stop attaching and start linking. Put the file in storage you control, generate a download link, and paste that link into the email. With WebUploads the link is a short 6-character code served from your own subdomain, with an expiration date you choose, and the other person downloads without creating an account.
Does zipping a file make it small enough to email?
Only when the file is mostly text or was barely over the limit. Spreadsheets and database exports can shrink by half or more. Media files are already compressed internally, so zipping them typically saves a few percent. If the file is a video or a photo batch, plan on sending a link instead.
Why did my attachment bounce when it was under the limit?
Two usual reasons. Email encodes attachments as text, which makes them roughly a third larger in transit, so a 20 MB file can exceed a 25 MB cap. And the receiving server enforces its own limit, which can be lower than yours, so the bounce often comes from the other side hours after you hit send.
Are free transfer services okay for business files?
For a one-off personal send, yes, and we recommend them for that. For client work the limits add up: free tiers cap sends at a few gigabytes, links expire within days, and the download page carries another brand. Recurring delivery is what a paid branded workspace is for; WebUploads starts at $12 per month with a 30-day money-back guarantee.
How do I receive large files through email instead of sending them?
Reverse the pattern: email the other person an upload request link instead of asking for attachments. With WebUploads, clients open the link at your subdomain and drop files from the browser with no account. Links last a year by default, uploads land in your workspace, and your team gets email digests as files arrive.
Send the link, skip the bounce
A branded workspace turns every delivery into a short link from your own subdomain. Plans start at $12 per month with unlimited transfer volume.
30-day money-back guarantee on every plan. Cancel anytime.