The attachment bounces, or your email client just refuses to send in the first place. Before you reach for a file-sharing link or start a whole new workflow, it's worth trying the two fixes that solve this in under a minute: shrinking the file, or breaking it into pieces.
Both work entirely in your browser — no upload, no signup — which matters here more than usual, since oversized PDFs tend to be exactly the documents (contracts, scans, statements) you'd least want sitting on a third-party server.
Know your provider's real limit first
Email attachment limits are lower than most people guess, and they're enforced inconsistently:
- Gmail — 25 MB per message, and that includes the text of the email itself, not just the attachment.
- Outlook.com — 20 MB.
- Corporate mail servers — often stricter than both, frequently 10 MB or even 5 MB, set by policy rather than any technical necessity.
Two subtleties trip people up. First, the limit that matters is often the recipient's, not yours: you can send a 24 MB attachment fine and still have it bounce off their corporate server. Second, an attachment grows in transit — email encoding adds roughly a third to the size of the file, so a 19 MB PDF may arrive as a 25 MB message. If you're aiming at a 25 MB ceiling, keep the file itself under about 18 MB to be safe.
Checking the actual limit first can save you from compressing a file that was never the problem — occasionally it's an attachment-type restriction or a full mailbox on the other end, not size at all.
Option 1: Compress it
Most oversized PDFs are bloated by images embedded far larger than they're ever displayed at — a photo placed at business-card size but stored at full camera resolution. Compress PDF detects each image's true on-page size and re-encodes it accordingly, and for most documents this alone is enough to clear an email limit without a visible quality difference. It's the right first move almost every time.
- Open Compress PDF and drop in your PDF.
- Pick a level: Low only strips metadata and tidies the file structure (images untouched), Medium recompresses images at balanced quality, High squeezes hardest for the smallest possible file.
- Compress, check the reported size, and download the result.
For email purposes, start at Medium — it's where the image savings live, and the quality trade-off isn't visible at normal reading size. Drop to High only if Medium doesn't get you under the limit. Check the final size against the recipient's ceiling before attaching, not after the bounce.
Two things worth knowing. Compression rebuilds the file, so if your PDF was password-protected, the compressed copy won't be — re-protect it with Protect PDF before sending if that matters. And since a smaller copy is being created anyway, keep the original for your own records; the compressed version is what travels, not what you archive.
Option 2: Split it into parts
If your PDF is huge because it genuinely has a lot of content — a long report, a scanned book — rather than because of oversized images, compression only goes so far. Split PDF breaks the file into smaller pieces by page range, so instead of one attachment that won't send, you send three or four that will.
- Open Split PDF and drop in your PDF.
- Choose how to split: fixed page ranges you specify (say, 1–20, 21–40, 41–60), every N pages, or one file per page.
- Split and download the parts as a .zip, then attach them across separate emails.
When you're splitting purely for transport, keep the parts roughly equal in size and tell the recipient the order — "3 emails: chapters 1–3, 4–6, 7–9" turns a strange trickle of attachments into something obviously deliberate. They can rejoin them later with Merge PDF if they want the original back as one file.
Which one should you try first?
Compress first — it's a single click and doesn't change how many files the recipient gets. Only split if compression alone doesn't get you under the limit, or if the recipient would genuinely benefit from receiving the document in smaller, separately-addressable chunks (like individual chapters).
The two also combine cleanly: compress to shrink the bulk, then split whatever remains if you're still over. That one-two handles everything short of truly enormous scans.
Why PDFs end up huge in the first place
Knowing what's eating the megabytes tells you which fix will work before you try either. The overwhelming cause is images stored at far higher resolution than they're displayed at: a page with a photo placed at a few centimeters wide can still carry the full ten-megapixel original, because PDFs embed the complete image and only show a crop of it. Multiply that by a twenty-page report and the file balloons past every mail limit in existence.
The second common cause is scanned pages. A scan isn't text — every page is a full-page photograph at whatever DPI the scanner was set to. Scan at 600 DPI in color where 200–300 DPI in grayscale would have been plenty, and a ten-page document easily lands at 100+ MB. If you control the scanning, dialing those two settings down at the source is the cheapest fix of all: no compression needed, because the file was never big.
What's not usually the problem: plain text. A hundred pages of pure text with standard fonts is a few hundred kilobytes. If a PDF is enormous, it's carrying images — which is exactly why image re-encoding (compressing at Medium or High) is where the savings come from.
When a link is the better answer anyway
Sometimes attaching is the wrong goal, not the wrong method. If the PDF is over 100 MB (the per-file ceiling for browser-based tools like these, set by device memory rather than any server quota), if the recipient's server limit is unknown or tiny, or if you expect to send updated versions repeatedly, upload the file to whatever cloud storage you already use and send a link instead. The trade-offs are real — the file now lives on someone else's infrastructure and the link is the access control — but for large documents it's often the pragmatic choice.
For everything under that bar, though, a compressed PDF sent as a plain attachment is hard to beat: it arrives as an email, not an account sign-up; it works offline; and it opens without any expiry date. Getting there is usually just one click of compression away.