How to compress a pdf for email using lossless compression
- Step 1Check the recipient's mail limit — Most caps land at 10 MB (Outlook/Exchange) or 25 MB (Gmail); corporate gateways can be lower. Aim a little under the limit so the encoded MIME attachment (which inflates ~33% in transit) still fits.
- Step 2Open the lossless compressor — Go to PDF Compress (Lossless) and drop your PDF. The header shows its current size so you know how far over you are.
- Step 3Let it rebuild automatically — There's no options panel — it runs on load, copying pages into a new document, clearing Producer/Creator, and re-saving with compressed object streams.
- Step 4Check whether you're under the cap — Compare the result size against your target. If a text/vector PDF was modestly over, lossless usually gets it under. If it's a big scan that barely moved, switch to the lossy tool.
- Step 5Account for email encoding overhead — Email attachments are Base64-encoded, growing about a third on the wire. A 9 MB file can present as ~12 MB to a 10 MB gateway — leave headroom, or compress a bit further.
- Step 6Download and attach — Save the smaller PDF and attach it to your message. It's a standard PDF that opens in every reader the recipient might use.
Common email attachment limits
Approximate provider caps. Remember attachments are Base64-encoded in transit, so the effective ceiling is roughly the cap divided by 1.37. Corporate gateways may enforce stricter limits than the underlying provider.
| Mail system | Typical attachment cap | Effective PDF size to stay safe |
|---|---|---|
| Outlook.com / Exchange Online | ~10-20 MB | Aim under ~7-14 MB |
| Gmail / Google Workspace | 25 MB (send) | Aim under ~18 MB |
| Apple iCloud Mail | 20 MB | Aim under ~14 MB |
| Yahoo Mail | 25 MB | Aim under ~18 MB |
| Corporate gateway (varies) | Often 5-10 MB | Aim under ~4-7 MB; confirm with IT |
Will lossless get you under the limit?
Depends entirely on what's in the PDF. Lossless reclaims structural slack; it cannot shrink image pixels. Use this to decide before you compress.
| Your PDF is… | Lossless likely outcome | If it's still too big |
|---|---|---|
| A text/vector report slightly over the cap | Usually gets it under (10-30% off) | Already minimal — this is the right tool |
| A merged/edited PDF carrying dead objects | Often a large drop (20-40%) | Re-run is pointless; you're at the floor |
| A scan/photo PDF far over the cap | Barely moves (0-10%) | Lossy compress — re-encodes images, can hit a target |
| Already optimised and still too big | Almost no change | Lossy, or split and send in parts |
Cookbook
Real email scenarios. Sizes are illustrative; the tool reports the exact figures for your file.
An 11 MB proposal blocked by a 10 MB gateway
A text-and-charts proposal exported from Word was just over the corporate cap. Lossless packing and dead-object pruning brought it comfortably under with no visible change.
Cap: 10 MB corporate gateway Input: proposal-final.pdf 11.2 MB Output: proposal-final.pdf 8.3 MB Result: ~26% off — sends cleanly, recipient gets full quality
A contract bundle just over Gmail's 25 MB
Several signed PDFs were merged, leaving duplicate fonts and orphaned objects. The rebuild dropped them and slid the bundle under 25 MB.
Cap: 25 MB Gmail Input: contract-bundle.pdf 27.0 MB, 95 pages Output: contract-bundle.pdf 18.4 MB, 95 pages Result: ~32% off — under the cap with headroom for encoding
A 40 MB scan that lossless can't fix
An image-only scanned packet barely shrinks losslessly. The right move is the lossy tool with a target size.
Cap: 10 MB Outlook Input: scanned-packet.pdf 41 MB (image-only) Lossless output: 39 MB (~5%) — still far over → Use /pdf-tools/pdf-compress-lossy, target ~9 MB
Leaving room for Base64 encoding
A 9.6 MB PDF technically fits a 10 MB cap, but Base64 inflation can push the encoded attachment over. Trim a little further or split.
Cap: 10 MB
Lossless output: 9.6 MB → encodes to ~13 MB on the wire (bounces)
Fix: compress source further (lossy) OR split into two emails
via /pdf-tools/pdf-split-rangeSplitting when nothing fits
When a document genuinely can't get small enough losslessly and must keep selectable text, split it and send the halves.
Input: handbook.pdf 18 MB, 200 pages (text)
Lossless output: 14 MB — still over a 10 MB cap
Fix: split 1-100 / 101-200 via /pdf-tools/pdf-split-range
→ two ~7 MB emails, full quality eachEdge cases and what actually happens
It's a big scan — lossless won't get it under the cap
By designLossless never re-encodes image data, so a scan or photo PDF that's far over the limit barely shrinks. That's the guarantee, not a failure. For a scan you must email, use lossy compress with a target size (e.g. 9 MB) — it re-renders pages as JPEGs and can actually hit the number, trading away selectable text.
Output fits the cap but the email still bounces
Encoding overheadAttachments are Base64-encoded, inflating roughly 33% in transit. A 9.6 MB PDF can present as ~13 MB to a 10 MB gateway and bounce. Leave headroom — aim for the cap divided by about 1.37 — or compress a little further. This is a transport quirk, not a problem with the file.
Already-optimised PDF won't get smaller
ExpectedIf the PDF already uses object streams and has no dead objects, there's almost nothing to reclaim and it stays roughly the same size. If it's still over the cap, either re-render with the lossy tool (if image-heavy) or split it and send in parts.
The PDF is password-protected
Loaded with ignoreEncryptionThe engine can open the file (encryption is ignored on load), but the compressed output is not re-encrypted. If the recipient needs the password kept, remove it with Remove Password first, compress, then re-apply protection before emailing. Don't assume the password carries over.
The attachment is digitally signed
Signature invalidatedCompressing rewrites the bytes and breaks the signature's hash, so the recipient's reader will flag it as invalid. If signature validity matters for the email, send the original signed file (and split it if it's too big) rather than compressing it. To re-sign, use Digital Signature after compressing.
File exceeds your tier's size limit
BlockedPDF caps by plan: Free 2 MB, Pro 50 MB, Pro+Media 500 MB, Developer 2 GB. A large attachment over your tier's limit won't load — the very files you most want to email may need a higher plan, the lossy tool, or splitting before they fit both the tool and the mailbox.
Document exceeds your tier's page limit
BlockedPage caps: Free 50, Pro 500, Pro+Media 2,000, Developer 10,000. A long handbook over the cap won't process. Split it with Split by Range — which also conveniently produces smaller, mailable pieces.
Corrupt PDF won't load
ErrorIf the file is truncated or malformed, pdf-lib can't parse it and compression can't run. Repair it with Repair PDF first, then compress and attach.
Output barely smaller than the original
PossibleA lean, already-tight text PDF has little structural slack, so the drop is small and may net flat after object-stream overhead. The pages are preserved exactly. If it's still over the cap, split it or use the lossy tool for image-heavy content.
Producer metadata expected by the recipient's system
Producer/Creator clearedThe tool blanks the Producer and Creator fields. This is harmless for normal email, but if the recipient's intake system keys on those fields, be aware they'll be empty. For deliberate metadata control use the Metadata Scrubber.
Frequently asked questions
Will the recipient notice any quality loss?
No. Lossless compression copies every page through without re-encoding images or rasterising text, so the recipient opens a document that's pixel-identical to your original and still fully selectable. The size reduction comes from packing the file's structure and dropping unused objects — nothing visible changes. That's the whole point of choosing lossless for an attachment.
Can it always get my PDF under the email limit?
Only if the PDF has structural slack to reclaim. A text or vector PDF that's modestly over the cap usually slips under after a 10-30% reduction. But a big scan barely moves, because lossless can't re-encode image pixels — for those you need lossy compress, which can hit a target size. Check the result size against your cap before sending.
What are the typical email attachment limits?
Roughly 10-20 MB for Outlook/Exchange, 25 MB for Gmail and Yahoo, 20 MB for iCloud Mail, and often 5-10 MB for corporate gateways. Crucially, attachments are Base64-encoded and grow about a third in transit, so aim for the cap divided by ~1.37 to be safe — a file that's exactly at the limit can still bounce.
Why did my file fit the limit but the email still bounced?
Email encoding. Attachments are Base64-encoded, inflating roughly 33% on the wire, so a 9.6 MB PDF can present as ~13 MB to a 10 MB gateway. Compress a bit further, or split the document with Split by Range and send it in two messages — each half staying comfortably under the cap.
My scanned PDF won't shrink enough to email. What now?
Switch to lossy compress. It re-renders each page as a JPEG and can target a specific size like 9 MB, so it actually shrinks scans that lossless can't touch. The trade-off is that text becomes part of the image (no longer selectable). For an emailed scan that's usually acceptable; for a contract you need to cite later, keep it lossless and split instead.
Is my attachment uploaded to a server to compress it?
No. Compression runs entirely in your browser, so the attachment — often a confidential proposal, invoice, or contract — never leaves your device. Only an anonymous usage counter is stored server-side if you're signed in, never the document itself. You can attach the result with confidence regardless of its contents.
Will the compressed PDF open on the recipient's device?
Yes. The output is a standard PDF written with compressed object streams (supported since 2003), so it opens in Outlook's preview, Gmail's viewer, Apple Preview, Acrobat, and every mobile reader. There's no special format or plugin needed — it's about as universally compatible as a PDF gets.
Does compressing affect a signed or password-protected attachment?
Yes on both. Compressing rewrites the bytes, which invalidates a digital signature, so send signed files uncompressed (split if needed). And the output isn't re-encrypted — if the recipient needs a password, remove it with Remove Password, compress, then re-apply protection before sending.
Are there options I should set before compressing?
No. The lossless compressor runs automatically when you drop a file, with one fixed rebuild and no sliders or presets. If you need to target a specific size for a tight cap, that capability is on the lossy compressor instead — set a target like 9 MB and it searches quality to land under it.
What's the biggest file I can compress here?
By plan: Free up to 2 MB, Pro 50 MB, Pro+Media 500 MB, Developer 2 GB (with page caps of 50 / 500 / 2,000 / 10,000). Files over your tier's limit are blocked. Note the free 2 MB cap is below most email limits, so very large attachments may need a higher plan or splitting before they'll even load.
If lossless isn't enough and I can't lose quality, what's the fallback?
Split the document. Use Split by Range to break it into sections small enough to email, each keeping full quality and selectable text. It's the cleanest option when the content must stay pristine but the whole file simply won't fit a single message.
Can I automate compressing outgoing PDFs?
Yes, with the @jadapps/runner. Fetch the schema via GET /api/v1/tools/pdf-compress-lossless, pair the runner once, then POST files to 127.0.0.1:9789/v1/tools/pdf-compress-lossless/run. Everything runs locally, so attachments never leave your machine — handy for a script that compresses reports before they're queued for sending.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.