Gmail Send vs Receive Attachment Size Limit, Explained

Gmail's sending limit and Gmail's receiving limit are two different numbers, set by two different rules — and for a personal Gmail account, Google only publishes one of them. Almost every article on this topic quotes "25 MB to send, 50 MB to receive" as if both halves came from the same page. They did not.

Here is what Google's own documentation states, with the qualifiers that get dropped everywhere else.

The limits, at a glance

For personal accounts, Gmail Help is a single sentence: "For personal Gmail accounts, the limit is 25 MB." For managed accounts it hands the question to someone else: "For work and school accounts, your Google Workspace administrator sets the attachment sending limits and attachment receiving limits."

The asymmetry Google actually documents

The Workspace admin pages are where the send-versus-receive split becomes explicit. The sending table reads, verbatim:

Edition	Attachment limits (sending)*
Business	25 MB
Education	25 MB
Enterprise	Up to 50 MB** for Enterprise Plus and 25 MB for Enterprise Standard.

Two footnotes hang off that table, and both change the meaning:

• "Available only on the web version of Gmail." — this is attached to the 50 MB figure. An Enterprise Plus user sending from a mobile Gmail app is not covered by it.
• "These values are the limits on the total size of the message content and attachments before encoding."

The receiving page gives different numbers for the same editions: "You can receive emails of up to 50 MB (Enterprise Standard) or 70 MB (Enterprise Plus)." So an Enterprise Standard account sends up to 25 MB but accepts up to 50 MB. Enterprise Plus sends up to 50 MB (web only) but accepts up to 70 MB.

That page also states the receiving figures are measured on the other side of encoding: "These values are the limit after encoding, which adds about a 37% increase." Sending is measured before encoding, receiving after. That is Google's own wording on two separate pages, not an inference — and it means the send and receive numbers are not directly comparable even when they look like plain megabytes.

One more line from the receiving page is worth keeping: "These Gmail limits apply to all editions and can't be increased. The limits may change without notice." There is no admin toggle that raises them.

What Google does not say about personal accounts

This is the part the top results get wrong. The 50 MB and 70 MB receiving figures appear only on the Workspace admin page, explicitly tied to Enterprise Standard and Enterprise Plus. There is no published receiving limit for a personal Gmail address. If you need one, check the official documentation — do not take the widely repeated "50 MB inbound" as applying to a free account.

Two related blanks, for the same reason:

• Whether the personal 25 MB is measured before or after encoding. The "before encoding" wording exists only on the Workspace sending page.
• Whether the roughly 37% encoding overhead applies to sending at all. Google attaches that note to the receiving limit only, so any "you can really only send 17–18 MB" figure derived from it has no official source.

Google also never states that Gmail compresses or transcodes your attachments. Plan on the file you attach being the file that gets measured.

What to do when you hit the limit

Gmail's documented behaviour on overflow is not a bounced message: "If your total attachment size is greater than the limit, Gmail automatically removes the attachment and adds it as a Google Drive link in the email." The Workspace receiving page gives the same advice as a deliberate workflow: "To send file attachments larger than the size limit, use Google Drive or other file-sharing services."

That handoff solves the size problem and creates a permissions problem. Once the file travels as a Drive link, whether the recipient can open it is decided by Drive sharing, not by Gmail. Gmail Help describes the check: "When you attach a Google Drive file to a message, Gmail checks to see if your recipients have access to the file. If they don't, you'll be prompted to change the sharing settings of the file before you send your message."

If you would rather the file stay a real attachment — so it lands in the recipient's inbox with no sign-in, no link, no sharing dialog — the answer is to make it smaller before Gmail sees it. For video, that is almost always straightforward: a phone clip or screen recording is usually carrying far more bitrate than an emailed file needs.

This runs entirely inside your browser tab — the file is read from disk, re-encoded locally, and handed back. Nothing is uploaded, which matters when the whole reason you are compressing is to avoid putting the file on someone else's server. See all Clapr tools for the rest of the browser-side toolkit, or the video compressor directly if you want manual control over the settings.

Gmail-specific gotchas

The 25 MB is your total, not per file. Google's wording is "your total attachment size," so three 10 MB files in one message are over the limit even though no single file is. This is the opposite of how per-file caps like Slack's upload limit work, and copying the mental model across platforms is how people get surprised.

A full storage quota blocks attachments in both directions. Gmail Help: "Attachments count toward your Google storage. Storage is shared across Drive, Photos, and Gmail. If you reach your storage limit, you can't send or receive attachments." If attachments stopped working and the file is clearly small, check your storage before you check the size.

Some failures are about file type, not size. Gmail blocks executables — "To prevent viruses, Gmail doesn't let you attach executable files, like files ending in .exe" — and the published blocklist includes .img and .iso, so footage handed to you as a disc image will not attach at any size. No common video or audio extension appears on that list, so a rejected video is a size, storage, or sharing problem rather than a format ban. Google notes the list changes over time, so check the official documentation for the current version.

Received messages cap the attachment count too. The Workspace receiving page states "You can receive up to 500 attachments per single email." That ceiling is on the receiving side; Google does not publish an equivalent number for sending.

FAQ

Why can Gmail receive a bigger attachment than it can send? On Workspace, that asymmetry is documented: Enterprise Standard sends up to 25 MB but receives up to 50 MB, and Enterprise Plus sends up to 50 MB (web Gmail only) but receives up to 70 MB. The two limits live on two different admin pages and are measured on opposite sides of encoding.

What is the receiving limit for a personal Gmail account? Google's official documentation doesn't state one. The 50 MB and 70 MB figures you see quoted are from the Workspace admin page and are labelled Enterprise Standard and Enterprise Plus. Check the official documentation rather than assuming they carry over.

Does the 25 MB apply to each file or to the whole email? The whole email. Gmail Help says the check is on "your total attachment size," and if that total is over the limit the attachment is removed and added as a Drive link instead.

Can my Workspace admin raise the limit for my account? No. The receiving page states these limits "apply to all editions and can't be increased," and adds that they may change without notice.

My video is under 25 MB and still will not attach — what else could it be? Two documented possibilities: your Google storage is full, which blocks sending and receiving attachments, or the file type is on Gmail's blocklist (disc images such as .img and .iso are, common video formats are not). More size-limit breakdowns are collected in the limits hub.

Figures cited from Gmail Help's attachment guide, the Workspace admin pages on sending limits and receiving limits, checked 16 September 2026. Google states these limits may change without notice — verify against the official pages before relying on them.