Skip to content
PurePDF HQ
Color theme

How to reduce the size of a scanned PDF and keep it readable

A scanned page is one big picture, so it is usually the file that is too big for the form. We shrank scans of seven kinds of page step by step and had a text reader check each one, to find where readable stops.

By PurePDF HQ. Published . Last updated . 4 min read.

The short answer

Our scans started at 147.7 KB to 571.4 KB a page, at 300 dpi. At 200 KB a page, all 7 stayed readable. At 100 KB, 6 of 7 did. At 50 KB, only 3, and at 25 KB, 2: the forms and receipts with large, sparse type.

What decides it is not the file size but how many pixels are left for each inch of the page. Every page we tested read cleanly at 87 dpi or more. The highest resolution at which any page failed was 82 dpi. So the rule of thumb: shrink a scan as far as you like, as long as its picture keeps about 87 pixels per inch, and a bit more for small print.

Smallest readable size we reached, per pageThe smallest output each page reached while OCR still read it: Book page 172.1 KB, Letter 83.1 KB, Bank-style statement 83.3 KB, Receipt 20.4 KB, Small print 88.5 KB, Form 20.3 KB, Invoice 43.2 KB.Form20.3 KBReceipt20.4 KBInvoice43.2 KBLetter83.1 KBBank-style statement83.3 KBSmall print88.5 KBBook page172.1 KB
Smallest readable size we reached, per page

Lossless compression does nothing to a scan

The lossless rewrite saved nothing on 8 of the 8 scans. That is expected: a scan is a JPEG picture already, and a lossless tool cannot touch the picture without decoding it. Any real saving on a scan comes from making the picture smaller, which is a loss, so the only question is how much loss the page can take.

Every page, every size

Each scan at each target: size, picture resolution and the OCR error rate
PageTargetSizeResolutionError rateReadable
Book pageLossless571.4 KB300 dpi0.0%Yes
Book page200 KB172.1 KB117 dpi0.0%Yes
Book page100 KB82.2 KB74 dpi5.8%No
Book page50 KB41.9 KB47 dpi57.3%No
Book page25 KB24 KB37 dpi68.4%No
LetterLossless440.5 KB300 dpi0.0%Yes
Letter200 KB162.2 KB142 dpi0.0%Yes
Letter100 KB83.1 KB87 dpi0.4%Yes
Letter50 KB43.5 KB56 dpi36.9%No
Letter25 KB23.1 KB37 dpi70.5%No
Two-column pageLossless541.8 KB300 dpi69.3%Not scored
Two-column page200 KB170 KB122 dpi69.3%Not scored
Two-column page100 KB85 KB75 dpi71.7%Not scored
Two-column page50 KB39.7 KB48 dpi71.7%Not scored
Two-column page25 KB20.8 KB37 dpi73.1%Not scored
Bank-style statementLossless261.7 KB300 dpi0.0%Yes
Bank-style statement200 KB151.5 KB215 dpi0.0%Yes
Bank-style statement100 KB83.3 KB133 dpi0.0%Yes
Bank-style statement50 KB42.5 KB82 dpi4.2%No
Bank-style statement25 KB23.2 KB51 dpi66.5%No
ReceiptLossless147.7 KB300 dpi0.0%Yes
Receipt200 KB147.7 KB300 dpi0.0%Yes
Receipt100 KB86.2 KB243 dpi0.0%Yes
Receipt50 KB37.5 KB146 dpi0.0%Yes
Receipt25 KB20.4 KB92 dpi0.8%Yes
Small printLossless346.5 KB300 dpi0.0%Yes
Small print200 KB159.6 KB171 dpi0.0%Yes
Small print100 KB88.5 KB107 dpi0.4%Yes
Small print50 KB39.4 KB68 dpi48.7%No
Small print25 KB19 KB45 dpi74.3%No
FormLossless151.7 KB300 dpi0.0%Yes
Form200 KB151.7 KB300 dpi0.0%Yes
Form100 KB78.9 KB240 dpi0.0%Yes
Form50 KB37.9 KB152 dpi0.0%Yes
Form25 KB20.3 KB95 dpi0.0%Yes
InvoiceLossless210.7 KB300 dpi0.0%Yes
Invoice200 KB192.7 KB288 dpi0.6%Yes
Invoice100 KB78.9 KB161 dpi0.8%Yes
Invoice50 KB43.2 KB101 dpi0.4%Yes
Invoice25 KB21.7 KB62 dpi30.1%No

Error rate is the share of characters the text reader got wrong, against the exact text we drew on the page. At or under 1% we call a page readable: at most one slip in a hundred characters.

What the resolution means in pixels

Our scans are US Letter pages at 300 dpi, which is 2,550 × 3,300 pixels. To reach a size, the engine first lowers the JPEG quality and then scales the picture down. The letter at 100 KB came out at 741 × 959 pixels, which is 87 dpi across the page, and every character was still read. At 50 KB it was 478 × 619, or 56 dpi, and the reader lost 36.9% of the characters.

So 87 dpi, less than a third of what the scanner captured in each direction, was enough for every typed page we tried. A clean, typed page needs surprisingly little, and it goes quickly once it drops below that.

Readability falls off a cliff

The drop is not gradual. The small-print page went from 0.4% wrong at 100 KB to 48.7% wrong at 50 KB. The statement went from 0.0% to 4.2% between the same two sizes. In between there is no setting that is a little bit worse: a page reads, or it starts to turn into guesses.

That is a reason to leave a margin. If a form allows 200 KB and your page reads fine at 100 KB, send it at the larger size. Nobody will thank you for the smaller file, and someone may have to squint at it.

Dense pages need more bytes than sparse ones

The book page and the letter are full of body text. The smallest readable files we reached for them were 83.1 KB to 172.1 KB. The form and the receipt have less text in larger type, and they still read cleanly at 20.3 KB to 20.4 KB. Small print needed the most resolution: it passed at 107 dpi and failed at 68.

The invoice sat between them. It has a table of short lines and figures, and it still read cleanly at 43.2 KB, but at the next step down the reader got 30.1% of its characters wrong. On a page of figures that matters most: a misread word can often be guessed from the words around it, a misread digit cannot.

So before you type a size, look at the page. A certificate with a few lines and a seal can go very small. A dense statement or a page of fine print needs room.

Step by step

  • Scan in grayscale unless colour matters. A colour picture has three channels where grayscale has one, and a black-on-white page gains nothing from the other two.
  • Scan at 200 or 300 dpi, well above the 87 dpi our pages needed. You can always shrink later; you cannot add back detail the scanner did not capture.
  • Compress to the size the form asks for. For a one-page text document, a target of 100 KB or more keeps it readable in our tests.
  • Open the result and read the smallest text on the page at 100% zoom. If you can read it, so can the person at the other end.
  • If the form's limit is too small for a dense page, check whether it takes several files, and split the scan page by page.

How we measured

The pages come from our own test set: made-up text drawn at 300 dpi in common fonts, each saved as one grayscale JPEG on a Letter page, the way a scanner writes it. Because we drew the text, we know exactly what each page says. We ran the site's own compress code in Node 22.23.4 on November 11, 2026, at each target, then drew each result at 300 dpi and read it with Tesseract, the same text reader and English model our OCR tool ships. A two-column page is left out of the figures, because the reader takes its lines across both columns even before compression.

A text reader is stricter than a person in some ways and more forgiving in others, so treat these as a guide, not a guarantee. The bench script is in our repository.

Tools used in this guide

Sources

  1. tesseract.js 7.0.0. Project Naptha, on GitHub, read November 11, 2026.
  2. tessdata_fast, English model. Tesseract OCR, on GitHub, read November 11, 2026.