
The report is finished, the recipient is waiting, and the email client says the attachment is too large. You need a 40 MB PDF to fit somewhere between 10 and 25 megabytes — depending on the mail server on the other end — in the next ten minutes, without turning every page into a blurry mess.
The good news is that reducing a PDF’s size for email is a solved problem with a predictable method — if you understand what actually makes the file large and which parts of it compression is allowed to touch. Most oversized PDFs are large for one or two reasons, and fixing the right one takes seconds.
In this guide you will learn why PDFs balloon in the first place, what compression genuinely removes versus what it quietly damages, realistic size targets for email, how to shrink a file step by step, and when splitting the document is the better answer than shrinking it further.
Why your PDF is larger than it has any right to be
Before touching any setting, it helps to know where the bytes live. Oversized PDFs almost always fall into one of these categories:
- Scanned documents. A 60-page scan at 300 or 600 DPI carries a full-resolution image per page — contracts, invoices and archive dumps arriving at 80–200 MB with no text layer to show for it.
- Embedded photographs. Reports and brochures with full-resolution camera photos, often thousands of pixels wide for a page slot that displays them at a fraction of that.
- Accumulated junk. Files edited, printed to PDF and re-saved several times can carry orphaned objects, unused font subsets, duplicated images and metadata from earlier versions.
- Nothing obviously wrong. A 200-page document with figures is legitimately several megabytes; you are fighting length, not bloat.
A quick diagnostic saves guessing: check the file size, then flick through the pages. If it is a scan, images are the bulk. If it is a photo-heavy report, the photos are the bulk. If it is a long text document, you are fighting length, not bloat — and your target should be realistic.
What compression actually removes — and what it keeps

PDF compression works on three main fronts, and understanding them tells you what result to expect.
Image downsampling and recompression. Every embedded image can be resampled to a lower resolution and re-encoded at a lower quality. This is where most of the savings usually come from. A 300 DPI scan downsamples to 150 DPI with barely perceptible loss for screen reading; the same reduction on fine print starts to blur. The first steps down from maximum JPEG quality cost almost nothing; deeper steps cost more and more.
Structure cleanup. Removing unused objects, redundant font data and duplicated streams. This is pure win — bytes deleted without touching anything visible. In files re-saved repeatedly it can be worth more.
What compression must not touch. The text layer stays vector: letters remain selectable and sharp at any zoom, however small the file gets. Page size, count and layout are preserved.
That last point is the important one for email: small does not have to mean blurry, because the text in your PDF is not made of pixels. In a text-based document you can compress aggressively and the words stay perfectly sharp; only the embedded images change. In a scan there is no text layer — the whole page is an image — so every size reduction costs visible sharpness. This is why the same “medium” setting can look great on one document and soft on another.
What most people get wrong
The most common mistake is compressing until the number looks good instead of until the document looks good. People drag the quality slider to the minimum, hit the attachment limit, and send a file they have not opened. Then the recipient reports that the appendix photos are mush.
The misconception underneath is that compression quality is a property of the setting. It is a property of the *setting plus the document*. The same setting that shrinks a photo-free contract by 70% with zero visible change will destroy a scanned drawing.
What to do instead: compress in stages, checking at each stage. Pick a target based on how the document will be read — if the recipient will zoom into detail, compress conservatively and consider splitting instead. And always open the compressed file and check the two or three most demanding pages: the smallest body text, the most detailed photo, the densest table.
The second common mistake is obsessing over megabytes when the limit is generous. Many mail systems accept 20–25 MB attachments today. If your file is 24 MB and the limit is 25, a light compression pass is enough — do not over-shrink to fix a one-megabyte problem.
Compress, split, or link: choosing the right approach
When a file will not fit, you have three real options. None is universally best.
| Approach | Result | Best for | Watch out for |
|---|---|---|---|
| Compress the whole file | One smaller PDF | Most reports, contracts, scans | Over-compression of image-heavy pages |
| Split by size | Several small parts | Very large scans and appendices | Recipient must open multiple files |
| Link instead of attach | No attachment at all | Very large files, many recipients | Link rot; access must be arranged |
Compress when the file is moderately over the limit and the content tolerates image reduction — the everyday case, and what our Compress PDF tool does. It usually turns a 40 MB report into the 5–15 MB range, depending on how much of it is imagery.
Split when the file is far over the limit, or its images must stay sharp. A 150 MB scan will not compress to email size without becoming unreadable; cutting it into 10 MB parts with [Split PDF by File Size](/pdf/split-pdf-by-size/) delivers the same pages at full quality. Name the parts clearly — “Report-part1of3” — so the recipient knows nothing is missing.
Link when size is genuinely extreme or the document goes to many people. Links expire, hosts go down, and recipients lose the offline copy. For formal or contractual documents an attachment is usually still expected.
A useful rule of thumb: if you must compress below roughly 50% of the original and the document is image-heavy, switch to splitting. You are about to trade away quality you will want back.
How to reduce a PDF file size for email, step by step
- Find out the actual limit. Check both ends: your own outgoing limit and the recipient’s. When unsure, assume 20 MB and leave headroom — mail servers count the encoded size, which runs slightly above the raw file.
- Check your file’s current size. In Explorer or Finder, check the file’s properties and note the page count — a 60 MB file with 20 pages is photographs; one with 200 pages is probably a scan.
- Make a copy and open our free Compress PDF tool in your browser. The file loads locally; it is not uploaded to any server.
- Choose a level by content, not habit. Text documents with a few figures: aggressive. Mixed reports: moderate. Scans and photo books: light, or skip to splitting.
- Compress and note the result, then compare it against your limit. Comfortably under? Move to verification. Not there yet? Try the next level down or reconsider splitting.
- Verify the output before attaching. Open the compressed file and check the worst-case pages: the smallest text, the most detailed image, the densest table. If a critical page degraded, back off one level — or split the document instead.
- Attach normally. The compressed file goes into the email like any other attachment.
- If you split instead, name and order the parts. Use sequential names, mention the part count in the message body, and check each part opens before sending.
For documents destined for a website or portal rather than an email attachment, the Optimize PDF for Web tool is tuned for that job: it targets fast loading rather than a hard size ceiling, using linearised output so the first page appears before the whole file arrives.
When compression is not enough
Some documents hit a floor. Recognising it early saves you from sending something unreadable.
Scanned archives. A 300-page scan at the quality floor will still be tens of megabytes. Split it, or send it in chapters — no setting makes a scan both tiny and sharp.
Documents with minimum-quality requirements. Colour-critical proofs, engineering drawings with fine line work and legal documents with fine print have a practical quality floor. Find it by compressing once at each level and reading the result, not by trusting the labels.
Unknown recipient limits. If their server rejects the file, compression cannot fix a limit you cannot see. Conservative 10 MB parts clear almost any mail system, making splitting the reliable fallback.
And remember the honest alternative: for documents that will only ever be read on a screen, sending a link sidesteps the attachment limit entirely.
Common mistakes to avoid
- Compressing blind. Never send a compressed file you have not opened. Check the pages with the smallest text and the most detail.
- Choosing the smallest setting by default. Match the level to the content; a text-heavy document barely benefits from light settings, and a scan suffers badly at aggressive ones.
- Ignoring the encoded size. Email transfers base64-encoded attachments, roughly a third larger than the file on disk. A 24 MB file can exceed a 25 MB server limit. Leave headroom.
- Over-shrinking instead of splitting. When quality starts to fall, cut the document into parts — full quality in several files beats one blurry file.
- Sending unnamed split parts. Name them “part1of3” style and say so in the message, or recipients will think pages are missing.
- Forgetting the original, or re-compressing a compressed file. Keep the uncompressed master and always compress from it — each extra pass loses more.
Final takeaway
Getting a PDF under an email attachment limit is a three-move sequence: learn the real limit, compress at a level matched to the document’s content, then verify the pages that matter before attaching. Text stays sharp through compression — it is the images that trade size for detail — so the question is always how much imagery you have. When a file is too big to shrink honestly, split it into named parts and send everything at full quality.
The tools below do the whole job in your browser, with the original file untouched on your disk.
Try it with the free tools
Shrinking a PDF for email takes a minute, and nothing is uploaded — the compressed file is produced and saved on your own device.
- Compress PDF — bring a document down under your attachment limit at a quality level you choose.
- Split PDF by File Size — cut an oversized file into email-sized parts that keep full quality.
- Optimize PDF for Web — prepare a fast-loading version for sharing by link instead of attachment.
What size can I realistically get a PDF down to?
u003cp>It depends on content, not on the tool. A text document with a few figures can shrink dramatically with no visible change, because text is vector and compresses almost freely. A scan shrinks in proportion to its images. A practical goal is under 10–15 MB; below roughly 50% of the original, image-heavy files should usually be split rather than compressed further.u003c/p>
Will compressing a PDF make the text blurry?
u003cp>No. Text in a PDF is stored as vector data, not pixels, so it stays sharp at any compression level and any zoom. Compression affects embedded images, which are resampled and re-encoded at lower quality. Only scanned documents — where every page is one big image — see their text blur.u003c/p>
How do I check whether my compressed PDF is still good quality?
u003cp>Open the compressed file and inspect the most demanding pages: the page with the smallest body text, the most detailed photograph, and the densest table. Compare each against the same page in the original. Those three checks catch virtually every compression problem before the recipient sees it. Do this every time — settings behave differently on different documents.u003c/p>
Should I compress my PDF or split it into several files?
u003cp>Compress when the file is moderately over the limit and the content tolerates image reduction — the common case for reports and contracts. Split when the file is far over the limit or its images must stay sharp, such as scanned drawings or photo collections. Splitting delivers full quality in several email-sized parts; name them clearly and note the count in your message.u003c/p>
Why was my attachment rejected even though it was under the stated limit?
u003cp>Most likely because email transfers attachments in base64 encoding, which adds roughly a third to the file’s on-disk size, and servers usually count the encoded size. A 24 MB file can therefore exceed a 25 MB limit. Leave headroom — target comfortably under the limit rather than right at it.u003c/p>