Gmail attachment size limit: 25 MB, and how to send more

Quick answer: Gmail lets you send up to 25 MB per email and receive up to 50 MB. Because of how attachments are encoded, the largest file you can reliably attach is about 18 MB. For anything bigger, send a link to the file instead of the file itself.

Gmail’s attachment limit is 25 MB. In practice you will hit it before the file reaches 25 MB, and the reason is worth understanding because it explains most of the confusing behaviour around email attachments.

Attachment limits by email provider

The limits are similar everywhere, which is why switching email provider does not solve the problem:

All of these limits apply to the whole message, not each file, and the encoding overhead below applies to all of them. Plan on about 18 to 20 MB of real files per email, whatever provider you use.

How big a file can you send through Gmail?

In everyday terms, 25 MB is roughly:

• A few dozen phone photos, at 2 to 5 MB each before encoding.
• One long PDF with images, such as a brochure or a scanned contract.
• 10 to 20 seconds of phone video in 1080p, and much less in 4K.
• A few minutes of MP3 audio.

Video is the one that catches everyone out. Our guide to sending videos without losing quality covers what to do instead.

The real ceiling is about 18 MB

Email was designed to carry text, specifically 7-bit ASCII. Binary files cannot travel through that channel directly, so they are encoded - almost always with Base64, which represents three bytes of data as four characters.

That is a 33% overhead, before headers and MIME boundaries.

So a 20 MB file becomes roughly 27 MB on the wire, and Gmail measures the encoded message rather than your original file. The practical ceiling is around 18 MB of actual content. This is why a file that is obviously under 25 MB gets rejected, and why the error feels arbitrary.

The receiving server has its own opinion

Gmail’s limit governs what you can send. It says nothing about what the recipient can accept.

Many organisations cap incoming mail at 10 MB. Some older systems sit at 5 MB. Gmail will accept your 24 MB message, send it, and the rejection arrives minutes or hours later from a server you have never heard of, in a bounce message written for administrators.

This asymmetry is the single most common reason “I sent it, did you get it?” exists as a genre of email.

Why the cap exists

It is not arbitrary rationing. An attachment is stored in full for every recipient, plus your sent folder, plus every backup of each of those mailboxes. One 20 MB file sent to eight colleagues creates at least 180 MB of permanent storage across an organisation, and no process will ever clean it up.

Mail servers also hold messages in memory while processing them. Large attachments make that expensive at scale.

The caps are what stop mailboxes becoming file servers, and they have not moved in fifteen years because the underlying reasoning has not changed.

Four ways past it

Send a link instead of a file

Upload once, share a URL. The message stays small, the recipient needs no account, and you keep control after sending - you can replace the file, expire the link, or revoke it.

This is the only option that improves with file size rather than degrading. Our guide to sending large files free covers doing it without paying, and the methods compared covers when a link is the wrong tool.

Compress, but only what compresses

Zipping is a reflex and often accomplishes nothing.

Worth compressing: text, CSV, JSON, source code, uncompressed audio, TIFF and PSD files. A folder of spreadsheets can shrink by 80% or more.

Not worth compressing: JPEG, PNG, MP4, MP3 and PDF are already compressed internally. Zipping them typically saves one or two percent and costs the recipient an extra step - sometimes a real obstacle on a phone.

One genuine exception: a folder of many small files is worth archiving regardless of the size saved, because one attachment beats forty.

Split the archive

Archive tools can split output into parts under a size limit. It works, and it is miserable for the recipient, who now needs every part present, in the same folder, with software that understands the format. If one part is caught by a spam filter, they get a corrupt archive and an unhelpful error.

Treat this as a last resort for recipients you can talk to directly.

Turn the direction around

If you need files from someone, do not negotiate limits at all. Send them an upload page. They choose a file, it arrives, and no attachment ever exists.

This is consistently the best experience for non-technical recipients, because there is nothing to install and nothing to understand.

Gmail’s own escape hatch

Attach something over 25 MB and Gmail offers to upload it to Drive and insert a link instead. It is the link method with extra steps, and it works.

Two caveats. The recipient may need permission granted separately - if the file inherits restrictive sharing settings, they get a request-access screen, which is where “I can’t open this” replies come from. And it consumes the same Drive quota as everything else in your Google account, so it is not free space, it is your space.

When workarounds are the wrong answer

If you are doing this weekly with the same people, no workaround is the fix. The files should live somewhere both parties can reach.

Mounting shared storage as a drive removes the transfer entirely: you save into a folder, and it is already where they can see it. On Windows the equivalent setup is here. Either way, the tenth transfer costs nothing because there is no transfer.

Sending a link with dosya.dev

Our free plan includes share links, so you can send a file of any size your storage holds without paying anything:

1. Upload the file in the web app, the desktop app or the mobile app.
2. Create a share link, and add a password or an expiry if it is sensitive.
3. Paste the link into your Gmail message.

The email stays tiny, the recipient downloads the original file without an account, and you can see when it was downloaded. The share links overview shows the options.

Quick reference