Gmail Email Limit Size: What 25 MB Actually Means
The gmail email limit size is quoted everywhere as 25 megabytes, and the number is true in the least useful way possible. It measures the finished message after encoding - not your file - and email encoding inflates attachments by roughly a third. The practical ceiling for the file on your desk is about 18 MB, the receiving limit is a different number entirely, and the failure modes on each side of the wall look nothing alike.
Here is the size math that actually predicts what sends, what arrives, and what silently turns into a Drive link.
The gmail email limit size in both directions
| Direction | Limit | What it measures |
|---|---|---|
| Sending | 25 MB | The complete encoded message: body, headers, all attachments after Base64 |
| Receiving | 50 MB | The complete encoded message arriving at a Gmail inbox |
| Practical attachment budget | ~18 MB | The largest raw file that survives encoding under the 25 MB send ceiling |
The asymmetry is deliberate and useful: Gmail will accept messages far larger than it will send, so a counterpart on a generous mail system can send you 40 MB even though you cannot reply in kind.
Why your 20 MB file will not send
Email is a text protocol, and binary attachments ride it as Base64 text - three bytes of file become four bytes of message, a fixed 33 percent tax before headers and MIME scaffolding add their share. The arithmetic every guide skips:
- 18 MB file -> roughly 24 MB encoded -> sends, barely.
- 20 MB file -> roughly 26.7 MB encoded -> refused, despite being "under 25".
- Two 10 MB files -> the same 26.7 MB fate; the limit binds the message, not each attachment.
When the web composer catches the overflow, it does not bounce you - it quietly uploads the attachment to Drive and inserts a link. Convenient for humans, surprising for compliance-minded senders, and unavailable to anything sending through SMTP, where the same message earns a hard rejection instead.
What the failure looks like from each door
From the Gmail web interface: the Drive substitution above, or a red warning if Drive is unavailable to the account. No bounce ever reaches your Sent folder because the oversized message never sends as mail.
Through smtp.gmail.com or the Gmail API: an SMTP-level refusal, typically a 552-class response with wording about size limits being exceeded. Your library either raises it or - worse - retries it, and no amount of retrying shrinks a payload. Log the size of what you attempted alongside the error, because the encoded size is the fact the next engineer needs and the bounce does not include your original file size.
On the receiving end: senders elsewhere get their own provider's bounce when your incoming copy would exceed 50 MB. You never see these failures at all, which matters when a client swears they emailed you the video and nothing arrived: their outbound may have died against your inbound wall without you receiving any evidence.
Workspace admins: the knobs you do and do not have
Google Workspace lets admins reduce message size limits below the defaults per organizational unit - useful for archiving discipline - but no plan tier raises sending above 25 MB. The purchased-storage question is unrelated: Drive quota governs what you can store, not what one message may weigh. The only genuine lever an admin holds is policy about the alternatives: whether Drive-link sharing is available externally, which determines whether the web composer's graceful fallback works for outside recipients. Check that policy before a customer-facing team leans on the fallback, because a link the recipient cannot open is a worse experience than a clean bounce would have been.
Moving big files like it is 2026
The 25 MB wall is a design opinion: email transports messages, not payloads. Working with the grain:
- Links over attachments, by default. Drive, Dropbox, or any object store with expiring links - one URL weighs nothing, versions cleanly, and revokes centrally. For anything a team sends repeatedly, this is policy, not preference.
- Compression only buys margins. Zipping already-compressed formats (photos, video, PDFs with images) reclaims single-digit percentages; it rescues the 19 MB file, not the 40 MB one.
- Splitting archives is the last resort it feels like. Multi-part zips arrive as N chances for one part to be spam-filtered, and reassembly instructions are a support ticket generator.
- For applications sending receipts, reports, or exports: generate the artifact to storage and email the link. It keeps every message tiny, sidesteps both directions' limits, and turns attachment questions into access-control questions your platform can actually answer.
The adjacent limits people conflate with size
Three neighbors get blamed on message size and are separate systems: recipient-count limits (a 5 MB message to 600 people fails on recipients, not megabytes); daily sending quotas (500 or 2,000 recipients per rolling day, indifferent to size); and attachment-type blocking (Gmail refuses executables and certain archive contents outright at any size, including inside zips). A rejection's wording names which wall you hit - size language means bytes, everything else means one of the neighbors.
Size is the one limit in email that never negotiates and never varies by reputation: the math above holds for a brand-new account and a ten-year veteran alike. Build the link habit and the wall stops existing; keep attaching, and 18 MB is the honest number to plan around - not the 25 printed on every label.
Frequently asked questions
What is the Gmail email size limit for sending?
25 MB measured on the fully encoded message, which means roughly an 18 MB real-world file after Base64 encoding adds its ~33 percent overhead. Anything larger is refused over SMTP or converted to a Drive link in the web composer.
Can Gmail receive attachments larger than 25 MB?
Yes - the receiving limit is 50 MB per encoded message, double the sending limit. You can accept a 40 MB message you would be unable to send back.
Why does a 20 MB file fail when the limit is 25 MB?
Because attachments are Base64-encoded for transport, growing about a third: a 20 MB file becomes roughly 26.7 MB of message and crosses the ceiling. Around 18 MB of raw file is the realistic maximum.
Can a Google Workspace admin increase the Gmail size limit?
No plan or setting raises sending above 25 MB; admins can only lower limits per organizational unit. Large files belong in Drive or another store with a link in the message - which is also the pattern that scales for application email.