Email-ready PDFs are a workflow problem, not a magic button
“Compress PDF for email” sounds like a single click, yet successful delivery depends on three different ceilings: your provider’s official attachment limit, the recipient’s gateway, and any ticket or portal that sits behind the message. Gmail and Outlook personal accounts often allow attachments in a range around 20–25 MB (product limits change over time — check current help docs). Many company mail filters, encrypted gateways, and helpdesk intakes quietly enforce lower caps — commonly somewhere in the 10–25 MB band, sometimes far less for external senders.
The practical goal is not to max out the published limit. The goal is to get under the lowest cap in the path — frequently a portal, a shared mailbox, or a partner’s security appliance — while keeping the document readable. LokaPDF’s Compress PDF tool shrinks files in your browser so sensitive attachments are not uploaded to LokaPDF for compression. Pair that with sensible assembly habits and you avoid most “I never got your PDF” threads.
Know the caps that actually matter
Provider maximums (Gmail, Outlook, and friends)
Consumer Gmail and Microsoft Outlook/Microsoft 365 mail commonly advertise attachment maximums in the ballpark of 20–25 MB per message. Those numbers are useful upper bounds, not targets. Large messages may still delay, trip spam scoring, or fail on the recipient side even when your send UI accepts them.
Corporate and school gateways
Organizations often clamp external mail lower than the consumer default. A 15 MB send that leaves your Gmail can bounce from a company Exchange connector. When you email [email protected], budget conservatively — many teams treat ~10 MB as a polite ceiling even if 25 MB is theoretically allowed somewhere upstream.
Portals disguised as email
Some “email us your PDF” instructions actually mean “upload to our vendor portal, then we notify by email.” Those portals may enforce 2 MB or 5 MB regardless of Gmail’s limit. Match the portal page’s rule, not your mailbox’s.
The key workflow tip: compress after merge
People routinely compress three small PDFs, attach all three, and still confuse the recipient — or they compress early, then merge, and the combined file jumps back over the cap. Prefer this order:
- Prepare clean source pages (rotate, delete blanks, export wisely).
- Combine related files with Merge PDF so the reader opens one narrative document.
- Run Compress PDF on the merged result until it fits the real cap in your path.
- Send through Gmail, Outlook, or your work client — and keep the original until receipt is confirmed.
Compressing after merge optimizes the attachment you will actually send. It also prevents the classic mistake of three “small” files that together exceed gateway limits or clutter the thread. For step detail on settings, see How to compress a PDF.
Gmail practical advice
- Watch the red size warning. If Gmail offers Drive link conversion, that is a signal your PDF is large. For confidential files, prefer compressing to a true attachment when policy forbids open Drive links.
- Do not rely on Drive for regulated data unless your organization already approves that channel. A locally compressed attachment can be the simpler compliance story.
- Check Sent mail on mobile. Confirm the PDF opens on a phone — many executives read there first.
- Avoid stacking huge prior attachments in the same reply chain. Start a fresh message when the thread is already heavy.
Outlook / Microsoft 365 practical advice
- On-premises or hybrid Exchange may enforce lower limits than Outlook.com consumer. Ask IT or test with a colleague before a deadline.
- Message recall is not a size fix. If a 30 MB PDF bounced, compress and resend; recalling does not help the recipient’s gateway.
- Sensitivity labels and encryption can wrap messages and change effective size behavior. When in doubt, shrink the PDF first, then apply your normal secure-send process.
- Shared mailboxes sometimes have stricter quotas. A PDF that reaches a personal inbox may fail into a department alias.
Choosing a size budget for email
Use stricter long-tail pages when you know the number: 500 KB, 1 MB, 2 MB, or 5 MB. When the recipient only said “email it,” a working heuristic is:
- Text-only letters: often fine well under 5 MB without heroic effort.
- Short image packets: aim near 5 MB for comfort.
- Unknown corporate recipient: try to stay under ~10 MB when possible (informational soft aim), even if Gmail allows more.
- Hard portal behind the mail: obey the portal’s MB/KB text exactly.
Honesty about quality and scans
Email compression is still compression. Image quality may drop. Multipage phone scans are harder to shrink than Word exports. If a handwritten page becomes unreadable, reduce page count or rescan before another aggressive pass. LokaPDF will not pretend every 40 MB binder becomes a crystal-clear 2 MB attachment.
Privacy while preparing attachments
Email already sends a copy to providers — that is inherent to mail. What you can avoid is uploading the same PDF to an extra compress website first. LokaPDF processes compression locally in the browser; file content is not uploaded to LokaPDF for that step. After download, attach via your normal client. Broader context: Are online PDF tools safe?.
Subject lines, filenames, and recipient UX
A perfectly sized PDF still fails if it is named scan(3)_final_FINAL.pdf. Use clear names: Invoice-4491.pdf, Offer-Signed-Lee.pdf. Mention the page count in the email body for long packets. If you had to compress aggressively, note that images were optimized for email so the recipient does not assume your scanner is broken.
Troubleshooting bounced or missing PDF emails
You see the message in Sent, they do not
Gateway strip or quarantine is likely. Compress further, rename the file, and resend in a new thread. Ask if they have an upload portal with a known cap.
Attachment became a link automatically
Your client decided the file was too large. Compress under your target and attach again if you need a true PDF attachment.
File opens on desktop but not on phone
Rare corruption or an interrupted download on your side — re-compress and re-download. Confirm the local file opens before blaming the recipient.
Tooling checklist
Compress: Compress PDF. Assemble first: Merge PDF. Method guide: How to compress a PDF. Safety guide: Are online PDF tools safe?.
Closing thought
Email success is the minimum of every limit in the chain. Respect published 10–25 MB realities without treating them as a dare, compress after you merge, proof scans honestly, and keep processing local with LokaPDF until the attachment is actually ready to send.
FAQ
What size should I compress a PDF to for email?
Stay under the lowest limit in the path. Gmail/Outlook may allow ~20–25 MB, but corporate gateways and portals often need smaller files — many people aim under ~10 MB when the recipient is unknown.
Should I merge PDFs before compressing for email?
Yes when the reader should get one document. Merge for order first, then compress the combined PDF so the attachment you send already fits the cap.
Why did Gmail turn my PDF into a Drive link?
The file exceeded Gmail’s comfortable attachment handling. Compress the PDF smaller if you need a real attachment, especially for confidential documents.
Does Outlook have the same PDF size limit as Gmail?
Not always. Consumer limits are often similar in magnitude, but Microsoft 365 tenants and on-prem Exchange frequently enforce lower organizational caps.
Is it safe to compress email PDFs with LokaPDF?
Compression runs in your browser by design — LokaPDF does not upload your file content for that step. You still send the final attachment through your mail provider as usual.
Try it now: Open Compress PDF →