Scan documents to PDF with your phone (clean results)

Phone scans often fail in two ways: they’re blurry, or they’re huge. The goal isn’t “maximum photo quality” — it’s a PDF that’s readable at 100% zoom, cropped straight, and small enough for email and portals.

A reliable scan pipeline looks like this:

1. Capture pages with good lighting and stable focus.
2. Crop/straighten so every page is clean.
3. Build a multi-page PDF with consistent page size and sensible quality.
4. Compress once if you must hit a strict limit (2 MB / 5 MB / 10 MB).

Most problems happen when people try to “compress their way out” of a bad scan.

If your scans look muddy or text seems fuzzy, lighting is usually the root cause. A simple setup that works:

• Use window daylight when possible (bright and even).
• Avoid harsh overhead shadows from your hands/phone.
• For glossy pages (IDs, laminated docs): tilt the document slightly so reflections move away from the text.

Better lighting often lets your camera choose a faster shutter speed, which reduces motion blur.

For most text documents, grayscale scans are smaller and can actually look cleaner. Use color only when it carries meaning (colored stamps, highlights, or diagrams). If you’re hitting a strict size limit, switching from color to grayscale is one of the safest “big wins”.

Scans often include addresses, IDs, signatures, and financial details. When you convert images to PDF or compress a PDF locally in your browser, the files are not uploaded to a server. That’s a simple way to reduce exposure while still getting a clean, shareable result.

These are small adjustments with big payoff:

• Use bright light: bad light forces the camera to use slower shutter speed and higher noise.
• Avoid glare on IDs/laminated pages: rotate the document slightly relative to the light source.
• Don’t use digital zoom: move closer instead.
• Keep the paper flat: books/wrinkles create blur near edges.

If you have photos (JPG/PNG/WebP), you can build a clean PDF locally in your browser: reorder, rotate, choose A4/Letter, and export. Local processing is privacy-friendly because files are not uploaded.

Scan PDFs are image-heavy, so shrinking them usually means fewer pixels. Try these in order:

• Grayscale for text-only pages.
• Slightly lower export quality (stop as soon as text remains crisp).
• Compress once and verify the smallest text after compression.

If you’re far above the limit, the right fix is often to re-export the images at a sensible size/quality rather than compressing aggressively.

If your scan app exported multiple PDFs (or you scanned different document groups), merge them in the correct order and do one quick scroll to confirm nothing is missing.

If you’re scanning something important, don’t delete the source images right away. If a portal rejects the file or you notice a blurry page later, having the originals lets you fix it quickly without re-capturing everything.

Why are scan PDFs so large?
Because each page is an image. More resolution means more pixels and bigger files.

Should I scan in color?
Only when color carries meaning. For text documents, grayscale is often smaller and clearer.

Can compression fix blur?
No. Compression only trades size for detail. If text is blurry, re-scan with better lighting and focus.

Compress before or after merging?
Merge first, then compress the final PDF.

Is local processing safer?
For sensitive documents, yes — it avoids uploading files to third-party servers.