How to email large files when the attachment bounces.

You wrote the email, attached the folder, hit send, and a minute later the bounce arrived. Message rejected, attachment too large. The limit you hit is real, it is not going away, and fighting it with smaller and smaller ZIP files is the wrong game. The reliable way to email a large file is to stop attaching it and start linking to it. Here is the whole picture, including why the bounce sometimes comes from the other side.

Why the attachment bounced

Every mail system caps message size, and the cap covers the whole message after encoding, not just the file. Gmail stops you at about 25 MB. Outlook and most business mail servers sit near 20 MB. Encoding a file for email inflates it by roughly a third, so a 19 MB attachment can become a 26 MB message and die even though the file looked safe.

The part almost nobody tells you: the receiving server has its own cap. Your provider may accept a 25 MB message and the recipient's company server may refuse anything over 10 MB. That is why the same attachment goes through to one client and bounces from another. You cannot see their limit, you only see the bounce, and sometimes the bounce arrives hours later after the message sat in a queue.

There is also a quieter failure with no bounce at all. Some corporate filters strip ZIP attachments as a malware precaution and deliver the email without the file. The client replies that nothing was attached, you check your sent folder and see the attachment sitting right there, and both of you are confused. Attachments are simply the wrong vehicle for anything big.

What not to do first

Three instincts show up the moment the bounce lands, and all three make things worse.

• Recompressing the files until they fit. For photos and video, the export quality you throw away to squeeze under 25 MB is exactly the quality the recipient hired you for. A gallery crushed to fit an email limit looks like it.
• Splitting the delivery across six emails. Now the recipient has to download six attachments in order, one will land in spam, and next month nobody can find email four of six. It also multiplies the chance of hitting their server cap, because each message still carries the encoding overhead.
• Sharing from a personal cloud drive in a hurry. It can work, but the default sharing settings are where it goes wrong: the link asks the recipient to sign in, or asks you to approve access one requester at a time, and your quota fills with delivered files you then have to remember to clean out.

Each of these trades your time or your quality for the privilege of staying inside a limit that was never designed for file delivery. The email was only ever meant to carry the message.

Send a link instead

The pattern that works is simple: the file lives at a private link, and the email carries the link. Any transfer service does this. With Kepla File Transfer the whole thing takes about a minute:

1. Open getkepla.com/transfer in any browser. There is no account and no app.
2. Drag in the files or the whole folder. They are packed into one ZIP as they upload, so a hundred files arrive as one tidy download. A single transfer holds up to 10 GB, with up to 4 GB for any one file.
3. Pick how long the link should live: 1 hour, 6 hours, 24 hours, or 3 days. After that the files are deleted.
4. Copy the link into your email, or enter up to 10 recipient addresses and let each person get their own link, which also gets you a receipt showing who downloaded and when.

The email itself is now a few kilobytes. It cannot bounce for size, it cannot be stripped by a filter, and the recipient clicks once to download the original bytes, exactly as you exported them. Nothing is resized or re-encoded on the way through.

When a plain attachment is still right

Links are not a religion. A contract PDF, a one page invoice, two reference images: attach them. Under about 10 MB an attachment is the most convenient thing for everyone, it survives forever in the thread, and nobody wants to click through to a download page for a 300 KB document.

A reasonable personal rule looks like this: under 10 MB, attach. Over 10 MB, link. The 10 MB line keeps you safely under every receiving server you are likely to meet, including the strict corporate ones. If the file matters beyond this week, also keep your own copy organized at home, because expiring links are delivery, not storage.

And if you email large files often, put the link habit in your templates. A delivery email that always says what the files are, what the link is, and when it expires reads as more professional than any attachment, and you will never see the size bounce again.

FAQ