Attachment limits are lower than they look, because encoding inflates your file by a third on the way out.
The limit is lower than the number suggests
This catches people out constantly, and it is not the mail client being awkward.
Email was designed to carry text, so binary attachments are encoded into text using Base64 before sending. That encoding represents every three bytes as four characters — an unavoidable 33% overhead. Add MIME headers and boundaries and the practical inflation is around 35%.
So a 20 MB PDF becomes roughly 27 MB on the wire, which a 25 MB limit rejects. The file that "should have fitted" never did.
| Service | Stated limit | Safe file size |
|---|---|---|
| Gmail | 25 MB | Under 18 MB |
| Outlook.com | 20 MB | Under 14 MB |
| Yahoo Mail | 25 MB | Under 18 MB |
| iCloud Mail | 20 MB | Under 14 MB |
| Typical corporate Exchange | 10 MB | Under 7 MB |
| WhatsApp document | 100 MB | Under 100 MB (no encoding overhead) |
The recipient's limit matters as much as yours, and you cannot see it. A message can leave Gmail happily and be refused by the receiving server — which is why the bounce sometimes arrives hours later.
What to do first
Work through these in order. Each one is cheaper in quality than the next.
- Check what is actually large. If the PDF is mostly text and still 30 MB, it usually carries a full-page background image on every page, or embedded fonts that were not subset. Compression will disappoint; the fix is upstream in whatever produced it.
- Compress at 150 DPI, quality 0.75. For a scanned document this typically removes 60-80%. Screen reading does not need more, and the recipient is almost certainly reading on a screen.
- Split it. A 200-page manual will not fit under 10 MB in readable form. Send it as three files, or send the chapter they asked about. Split PDF extracts page ranges cleanly.
- Send a link instead. Past a certain size this is the correct answer rather than a defeat — and it lets you replace the file later without sending a second email.
The Compress PDF tool shows the resulting size before you download, so you can confirm you are under the safe threshold rather than discovering it from a bounce message.
Zipping a PDF barely helps
This is the most common piece of bad advice on the subject, and it is worth being precise about why it fails.
ZIP compresses by finding repetition. A PDF has already been compressed internally — its image streams are JPEG or Flate encoded, and its text streams are Flate encoded. Compressed data is close to random from ZIP's point of view, and random data does not compress.
In practice zipping a typical PDF saves between 0% and 5%. Occasionally a PDF full of uncompressed content compresses well, but that is the exception and you cannot tell in advance without trying.
Zipping does have two real uses here: bundling several files into one attachment, and getting past filters that block certain file types. Neither of those is size reduction, and if you need 40% off, ZIP will not deliver it.
What about WhatsApp and Slack?
Different services, different rules, and both are more generous than email.
WhatsApp accepts documents up to 100 MB and does not apply Base64 overhead, since it is not email. But it re-compresses images aggressively while leaving documents alone — so sending a scan as a photo destroys it, and sending the same scan as a PDF document preserves it. Always attach as a document.
Slack allows 1 GB on paid plans and shares by link rather than by copy, so size is rarely the constraint. The constraint there is workspace storage, which is somebody else's problem until it is not.
For anything genuinely large, a link from cloud storage remains the most reliable route across every platform, and it avoids the recipient's mail server rejecting something you cannot see the limits of.
Compress once, at the end
If you are assembling a document from parts — merging scans, adding a cover page, appending an appendix — do all the assembly first and compress the finished file once.
Compressing each part and then merging means every part has been through a lossy pass, and the merged result is the sum of that damage. One pass over the combined file is both smaller and better.
The one exception is when the parts are photographs you are converting to PDF. There, compress the images first with the Image Compressor, because you can see each one and judge it — and it is still only one lossy pass. The general reasoning is in how to compress a PDF without losing quality.
Frequently asked questions
What is the maximum attachment size for Gmail?
25 MB, but Base64 encoding inflates attachments by about 33% in transit, so the practical ceiling is around 18 MB of actual file. Above 25 MB Gmail offers to upload to Drive and send a link instead, which is usually the better answer anyway.
Does zipping a PDF make it smaller?
Barely — typically 0-5%. A PDF is already internally compressed, and compressed data does not compress again. ZIP is useful for bundling several files into one attachment or getting past file-type filters, but not for size reduction.
How small should I make a PDF for email?
Aim for about 70% of the stated limit to leave room for encoding overhead. For Gmail that means under 18 MB; for a corporate server with a 10 MB cap, under 7 MB. Remember the recipient's limit may be lower than yours and you cannot see it.
Why did my email bounce even though the file was under the limit?
Either encoding overhead pushed it over — a 20 MB file travels as about 27 MB — or the receiving server has a lower limit than your provider. Corporate mail servers commonly cap at 10 MB, and the bounce can arrive hours after sending.
Can I send a large PDF on WhatsApp instead?
Yes, up to 100 MB, with no encoding overhead. Attach it as a document rather than as an image: WhatsApp re-compresses images aggressively but leaves documents untouched, so a scan sent as a photo is destroyed while the same scan sent as a PDF is not.
Should I compress before or after merging?
After. Compressing each part and then merging puts every part through a lossy pass, and the merged file carries all of that damage. One compression pass over the finished document is both smaller and better.