When a PDF is too large to email

Email attachment limits are the most misleading numbers in this subject, because the number your provider publishes is not the number your file has to come in under.

If you have had a PDF bounce at 22MB against a "25MB limit", this is why.

The published number versus the real one

Email was designed to carry text. Binary attachments are encoded into text using base64, which represents every three bytes as four characters — inflating the attachment by about 33% before anything is sent.

The provider's limit applies to the encoded message, not to the file sitting on your disk.

Provider	They advertise	Real file ceiling	Why
Gmail	25MB	~18MB	Base64 inflation on the whole message
Outlook.com	20MB	~15MB	MIME encoding, and admins set it lower
Corporate Exchange	varies	often 10MB	Set per organisation, frequently reduced
Microsoft Teams chat	250GB	100MB	The 250GB is SharePoint, not the chat box

Two consequences worth internalising. A 20MB PDF will not send through Gmail despite being "under 25MB". And on corporate mail you often cannot find out your real limit without testing, because your administrator set it and did not announce it.

There is also a second ambiguity stacked on top: whether "25MB" means 25,000,000 or 26,214,400 bytes depends on who is counting, and almost nobody says which. Taking the smaller reading costs a sliver of quality; taking the larger one costs you the send.

The four options, ranked

1. Compress the PDF

Usually the right answer, and usually easier than people expect, because most large PDFs are large for a fixable reason.

If the document has selectable text, a lossless structural rewrite often takes 30–70% off with nothing lost — that alone gets plenty of 25MB documents under 18MB. If it is mostly photographs, downsampling those images is where the file is. Which one applies to you is diagnosable in about five seconds.

Target 2MB rather than 18MB if you can. Not because you have to, but because a 2MB attachment arrives instantly on a phone on mobile data and an 18MB one does not. The recipient's experience is part of sending it.

2. Split it

Underrated. A 60MB scanned report is often three logically separate things — the report, the appendices, the raw photographs. Sending the 3MB report and offering the rest on request is frequently what the recipient wanted anyway.

Also the correct move when compressing hard enough to fit would make the document illegible. Two emails beat one unreadable attachment.

3. Link to it instead

Upload to a file host and send a link. Gmail does this automatically above its limit by putting the file in Drive, and the result is that the recipient needs permissions, an account, or a login to see it — which is a different problem rather than no problem.

Worth knowing: the common hosts have their own limits. Dropbox takes 2TB per file, Google Drive 5TB, and WeTransfer's free tier allows 3GB in any 30-day window. None of them is your constraint; the constraint is whether the recipient can actually open a link.

4. Zip it

Almost always pointless for a PDF, and worth saying plainly because it is the most common reflex.

PDFs are already internally compressed. Zipping one typically saves 2–5% and sometimes nothing at all. It also makes the attachment more likely to be stripped — a great many corporate mail filters quarantine or delete .zip attachments outright, so you have converted "too large" into "silently never arrived".

Zip is useful for sending many files as one, not for making one file smaller.

What to actually do with a 40MB PDF

A decision procedure that takes about a minute:

Can you select text in it?
  Yes -> Lossless rewrite first. Measure.
         Under 18MB? Done, and nothing was lost.
         Still over? The images are the problem; downsample them.

  No (it is a scan)
      -> Greyscale if the content allows (saves ~60%).
         Then reduce resolution to ~150dpi.
         A 40MB scan reaches 2-4MB this way and stays readable.

Either way, is the result still too large or now illegible?
  -> Split it, or send a link.

The number to aim for

If you want one rule: target 2MB for anything you are emailing.

It clears every mail provider's real ceiling with enormous margin, it survives a corporate filter set to 10MB, it arrives quickly on a phone, and for a text-based document it is rarely even a compromise — a 40-page text PDF under 2MB is simply a well-made file.

Compress a PDF to 2MB, to 1MB or to 5MB tries the lossless pass first and measures the real output before handing it back, so "under 2MB" means it weighed under 2MB rather than that it ought to. It runs in your browser and the document is not uploaded — which, given that the PDFs people email are contracts, invoices, statements and medical letters, is worth more than the convenience.

FAQ

Why did my 20MB PDF fail to send through Gmail when the limit is 25MB?

Because Gmail's 25MB applies to the base64-encoded message, not to the file on your disk, and base64 inflates a binary attachment by about 33%. A 20MB PDF becomes a roughly 27MB message and bounces. The practical ceiling for the file itself is about 18MB, and aiming lower is wise because the rest of the message counts too.

Does zipping a PDF make it smaller?

Barely — usually 2–5%, sometimes nothing, because a PDF is already compressed internally. It also makes the email more likely to be blocked, since many corporate mail filters quarantine .zip attachments. Zip is for bundling several files into one, not for shrinking a single PDF.

What is the largest PDF I can email?

About 18MB through Gmail and about 15MB through Outlook.com, against published limits of 25MB and 20MB. Corporate Exchange servers are set per organisation and 10MB caps are common, so if you are sending to a company address, under 10MB is the safe assumption. Aiming for 2MB avoids the whole question.

How do I send a PDF that is too large even after compressing?

Split it into logical parts and send the part that matters, offering the rest on request — that is usually what the recipient wanted. If it genuinely must travel as one file, upload it somewhere and send a link, but check that the recipient can open that link without an account, which is the usual failure of this approach.