Document Digitisation

300 or 600 dpi for Small-Print Document Scanning?

By Pexatech5 min read

300 dpi is a reasonable setting to assess for ordinary printed documents. When required small print is unclear, compare it with a genuine higher-resolution capture, such as 600 dpi, of the same original. Choose the setting that preserves the details your team needs in the finished files. A larger number alone does not establish a better result.

A tiny decimal point, footnote marker or reference character can matter more than the appearance of the whole page. For a Sydney business commissioning scanning, the useful question is whether that specific detail survives capture and delivery. The comparison below is a proposed buyer method, not a report of Pexatech test results.

Why compare 300 and 600 dpi?

ABBYY's source-image recommendations suggest setting a scanner to 300 dpi, and advise 400–600 dpi for documents in very small fonts — under 10 pt in its guidance — that may not be recognised well at 300 dpi. That is product guidance supporting a comparison, not a universal minimum or a guarantee; your own small print may need checking either side of that threshold. It does not identify the software Pexatech uses.

In a scanning brief, dpi describes the sampling density requested from the scanner. For the resulting raster image, pixels per inch is the more precise image term. Brother explains optical and interpolated resolution by distinguishing detail before software manipulation from resolution enhanced by software. Ask the provider which applies to its proposed setting; this distinction does not verify any particular scanner's ability to resolve your print.

For the same one-inch square of paper, a 300-by-300-pixel capture contains 90,000 pixels. At 600 pixels per inch in both directions, it contains 360,000: twice the samples across and down, or four times as many pixels. This is arithmetic, not a measured quality improvement. It does not mean four times the PDF size, scanning cost or OCR accuracy; compression, colour mode and other processing affect the delivered file.

Make sure the comparison uses two captures

Request two scans of the same selected originals at the proposed settings, subject to suitable handling. A 300 dpi scan enlarged afterwards is a different candidate from a new 600 dpi capture. Keep those labels explicit if both are being assessed.

Adobe's image-resizing explanation distinguishes changing a resolution value without changing the pixel count from resampling, which changes that count. Conventional upsampling adds pixels calculated from existing ones. The practical implication is that a file labelled 600 dpi does not, by itself, show that more detail was measured from the paper.

That does not make all resizing useless. Tesseract's image-quality guidance says resizing can benefit its recognition process. Treat that as an OCR-processing option to test, while keeping it distinct from capturing previously missing source detail.

Ask for the same scanner, page area, colour mode and other image settings where feasible, with differences recorded. If the provider changes the device, brightness, sharpening or compression as well, the result compares two workflows; it does not isolate the effect of resolution. The colour-mode guide covers that separate choice.

Compare the same detail at the same page size

Select pages containing the smallest information people actually need, alongside ordinary pages from the same document group. Identify each detail before viewing the candidate scans. Check whether it can be read on the original; if the source itself is ambiguous, record that instead of making the scan responsible for proving an uncertain reading.

Use the same application and display the same area at a comparable size on screen. Avoid judging one whole-page thumbnail against an enlarged crop of the other. Zoom can help inspect a character, but the zoom percentage is not a capture-resolution measurement. If printing is part of the intended use, compare the proposed files at the required print size too.

Copy this worksheet for each selected page. The rows suggest things to inspect; all result cells are deliberately unfilled. No scans or OCR tests were performed for this article. On a small screen, scroll the table sideways if needed.

Detail to identify on the source Source reading or uncertainty 300 dpi capture 600 dpi capture Final delivery check
Smallest required punctuation, such as a decimal point [Record location and what is visible] [Readable / unclear; observation] [Readable / unclear; observation] [Candidate, file version and observation]
Footnote or superscript marker linked to a passage [Record marker and its context] [Readable / unclear; observation] [Readable / unclear; observation] [Candidate, file version and observation]
Small reference characters that staff must distinguish [Record exact characters or uncertainty] [Readable / unclear; observation] [Readable / unclear; observation] [Candidate, file version and observation]

Add the document ID, page, capture settings, candidate filenames, reviewer and date above the table. Replace these rows with details from your records. A note such as “decimal point visible separately from the adjacent digit” gives a later reviewer more to check than “looks sharper”.

Check what reaches the finished PDF

Ask whether either capture is reduced or otherwise altered during PDF creation. Compare the chosen details again in the final delivery candidate, after the proposed processing. A useful capture comparison cannot settle the delivery choice if a later step removes the detail that justified it.

If the early image is readable but the final version is unclear, investigate that processing step before ordering another scan. Record the actual final file size separately. Use the scanned PDF file-size guide for compression and upload-limit decisions.

When searchable output is required, agree optional OCR separately. For each candidate, test the required reference or passage by searching and copying it, then compare the recognised text with the visible source. Keep the OCR software, language and settings consistent where feasible, and identify manual corrections. A readable small character and a correctly recognised character are two different observations.

Turn the observations into a setting decision

Both candidates meet the requirement: there is no demonstrated reading benefit from 600 dpi for the details checked. Compare the proposed delivery files and quoted work, then choose within your agreed requirements. Keep any untested document groups visible.

Only the 600 dpi candidate preserves a required detail: ask whether that capture and delivery approach can be used for the affected group. Confirm how those documents will be identified and whether mixed settings are feasible, rather than applying the result to every box automatically.

Neither candidate meets the requirement: investigate the source and other capture settings. ABBYY's guidance also describes brightness problems that break up or obscure characters. Increasing resolution alone does not resolve every defect. If the source is already an unclear PDF, use the OCR or rescanning guide to assess the next step.

Keep the worksheet with the agreed specification and name the groups it covers. For a document scanning enquiry, describe the small-print problem and request a comparison before committing to a setting. Confirm feasibility, any additional work and handling arrangements before sharing records. The wider quality checklist covers completeness and delivery acceptance once this narrower choice is settled.

Discuss the small details your scans must preserve

Describe the documents and the print people need to read. Ask whether a paired capture comparison can be scoped, and confirm suitability and handling before sharing records.

Discuss Document Scanning

Related Articles

Scanned PDF File Size: What to Agree Before Scanning

Document Digitisation · 5 min read

Document Scanning Quality Checks for Australian Buyers

Document Digitisation · 8 min read

Do Your Existing PDFs Need OCR or Rescanning?

Document Digitisation · 6 min read