Reading time: 11 min · Last verified: August 2026 · SMTPedia editorial team
You attach the file, you press send, and something refuses. Sometimes it is your own mail program, before anything leaves the building. Sometimes the message goes out and comes back an hour later. Sometimes it reaches one colleague and bounces off another who works at a different company. All three look like the same failure, and they are three different ceilings.
This is the part most guides skip. They give you one number, usually 25 MB, and a list of cloud services. The number is real but it is only one of three limits stacked on top of each other, and the file on your desk is not the size that gets measured. This page gives you the working methods for how to send a large file through email, and the arithmetic that explains why the one you tried already did not work.
Upload the file to cloud storage and paste the share link into the message body. That is what Gmail does automatically above 25 MB, and it is what Microsoft’s own support page tells Outlook users to do. Anything above roughly 20 MB is not worth attaching: base64 encoding inflates it by a third on the way out, and the server that decides whether to accept it belongs to your recipient, not to you.
Three Ceilings, and You Only Looked Up One
An attachment has to clear three separate gates, in order. Each one is set by a different party, and each one produces a different symptom. Knowing which gate stopped you is the whole diagnosis.
The program on your desk
Outlook refuses at 20 MB on internet accounts and 10 MB by default on Exchange accounts. Nothing is sent. You get a dialog box, not a bounce.
The service you send through
Gmail stops at 25 MB on personal accounts. Exchange Online defaults to 35 MB. The message is rejected at submission or swapped for a link.
The recipient’s mail server
The one nobody checks. It advertises its own maximum and answers with a 552 or a 452. This is the bounce that arrives an hour later.
Ceiling 3 is why a 30 MB deck reaches one colleague and bounces off another. Your server accepted it, theirs did not, and no setting on your side would have changed that. When the rejection is size, the reply text is usually explicit: our reference on what a 552 message size exceeds fixed maximum actually means covers the permanent form, and the 452 that fires when the mailbox is simply full covers the temporary one. The full set of numeric replies is indexed in the SMTP error codes reference directory.
Your 20 MB File Does Not Travel as 20 MB
This is the single most useful thing on this page, and it is arithmetic rather than opinion. SMTP was specified to carry 7-bit text, so a binary file cannot go across the wire as raw bytes. It is re-encoded into printable characters first, almost always with base64, one of the encodings defined by the MIME specifications. Our page on how Content-Type and MIME split a message into parts and encodings covers the mechanism in full.
Base64 represents every 3 bytes of input as 4 output characters. That is a one third increase before anything else is counted, and headers, boundary strings and a line break every 76 characters push real growth slightly past it.
| File on your disk | Roughly, on the wire | Clears a 25 MB limit? |
|---|---|---|
| 10 MB | 13.4 MB | Yes |
| 18 MB | 24.1 MB | Only just |
| 20 MB | 26.8 MB | No |
| 25 MB | 33.5 MB | No |
The practical rule. Multiply the file size by 1.35 before comparing it to any published limit. A 25 MB ceiling is really an 18 MB ceiling for the thing sitting in your folder. This is not an estimate someone invented: Microsoft applies the same correction in its own products, and states that Outlook on the web restricts you to 25 percent below the configured maximum precisely to leave room for the encoding increase.
What the Big Providers Actually Publish
Transcribed from the providers’ own documentation, not from comparison articles. The third column is the one that matters, because it is what your file may actually be after encoding.
| Service | Published limit | Usable file size |
|---|---|---|
| Gmail, personal | 25 MB per message | About 18 MB |
| Google Workspace | Set by the administrator; Enterprise Plus sends 50 MB and receives 70 MB since February 2026 | Varies by tenant |
| Exchange Online, default | 35 MB sending, 36 MB receiving | About 26 MB |
| Exchange Online, maximum | Admin may set 1 MB to 150 MB | 112 MB once mail leaves Microsoft |
| Outlook desktop, internet accounts | 20 MB, client side | About 15 MB |
| Outlook desktop, Exchange accounts | 10 MB by default, client side | About 7 MB |
Microsoft’s Outlook support article says the limit is 20 MB for internet accounts and 10 MB for Exchange accounts. Its Exchange Online service description says the default is 35 MB. Neither is wrong, and this is the source of most of the confusion in this topic: the first number is enforced by the program on your computer, the second by the service behind it. The client refuses before the server ever gets a say. If you looked up 35 MB and Outlook rejected a 22 MB attachment, you were reading the right number for the wrong layer.
Provider by provider values for the mail programs themselves, including the hosts and ports that go with them, live in our settings pages for Gmail and its app password requirement, Outlook.com and Hotmail, and Yahoo Mail. If you want the published ceilings on their own, without the workarounds, that is the job of our dedicated reference on attachment size limits in Gmail, Outlook and on the wire.
Five Methods That Work, Ranked by How Little They Ask of You
1. Let Gmail Do It For You
If you are on Gmail, the work is already done. Google states that when the total attachment size is greater than the limit, Gmail removes the attachment and adds it as a Google Drive link in the message instead. You attach normally, and above 25 MB the interface swaps the mechanism without asking.
The catch is permissions, not size. The file lands in your Drive with whatever sharing setting your account defaults to, and if that default is restrictive your recipient opens the message and hits a request access screen. Before you send, set the link so that anyone with it can view. This is the single most common failure of the easiest method, and it happens after the message is delivered, so nothing bounces to warn you.
2. Upload to Cloud Storage and Paste the Link
This is what Microsoft’s own guidance recommends: upload to OneDrive or a comparable service, let it generate a link, and share the link. Business accounts with SharePoint can save to a library and share from there. It works from any client and any provider, and the message stays a few kilobytes, which means it clears all three ceilings at once.
CHECK THESE THREE BEFORE YOU SEND THE LINK
Who can open it. Anyone with the link, or named people only. How long it lives. Corporate tenants often expire external links after a set number of days. Whether they can download. View only is the default in several tenants, and it is not what you want when you are sending a working file.
3. Use a Transfer Service for One Off Sends
When the recipient is outside your organisation and you do not want a permanent copy sitting in your storage, a dedicated transfer service is cleaner than cloud storage. You upload, it gives you a download link, and the file expires on its own. Dropbox advertises its Transfer feature for files far past any mail ceiling, up to 250 GB, and Filemail publishes a free tier of up to 5 GB. Ceilings vary by plan, so read the tier you are actually on rather than the headline number.
The trade off is trust. A link to a consumer transfer domain looks, to a filtering engine and to a cautious recipient, a great deal like the pattern used by attackers. If the file is sensitive or the recipient is a large enterprise, expect the message to be held or the link to be rewritten. Our guide to the phishing patterns that pass every automated check explains what those filters are looking for, and why an unexpected download link from a domain nobody recognises scores badly.
4. Compress It, and Know When That Is Pointless
Microsoft suggests zipping, and states plainly that it might decrease the file enough to fit within the Outlook limits. The honest version is that it depends entirely on what the file is, and the difference is large enough to decide whether this method is worth trying at all.
| File type | Does zipping help? |
|---|---|
| Text, CSV, logs, uncompressed databases | Dramatically. Often a fraction of the original |
| Word and Excel documents, PDFs with text | Somewhat. Worth one attempt |
| JPEG, PNG, MP4, MP3, files already zipped | Almost never. These are already compressed |
The video case deserves its own warning, because it is the most common version of this question. A video file is already compressed, so zipping a 400 MB clip produces a 398 MB zip and wastes ten minutes. The only thing that shrinks a video is re-encoding it at a lower bitrate or resolution, which is a different operation with a real quality cost. For video, skip to a link.
One more trap worth naming: in the new Outlook, you can change the display size of an image you have inserted, but that does not reduce the file size. Microsoft says so in the same article. Making a photo look smaller in the message body changes nothing about what gets transmitted.
5. Split the File, as a Last Resort
Archive tools can break one large archive into numbered volumes that you send across several messages. It works, and it is the worst option on this page. Your recipient needs the same tool and all the parts, a single missing message makes the rest useless, and multi part archives from unfamiliar senders are exactly the shape that security filters quarantine. Use it when a link is genuinely impossible, such as a recipient whose policy blocks external file sharing outright, and tell them in advance that it is coming.
Choosing in Ten Seconds
Under 15 MB on disk? Attach it normally. It will clear every ceiling in the table above.
15 to 25 MB, and it is text or documents? Zip it first, then attach. One attempt, and you will know immediately.
Anything over 25 MB, or any video at all? Send a link. On Gmail this happens by itself; anywhere else, upload first and paste.
Sensitive, or the recipient is a large enterprise? Use your own organisation’s storage rather than a consumer transfer service, and expect the link to be inspected.
What Goes Wrong After the Link Is Sent
Switching to a link moves the failure rather than removing it, and the new failures are quieter because nothing bounces. Three account for most of them.
Permissions. The recipient sees a request access screen. You will not hear about it unless they tell you, because from the mail system’s point of view the message was delivered perfectly.
Expiry. The link worked on Monday and is dead on Friday. Corporate tenants apply expiry policies to external sharing, and transfer services delete files by design. If the recipient may need the file later, say when it expires in the message itself.
Rewriting and inspection. Many organisations pass every inbound link through a protection service that rewrites the URL. The link in the received message is not the one you sent, and if that service cannot fetch the file it may block it. This is normal, not a sign that anything was configured wrongly, and it is the same machinery covered in our page on how spoofing works and what receivers do to detect it.
If you are sending files as part of an automated system rather than by hand, none of this applies in the same way, and the design question is different: our page on what a transactional email is and how those systems are built covers the pattern of sending a link to a generated document instead of the document itself, which is what every well built application does. Teams choosing where their mail runs in the first place will find the storage and attachment ceilings compared in our guide to what each business email hosting plan actually lets you do.
Frequently Asked Questions
How do I email a file that is too large?
Upload it to cloud storage and paste the share link into the message instead of attaching the file. On Gmail this happens automatically above 25 MB. On Outlook, Microsoft’s own guidance is to upload to OneDrive or SharePoint and share the link from there. Set the link so anyone with it can view before you send.
How can I email a large file over 25MB?
You cannot, as a normal attachment, on a personal Gmail account. 25 MB is the published per message limit and base64 encoding means a file of about 18 MB already reaches it. Above that, Gmail replaces the attachment with a Google Drive link on its own. Other providers require you to do the same step by hand.
Can I send large files via email at all?
Only within the limits of three separate systems: your mail program, your provider, and the recipient’s server. The lowest of the three wins, and you cannot see the third one. In practice anything above roughly 20 MB on disk should travel as a link rather than as an attachment.
How can I compress a file to send via email?
Zip it using the built in compression in Windows or macOS. Microsoft notes this might decrease the size enough to fit within the Outlook limits. It works well on text, spreadsheets, logs and documents. It does almost nothing for photos, video, audio or anything already compressed, because those formats are compressed already.
How do I send a large video through email?
Send a link. Video files are already compressed, so zipping saves essentially nothing, and even a short clip usually exceeds every mail limit. Upload to cloud storage or a transfer service and share the link. The only way to genuinely shrink a video is to re-encode it at a lower resolution or bitrate, which costs quality.
Why does Outlook reject a file that is under the limit I looked up?
Because you were reading the server limit, not the client limit. Microsoft’s Outlook article gives 20 MB for internet accounts and 10 MB by default for Exchange accounts, enforced on your computer. The Exchange Online default of 35 MB never comes into play, because the program refuses before anything is submitted.
Why did my attachment reach one person and bounce off another?
Because the receiving server sets its own maximum and it differs between organisations. Your provider accepted the message; theirs refused it, usually with a 552 for a permanent size rejection or a 452 when the mailbox is out of space. No change on your side affects a limit set by the recipient.
How do I send large files from my phone?
The same limits apply, because they belong to the provider and not to the device. The mobile Gmail app performs the same Drive substitution above 25 MB, and the iOS and Android mail apps for other providers will simply fail to send. Uploading to your cloud storage app first and sharing the link is the reliable path on mobile.
Where These Numbers Come From
The Gmail limit and the Drive substitution behaviour are stated in Google’s own Gmail help documentation. The 20 MB and 10 MB client side figures, the zip guidance and the note that resizing an image changes only its display size come from Microsoft’s Outlook support article on reducing attachment size. The 35 MB and 36 MB defaults, the 1 MB to 150 MB administrator range, the 112 MB effective ceiling for mail leaving Microsoft’s datacentres and the 25 percent reduction applied by Outlook on the web all come from the Exchange Online limits service description. The base64 arithmetic is defined by the MIME specifications, indexed on our page for RFC 2045 through 2049. Transfer service ceilings are as published by Dropbox and Filemail on their own pages and change with plan.
If you want to check what your own client is capable of before troubleshooting further, the complete email clients directory lists desktop, web and mobile programs, and the download pages for Microsoft Outlook and Apple Mail cover the two most common desktop cases. The transport rules underneath all of it, including how a server announces its maximum during the conversation, are documented in our reference on email protocols, ports and TLS configuration.
About the Author

Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.

