How to Compress a PDF for an Email Size Limit

Most advice on this topic stops at "compress it and try again". That is fine when you are a little over, and useless when you are not. This is about hitting a hard number, in the order that wastes the least time.

The limit is smaller than the number suggests

Email cannot carry raw binary data, so every attachment is re-encoded into plain text before it is sent, using a scheme called base64. That encoding turns every three bytes into four characters. The arithmetic is unavoidable: your file arrives at the mail server roughly a third larger than it is on disk.

So a 25 MB cap is not 25 MB of PDF. It is closer to 18 MB of PDF once encoding overhead is accounted for, and slightly less again because the message body, headers and any signature image count toward the same total. This is the single most common reason a file that "should" fit is rejected anyway.

Find out what is actually heavy first

Compression behaves completely differently depending on what is inside the document. A 40 MB file of scanned pages and a 40 MB file of text with one enormous embedded font need opposite treatments, and guessing wastes a round trip. What actually happens when a PDF is compressed covers where the bytes usually are and why some files barely shrink at all.

The short version: if the document is scanned or photo-heavy, image compression will do the work and you have a lot of headroom. If it is text generated from a word processor, it is probably already near optimal and compressing it may save almost nothing. In that second case, stop compressing and skip ahead — you need a different approach, not a harder setting.

The order to try things in

1. 1Remove what the recipient does not need. This is the most overlooked step and often the biggest single win, because it removes whole pages rather than shaving quality from all of them. If someone asked for an appendix, send the appendix — Remove Pages or Split PDF will get you there faster than any compression setting.
2. 2Compress once, at a moderate setting. Check the result before reaching for anything more aggressive.
3. 3Check the text is still selectable. Try to select a line in the output. If you cannot, the pages were flattened into images — the file will be small and it will also be unsearchable, uncopyable and unreadable to screen readers.
4. 4Only then compress harder, and only if the document is genuinely screen-only. A contract someone has to print, sign or read numbers from is not screen-only.
5. 5If you are still over, stop compressing and share a link instead.

When compressing is the wrong answer

There is a point where every further megabyte costs you something the document needed. Small print goes soft, a signature turns into a smudge, a table of figures becomes ambiguous. A file that arrives but cannot be relied on has not solved the problem.

Two better exits. Split the document and send it in parts, which works well when the content has natural sections and badly when it does not. Or upload it somewhere and send a link — both Gmail and Outlook will offer to do this for you automatically when an attachment is too large, substituting a Drive or OneDrive link for the file. For anything confidential, check that the sharing link is restricted to the recipient rather than open to anyone who has it.

The published limits

• Gmail: 25 MB for personal accounts. On a work or school Google Workspace account, an administrator sets the limit and it can be lower — which is why a file that sends from your personal address bounces from your work one.
• Outlook.com: 25 MB, and Microsoft counts the whole message, including body text and inserted images, toward that figure.
• Everywhere else: assume nothing. Corporate mail gateways commonly enforce 10 MB, and the receiving server has its own limit that is independent of yours.

Both figures above are the providers’ own published numbers at the time of writing, and both change. The encoding overhead does not change, so the three-quarters rule of thumb survives even when the specific limit does not.