Why is my PDF so large? 6 real ways to shrink it (with trade-offs)

A three-page PDF has no business being 40 MB — until it is, and your email bounces it back. Before you compress blindly, it helps to know why a PDF got big in the first place, because the reason points to the fix. Sometimes the right move is to compress; sometimes it's to not include a giant image at all.

Here's what actually makes PDFs large, followed by six ways to bring the size down, honestly labelled with what each one costs you.

What actually makes a PDF big

Text is tiny. A hundred pages of pure text is a rounding error next to a single high-resolution photo. So when a PDF is large, the weight is almost always somewhere other than the words:

• Images. Photos and graphics saved at full camera resolution carry far more data than the page can even display. This is the number-one cause.
• Scanned pages. A scan isn't text — it's a full-page image. A scanned contract is basically a stack of photos, which is why scans balloon so fast.
• Embedded fonts. PDFs bundle fonts so they look identical everywhere. Usually small, but several fancy fonts add up.
• Leftover data. Revision history, saved form entries, hidden layers and metadata all ride along and rarely get cleaned out.

6 ways to reduce the size

1. Compress it (the default, best all-rounder)

A compressor re-encodes the images inside the PDF at a sensible resolution and quality. For the typical document — a report with a few images, or a scan — this cuts the size dramatically with little or no visible change on screen. It's the first thing to try. Trade-off: at aggressive settings, photos and fine detail can soften; match the level to how the file will be used (screen vs print).

You can do this in your browser with RaptorPDF's compress tool — no upload, so even a sensitive PDF stays on your device.

2. Lower the resolution of a scan before you make the PDF

If you control the scan, scanning at 150–200 DPI instead of 600 produces a perfectly readable document at a fraction of the size. Trade-off: less useful if you need to zoom into fine print or archive at high fidelity — but for sharing and reading, it's plenty.

3. Split out the pages you actually need

Often you don't need to send the whole 80-page file — just pages 3 to 7. Splitting or deleting pages you don't need is the cleanest size reduction there is, because you're removing data rather than degrading it. Trade-off: none, as long as the recipient really only needs the subset.

4. Re-export from the source instead of the PDF

If the PDF came from Word, Google Docs, or a design tool, exporting again with a "smaller file / web" or "reduced size" option often beats compressing the finished PDF, because the source app can down-sample images intelligently. Trade-off: you need the original file, and it's an extra step.

5. Flatten or remove what you can't see

Form fields, annotations, and multiple layers add weight. Flattening the document (merging everything into the page) and stripping unnecessary metadata can trim a surprising amount from form-heavy or heavily edited files. Trade-off: flattening makes form fields no longer editable — do it on a copy, once the form is final.

6. Convert image-only pages to real text (OCR) — sometimes

If a scan is enormous and you mainly need the words, running OCR and keeping the recognised text (instead of the page images) can shrink it massively. Trade-off: you lose the exact visual of the original, and OCR isn't perfect — best when the content matters more than the look.

How small do you actually need it?

Pick the target before you start, so you don't over-compress:

• Email attachments: most providers cap at 20–25 MB. Getting comfortably under that is usually enough — you don't need to crush it to 1 MB.
• Web upload / forms: often 2–10 MB limits. A single compression pass usually clears these.
• Print: keep quality high — don't over-compress a file that's going to a printer.

And one habit that saves grief: keep the original. Compress a copy, so you can always redo it at a different level. Compressing an already-compressed file repeatedly is how you end up with mush.

Frequently asked questions

Keep reading