Home/Guides/PDF
📠PDF

Why a Scanned PDF Won't Get Smaller (and the Three Changes That Actually Work)

A scan is a stack of photographs, so structural compression does nothing. Here is what the scanner wrote, the three levers that shrink it 10–30×, and a worked example.

7 min read

You compressed it and it barely moved

A scanned PDF is the file people most often need to shrink and the one that most often refuses. You run it through a compressor, it drops from 18 MB to 16 MB, and the upload form still says no. The reason is that a scan is not a document in the usual sense: it is a stack of photographs of paper, one per page, and photographs only get smaller when you throw pixels away. This guide explains what a scanner actually writes into the file, why generic compression does nothing, and the specific changes that do work — with numbers, so you can predict the result before you start.

What a scanner puts in a PDF

A flatbed or sheet-fed scanner set to 300 dpi turns an A4 page into an image of about 2,480 × 3,508 pixels — 8.7 million of them. In colour, uncompressed, that is 26 MB per page. The scanner software then encodes the image, and the choice it makes decides everything that follows:

Encoding the scanner usedPer A4 page at 300 dpiHow to tellWhat compression can gain
JPEG, high quality (most home scanners, phone scan apps)1.5–4 MBPhoto-like, slight smudging around letters at high zoomA lot — quality is set far higher than a document needs
JPEG, medium quality400–900 KBVisible blockiness at 300% zoomSome — mainly by lowering resolution
Lossless (Flate/ZIP or uncompressed) — office copiers, 'archive' modes5–25 MBFile size wildly out of proportion to page countEnormous — 10–30× by switching to JPEG
CCITT G4 / JBIG2 (black-and-white fax-style)30–80 KBPure black and white, no greysAlmost none — already the most compact form

Generic PDF compressors that work on the file structure — removing unused objects, deduplicating fonts — cannot touch any of this, because there is no structure to trim: the file is 99% image data. That is why a tool that shrinks a Word-exported PDF by half does nothing for a scan.

The three things that actually shrink a scan

Size of an image page ≈ width × height × bits per pixel × JPEG factor. Each of the three changes below attacks one term. Combined, they routinely turn a 20 MB scan into 1 MB.

  • 1. Lower the resolution. Halving dpi cuts pixels by four. 300 dpi is for OCR and reprinting; 150 dpi is perfectly readable on screen and prints acceptably; 100–120 dpi is fine for a reference copy. This is the single biggest lever — a 300→150 dpi change alone is a 4× reduction.
  • 2. Drop colour. A black-on-white page carries no useful colour. Greyscale stores one channel instead of three, and JPEG compresses greyscale text more efficiently. Expect 40–60% off at the same resolution. Keep colour only for pages where colour carries meaning — stamps, highlighted clauses, photographs of ID cards.
  • 3. Lower JPEG quality. Scanner defaults sit around quality 0.9–0.95, which is wasted on paper. Quality 0.7 is visually identical for text at normal zoom; 0.5–0.6 is where softening becomes noticeable. Going from 0.92 to 0.7 typically halves the size.

On this site, Compress PDF applies levers 1 and 3 (it re-renders each page at the dpi and quality you pick), and Grayscale PDF applies lever 2. Run Grayscale first, then Compress, and you get all three.

Worked example: a 20-page colour scan

StepSettingSizeReduction
Original from scanner300 dpi, colour, JPEG ~0.9222 MB
Grayscale PDF300 dpi, grey11 MB
Compress PDF150 dpi, quality 0.751.6 MB14×
Compress PDF (tighter)110 dpi, quality 0.650.8 MB27×

The 1.6 MB version is indistinguishable from the original at normal reading size and still prints cleanly. The 0.8 MB version is for a 1 MB portal cap; small print goes slightly soft but stays legible.

Things that make scans bigger than they need to be

  • Scanning in colour by habit. Set the scanner to greyscale (or black-and-white for pure text) before scanning; it beats fixing it afterwards.
  • 600 dpi. Nothing on paper needs it except tiny type destined for OCR. It quadruples 300 dpi.
  • Wide margins and blank backs. Pixels of white paper still cost bytes. Crop PDF trims margins; Delete PDF Pages removes blank reverse sides from duplex scans.
  • Phone scan apps' 'enhance' filters add contrast noise that JPEG compresses badly. Turn enhancement off and let the compressor do its job.
  • An OCR text layer adds only a few KB per page — keep it, but note that rasterized compression discards it (see below).

What you lose, and how to keep it

Re-rendering pages removes any invisible OCR text layer the scanner added, so the compressed file is no longer searchable. If you need both small and searchable, compress first, then run OCR on the result in Acrobat, macOS Preview, or Google Drive — OCR works fine at 150 dpi. Form fields and annotations are also flattened into the image; on a scan that is rarely a concern, since a scan has none to begin with.

Frequently asked questions

My scan is already small per page but there are 400 pages. What then?

Multiply your per-page target by the page count and see whether any legible setting reaches it. If not, split the document with Split PDF and upload in parts, or ask the recipient for a larger limit.

Why does black-and-white (1-bit) scanning look worse than greyscale?

It has no anti-aliasing, so letter edges are jagged and pencil marks vanish. It is the smallest option but only suits clean printed text.

Is there a way to compress without losing any quality?

For a scan encoded losslessly, converting to JPEG at quality 0.9 is a 10× gain with no visible change. For a scan already in JPEG, every further reduction costs some detail — the aim is to keep it below what the eye notices.

Does compressing remove the scanner's metadata?

Compress PDF rebuilds the document, so scanner make, model and timestamps in the Info dictionary are dropped. Remove PDF Metadata does this on its own without touching the images.

Can I compress just some pages?

Yes: Split PDF into the heavy pages and the rest, compress only the heavy part, then Merge PDF them back in order.

Is my scan uploaded to a server?

No. Rendering and re-encoding happen in your browser with PDF.js and the Canvas API; the file never leaves your device.

Tools mentioned in this guide