Guide
How to compress a PDF for an email attachment — using the PDF Pro email-target compressor.
If you've ever waited five minutes for an attachment to upload, hit Send, and gotten a "message too large" reply 30 seconds later — this guide is for you. We'll get a PDF under Gmail's 25 MB cap, Outlook's 20 MB cap, or Apple Mail's 20 MB cap on the first try, with a preset that does the math for you.
What you'll need
- A modern browser
- The PDF you'd like to attach
- About two minutes (less if your file is small)
- Your email draft open in another tab, ready to attach
The five steps
Open the email-target compressor
Open the PDF Pro email compressor. It's the same engine as the standard PDF Pro reducer, but with mailbox-specific presets pre-configured. Each preset accounts for MIME-encoding overhead — it actually targets ~5–10% under the published cap, because the published cap is post-encoding.
Drop your PDF in the page
Drag the file onto the drop zone. The page parses it locally — no upload — and shows you the current file size in MB so you know how aggressive the compression will need to be. If you're already under your target, the page tells you so and skips the rest of the workflow.
Pick the right mailbox preset
Pick the preset that matches the recipient's email provider, not necessarily yours. If you're sending to a corporate Outlook user, the Outlook 20 MB preset is the safer bet — even if your Gmail outbound allows 25 MB, the recipient's server may reject anything over their cap.
Confirm the result hits the cap
The result panel shows new file size with a green check if you're under the preset cap, or a red flag if the PDF can't compress that small at the current quality tier. If it's flagged, drop one tier (Mixed → Smaller → Smallest) and run again, or split the PDF into two smaller attachments.
Attach to the draft and send
Click Download, switch to your email tab, and drag the compressed file onto the draft. Compose, send, and watch for the bounce that doesn't come this time. The original file is untouched on disk — keep it for archive.
Download for GmailCommon mistakes & gotchas
- Picking Maximum compression when a mid-tier would do. Maximum quality loss is unnecessary if your PDF is only slightly over the cap. The Gmail preset starts conservative and ramps if needed.
- Targeting your own mailbox cap, not the recipient's. Outlook 365 users can sometimes send 25 MB but recipient corporate servers reject anything over 20. Pick the recipient's expected provider.
- Forgetting MIME-encoding overhead. Email attachments inflate ~33% over raw bytes. A 24 MB PDF may arrive as 32 MB on the wire. The presets handle this; custom caps don't unless you do the math.
- Compressing the wrong PDF. If your draft already has the original attached, remove it before attaching the compressed copy — most clients will keep both, doubling your size.
- Not checking the recipient actually received it. Bounces sometimes silently route to spam folders. Confirm receipt for important sends.
Troubleshooting
The PDF is still too large after Maximum compression.
Some PDFs (high-res photo books, scanned art portfolios) can't compress under 25 MB without unacceptable quality loss. Consider splitting the file with a page splitter and sending in two emails, or upload to Drive/OneDrive and share the link instead.
Outlook is rejecting a 22 MB file even though the cap is supposedly 25.
Outlook's Office 365 cap can be lower than 25 MB depending on tenant policy — many enterprises lower it to 10 MB. Use the Outlook preset (target 18 MB) and try again, or check with the recipient's IT.
Apple Mail says my attachment is too big at 18 MB.
Apple Mail's iCloud route caps at 20 MB but enables Mail Drop for files up to 5 GB — the recipient gets a download link. If Mail Drop is disabled, drop down to a Custom 15 MB target.
The compressed PDF lost the embedded fonts.
Aggressive compression presets sometimes subset fonts further than the source. The recipient should still see correct rendering because subsetting preserves used glyphs. If you need full font embedding, use the Keep Text mode instead and accept a larger file.
Why does my mail server bounce 24 MB when Gmail allows 25?
The 25 MB Gmail cap is on the encoded message size, not the raw attachment. After base64 encoding, your 24 MB raw becomes ~32 MB on the wire. The Gmail preset targets ~18 MB raw to stay safely under after encoding.
Ready to attach?
Open the email compressor, pick a mailbox preset, and skip the bounce.