2026-03-22 · 6 min read

Compress a PDF Without Ruining Scanned Text

Compression is not a single button that always “makes any PDF smaller.” Most of the savings come from shrinking embedded images. Text-heavy, vector-based PDFs barely move. Giant phone scans shrink a lot—sometimes too much, until letters look soft or watercolor-like. The real goal is the smallest file that still passes a human eye and, when relevant, a portal’s automated checks.

Measure first

Note the current size and the limit you must hit. Email attachments often sit around 10–25MB. Many government and HR forms sit at 2–5MB. Some learning platforms allow more. If you are already under the limit with readable pages, stop. Extra compression only adds risk. Write the limit next to the filename so you do not keep squeezing “just in case.”

What is making the file large?

Open the PDF and skim for full-page photos, high-DPI scans, or embedded screenshots. A 20-page report of selectable text may be under 1MB. A three-page pack with two color passport photos can be 15MB. Knowing the culprit tells you whether to compress the whole file, re-export one photo, or rescan at a saner DPI.

Choose a sensible level

Start with a medium setting in Compress PDF. Download the result, open page 1 at 100% zoom, and read a full paragraph—especially small print on IDs, stamps, and signatures. If edges stay crisp and contrast is acceptable, try a stronger pass only if you still exceed the cap. Jumping straight to maximum compression is how people ruin scans they cannot easily recreate.

Scans vs born-digital files

Scans respond well to careful image compression because they are mostly pixels. Born-digital exports from Word or Google Docs are often already efficient; size problems there usually come from embedded screenshots or “print to PDF” producing page bitmaps. Do not flatten a crisp digital report into mush just because a compressor is available. Sometimes the better fix is re-exporting from the source with “best for electronic distribution,” or removing unused high-resolution images in the Word file and converting again with Word to PDF.

DPI reality check

For text documents, 150–200 DPI is often enough for screen review. 300 DPI helps when you need sharper print. 600 DPI phone scans of forms rarely improve OCR enough to justify multi‑megabyte pages. If compression keeps failing to hit a 2MB cap, reshoot or rescan at a moderate DPI, then rebuild the pack with Merge PDF.

When compression fails to help

In those cases, split the pack with Split PDF, replace one oversized photo, convert photos to JPEG with reasonable quality before building the PDF, or ask the recipient whether attachments can be sent as separate files. Compression cannot invent a new structure—it only reduces what is already embedded.

Special cases: IDs, signatures, and forms

Identity pages and wet-ink signatures are the first places quality loss shows. After any strong compress pass, inspect MRZ lines, hologram areas (as much as a flat scan shows), and signature strokes. If a signed contract blurs, revert to the previous version and compress only the appendix pages, then merge. For fillable forms, compress before filling when possible; some workflows flatten fields and you do not want to discover corruption after data entry.

Browser vs temporary API processing

Light organize tools may run entirely in the browser. Compression that re-encodes images often uses a short-lived HTTPS processing job. That is temporary processing, not permanent storage—but it is still an upload. Prefer the lightest path that meets your quality bar, and avoid uploading more pages than you need. Strip extras with Remove Pages first when a draft includes working notes.

Privacy notes

Compressed application packs and HR files still contain the same personal data as the originals. Delete scratch copies from Downloads after submission. Do not post “before/after size” screenshots that show passport pages. If you must share a compressed file by email, consider Password Protect and send the password through a different channel.

Related tools

Bottom line

Compress to the limit, not past clarity. Measure the requirement, start medium, verify a text-heavy page after every strong pass, and keep an uncompressed backup until acceptance. Readable scans beat a file that merely fits the counter.

Open the related free tool →

← All articles