How to Reduce PDF Size Without Losing Quality

Why PDFs get so big in the first place

The single biggest cause of an oversized PDF is embedded images, and scanned documents are the worst offenders — a scanner or phone camera typically captures each page as a full-resolution photograph, so a 20-page scanned contract can easily be 10 times larger than the same 20 pages of native, typed text. Embedded fonts, unused objects left over from editing, and (less commonly) embedded video or audio can add extra weight too, but images are almost always where the bulk of the file size actually lives.

Quick fixes that don't sacrifice quality

Before reaching for a compression tool, a few free adjustments can shrink a PDF without touching quality at all: remove any blank or unnecessary pages before exporting, check for accidentally embedded high-resolution images that aren't actually needed at that resolution, and use your source application's own "reduced file size" or "optimize" export option if it has one — Word, Google Docs, and Preview on macOS all offer some version of this, and it often trims meaningful size before you even touch a dedicated compressor.

If a PDF was created by "printing" a webpage or document to PDF rather than exporting it directly, re-exporting from the original source is frequently smaller than the printed version, since the print pipeline sometimes rasterizes content that could have stayed as clean vector text.

Where quality loss actually comes from

Real quality loss happens specifically when an embedded image is recompressed at a lower resolution or a more aggressive lossy setting than the content needs — text and line art suffer the most since compression artifacts show up as fuzziness right around sharp edges. The practical sweet spot is roughly 150 DPI (dots per inch) for anything that will mostly be viewed on a screen, and around 300 DPI if the document needs to print cleanly; scanned pages captured at 600 DPI or higher are almost always overkill and can be safely down-sampled without a visible difference in normal use.

Using a dedicated PDF compressor

Once the easy wins are done, a dedicated compressor gets you the rest of the way. Nonkera's PDF compressor works entirely in your browser — nothing is uploaded to a server — by re-rendering each page as a single optimized image at the resolution and quality level you pick, then rebuilding the PDF from those images. That approach is what makes it reliable on any PDF and especially effective on scans, but it comes with one trade-off worth knowing up front: the compressed file's text is no longer selectable or searchable, since every page becomes a picture of itself rather than a page with live text on it. For a scanned document that changes nothing (a scan was already just a photograph of a page); for a document with real, selectable text, it's worth keeping the original around alongside the smaller copy.

If you're building the PDF from images

If you're creating a PDF by converting a batch of photos or scanned pages into one document, it's more effective to compress the source images first, before combining them, rather than compressing the finished PDF afterward — you get more control over each individual image's quality that way, and the resulting PDF starts small instead of needing to be shrunk down after the fact.

Choosing the right compression level for the job

The right amount of compression depends entirely on where the file is headed. An email attachment or a form upload with a strict size limit can usually handle fairly aggressive compression, since the recipient just needs to read it, not scrutinize fine print. A document you're archiving long-term or sending to a print shop is worth compressing more conservatively, keeping resolution higher so nothing looks soft when it's zoomed in or printed. When in doubt, compress at a moderate setting first and open the result to check readability before sending it anywhere important.

Common mistakes that make PDFs bigger than they need to be

A few habits reliably produce oversized PDFs without anyone intending it. Scanning at the printer or scanner's default "maximum quality" setting is the most common one — most scanners default to 600 DPI or higher, far beyond what's needed for a document that will only ever be read on a screen or printed once. Re-scanning a document instead of exporting it directly from its original source is another: if a Word document, spreadsheet, or webpage exists as an editable file somewhere, exporting straight to PDF from that source almost always produces a smaller, sharper result than printing a physical copy and scanning it back in.

Combining several already-large PDFs into one without compressing any of them first is a third common trap — merging doesn't add overhead on its own, but it also doesn't fix bloat that was already there, so a bundle of five oversized scans becomes one very oversized document instead of five slightly-easier-to-manage ones. Compressing each file individually before merging, or compressing the combined result afterward, avoids ending up with an unnecessarily large final document either way — whichever order fits more naturally into your existing workflow for assembling the file.