Document Workflow
Smaller Scanned PDFs: Keep Text Readable and Attachments Manageable
A smaller file is useful only if it remains complete and readable. Build a delivery profile around the destination limit, then verify the difficult pages before processing the archive.

To reduce a scanned PDF, choose an appropriate resolution and colour mode, then adjust compression and inspect the result. Keep the original or a suitable preservation copy. Test small text, faint marks, stamps, images and page completeness before applying the profile to a large batch.
A form is ready to send, but the upload portal refuses the attachment. Scanning again at the highest quality may make the file even larger. Compressing until the limit is met may remove the detail the recipient needs.
Start with the destination and the document. A simple text form, a faded receipt and a colour evidence photograph do not have the same useful settings. The aim is a dependable delivery copy, not the smallest file that can be created.
Turn the Destination Limit into a Working Budget
Check the actual limit and accepted format. An email service, web portal and document repository may each enforce different rules. Attachment encoding and message limits can also differ from the size shown for a file on disk, so leave room rather than aiming exactly at a stated maximum.
For a planning example, a portal allowing a 10 MB file with 40 pages gives an average budget of about 0.25 MB per page before allowing for file structure and a safety margin. That is arithmetic, not a promised scan size. A few photo-heavy pages can consume much more than the average.
If the recipient permits separate files, splitting a document into clearly named parts may be more useful than degrading every page. Preserve the order and include a simple part count. Do not split a signed or regulated submission without checking its requirements.
Reduce the Delivery File Without Losing Its Purpose
Use the smallest useful result, rather than the smallest possible file.
01 Capture Detail
Read the Difficult MarksCheck fine type, faint text, stamps, images and annotations.
02 Control the File
Use a Working BudgetBalance image quality, compression and accepted file parts.
03 Check the Handover
Verify Every Intended PageOpen the result, check sequence and test search where required.
Choose Detail and Colour for the Document
For ordinary office text, compare a representative 200 dpi and 300 dpi scan rather than assuming 600 dpi is necessary. Fine print, faint originals and detailed diagrams may need more care. The original’s legibility still places a limit on what scanning can recover.
Doubling resolution in both directions produces four times as many pixels before compression. It does not guarantee a PDF exactly four times larger, because content and compression affect the result. A higher DPI setting should answer a visible need.
Use colour when it carries information, such as coloured annotations, stamps or photographs. Greyscale may be suitable where colour is unnecessary. Black-and-white processing can make a text document compact, but an unsuitable threshold can remove faint marks or fine lines. Inspect those features before choosing it for the batch.
Adjust the Actual Scan Profile
In ScanSnap Home for a computer, open the profile being used and its detailed settings. Image quality is controlled in the Scan settings, while compression for colour or greyscale images is available under File size. The profile selected for the real job matters more than a setting changed in an unused example profile.
Higher compression generally makes the file smaller at the cost of image detail. Change one step, scan the same sample and compare both size and readability. Avoid repeatedly recompressing the only surviving copy, which makes later judgement harder.
A saved OCR text layer can make a scan searchable, but OCR does not prove that the page image is readable or complete. If search is the problem, use the searchable PDF guide. File-size control and text recognition deserve separate checks.

Compare the Difficult Pages, Not Just Page One
Build a short sample containing the smallest type, faintest text, a signature, a stamp, a table and a shaded image. Open the delivery file in an ordinary PDF viewer and inspect at a useful reading scale. Compare against the original, not just against another compressed version.
| Document feature | What can go wrong | Acceptance check |
|---|---|---|
| Small or faint text | Blur, broken characters or disappearing strokes | Read it without guessing |
| Stamps and annotations | Loss of colour meaning or pale marks | Compare with the source |
| Photographs and shaded diagrams | Block artefacts or missing detail | Inspect relevant areas at normal viewing scale |
| Duplex or mixed batches | Missing backs or removed faint pages | Check sequence and page count |
| Searchable text | OCR errors despite a plausible page image | Search a known phrase and inspect the result |
Use the missing scanned pages guide if faint or lightly printed sheets disappear. A smaller PDF obtained by accidentally removing a page is not a successful compression result.
Keep a Preservation Copy and Control Sharing
Where the work requires it, retain a suitable original-quality scan separately from the smaller delivery copy. Name them clearly so the compressed version does not silently replace the master. Preserve the paper where organisational or legal requirements call for it.
For sensitive business or personal documents, use an approved local tool or authorised service rather than uploading them to an unfamiliar compression website. File-size convenience does not establish how another service stores or uses the document.
A NAS can provide an organised home for the master, delivery version and index, with appropriate permissions and backup. The document search and NAS workflow guide explains how to make that archive useful after scanning.
Save the Profile and Verify the Handover
If you already use a ScanSnap iX1600, begin by improving the supported profile and review process. A new scanner does not automatically choose the right compression for a submission portal. For a new purchase, compare the current supported hardware and software requirements for the planned workflow.

Use a named profile for the document and destination. Verify the resulting PDF before scanning the remaining archive.
The finished file should open, read, search where required and contain every intended page. Confirm that the destination accepts it, then record the profile and its intended use. Keep a separate high-detail profile for documents that need it instead of turning one low-size setting into a rule for all scanning.
Frequently Asked Questions
Does a lower DPI always give an acceptable smaller PDF?
No. It may remove small or faint detail. Test representative pages and use the resolution needed for the document.
Will 600 dpi make OCR twice as accurate as 300 dpi?
Do not assume a fixed accuracy gain. Original quality, language, layout and processing matter. Judge a representative result.
Can I make every scan black and white?
Only where the result preserves the information. Faint marks, colour annotations and images may need greyscale or colour.
Why do equally sized pages produce different file sizes?
Content, colour, resolution and compression differ. A photograph can require more data than a mostly empty text form.
Should I delete the larger scan after making a small copy?
Retain a suitable master when the workflow requires it and confirm the delivery copy first. Do not overwrite the only useful version during testing.
What is the final check before sending?
Open the PDF, inspect difficult detail, verify page count and sequence, test search if required, and confirm the destination accepts the file.
