How to get a PDF under an email attachment limit

Every mail system draws a line somewhere, and it is rarely the line you expect. Worse, the size the server measures is not the size you see on disk. Before touching your file, it helps to know exactly what wall you are up against.

The real limits, and the hidden 33% tax

Gmail caps attachments at 25 MB. Outlook.com and Microsoft 365 sit around the same neighbourhood by default, while a great many corporate and older mail servers stop at 10 MB, and some legacy gateways as low as 5 MB. Those are the numbers you are told. Here is the one you are not: email cannot carry raw binary data, so every attachment is re-encoded in a format called base64 before it is sent. Base64 inflates the payload by roughly a third. A file that reads as 24 MB on your desktop can arrive at the server as about 32 MB of encoded data: over a 25 MB cap, and rejected.

The practical consequence is simple: aim below the raw cap, not at it. Leave headroom for the encoding tax and for the message body itself.

Step one: figure out why it is big

Do not start compressing blindly. Diagnose first, because the cause dictates the cure. A PDF made from a Word document or a spreadsheet is mostly selectable text and vectors, which are already tiny; if such a file is somehow huge, the bloat is structural and a lossless tidy-up will fix it for free. A PDF made by scanning paper or stuffed with photographs is a different animal entirely: nearly all of its weight is in images, and that is content you can genuinely shrink. If you want the full explanation of which parts of a PDF carry the weight, and why a naive squeeze can even make a text file grow, that is covered in why a compressed PDF sometimes gets bigger.

Step two: shrink the images

For an image-heavy or scanned document, image compression does the heavy lifting. Re-encoding the pictures at a sensible quality can take a 40 MB stack of scans down to a few megabytes without making it unreadable. The Compress PDF tool does exactly this. It optimizes each page as an image, entirely in your browser with nothing uploaded, and it is described end to end in how to compress a PDF. Be realistic about outcomes: a scanned contract might drop by ninety percent, while a lean text PDF that was already small has little to give and should be left alone.

Step three: walk it down to a hard target

General compression hands you whatever size it produces and hopes it is enough. But an email gateway does not want "smaller, probably." It wants the file under a specific number. When you have a firm ceiling, the Reduce PDF Size tool is built for it: you type the target (say 7 MB for a 10 MB server, or 18 MB for Gmail) and it steps down through quality levels until the file fits, then reports the size it achieved. If your target is not reachable, it tells you honestly and gives you its best result rather than a ruined, illegible document. The step-by-step version lives in how to reduce PDF file size.

Step four: split when one file simply cannot shrink enough

Sometimes the content is irreducible. A 200-page scanned manual will not fit under 10 MB at any quality you would want to read. When shrinking hits its floor, stop fighting it and divide the document instead. The Split PDF tool breaks a large file into smaller parts you can send across two or three messages (chapters, page ranges, or halves), with each piece comfortably under the cap. Number them clearly in the filenames so your recipient can reassemble the order at a glance.

Step five: when nothing fits, send a link

If a document is both large and must stay intact (a high-resolution portfolio, a legal bundle that cannot be broken up), stop treating email as the delivery mechanism. Upload the file to a cloud drive and paste a share link into the message instead. The email stays tiny, the recipient downloads the full file at their leisure, and you sidestep the attachment cap completely. It is not a compromise so much as the correct tool for genuinely large payloads.

A quick decision path

1. Check the server's real limit and subtract the base64 tax, aiming for about three-quarters of the stated cap.
2. Is it text-based and oddly large? Optimize losslessly and you may already be done.
3. Is it scanned or photo-heavy? Compress the images.
4. Still over? Reduce to your exact target number.
5. Physically cannot fit? Split into parts, or share a link instead.

Everything above runs locally in your browser, so a tax return or a signed contract never leaves your device on its way to fitting under the limit. Work the steps in order, respect the encoding tax, and the bounce message stops coming back.