Work out the budget first
Your provider’s limit isn’t the limit that matters. A 25 MB attachment limit is common, but the recipient’s mailbox quota, their spam filter and any gateway in between can refuse something well under it. Twenty megabytes is the figure that clears almost everything.
Attachments are also base64-encoded in transit, which inflates them by roughly a third. A 20 MB file can present as closer to 27 MB to a gateway enforcing a cap on the encoded size, which is why a file that sits comfortably under the stated limit still bounces.
Find out what is making it large
Run the file through and read the two numbers before choosing a setting. Size divided by page count tells you what you’re dealing with.
A few hundred kilobytes per page is normal for real text. A few megabytes per page means images, which means the image route has something to work with. If the file doesn’t look large enough to need this at all, check what’s actually in it. A logo pasted at full camera resolution, or one scanned page inside an otherwise digital document, is a common culprit.
- Under 100 KB per page
- Born-digital text. Compression will barely move it; the lossless route is all that helps, and only slightly.
- 100–500 KB per page
- Text with a few images. Mixed results, and the tool picks whichever route wins.
- Over 1 MB per page
- Scanned or image-heavy. This is where the 80–95% reductions live, and where the setting you choose matters.
- One huge page among small ones
- Usually a full-resolution image inserted into a text document. The result panel reports the overall change, not per-page.
The setting to pick for email
Email is the least demanding destination a PDF ever has. It’s read on a screen, usually at 100%, and printed at most once. That makes the balanced setting almost always right, and the aggressive ones a common mistake.
The exception is a file something will read mechanically at the far end: a form, a statement feeding an automated check, anything with a barcode. Those want the lossless route or a high resolution, because the software reading them has no human to fill in the gaps.
When it still won’t fit
If the smallest honest output is still over the limit, size isn’t the problem to solve. These work, in the order worth trying.
Send fewer pages. A twenty-page statement cut to the three pages the recipient asked about is smaller than any compression can achieve, and it’s a better document to send.
- Split the document and send the parts as separate attachments, or across two messages.
- Extract just the pages in question, since organize can pull a range into its own file.
- Send a link instead. A file on your own storage, or a service the recipient already uses, skips every size limit in the chain.
- Ask whether they accept a shared folder. For a document this size, that’s usually the channel they expected anyway.
