PDF size versus quality
Compression is an information tradeoff. The useful question is not “How small can this get?” but “Which details must remain reliable after the size falls?”
Know what consumes the bytes
A text-native PDF can hold many pages in a small file. A scanned PDF is closer to a stack of photographs: resolution, color depth, noise, and JPEG quality dominate its size.
Page count matters, but ten clean black-and-white text pages can be smaller than one high-resolution color scan. File size alone does not reveal document complexity.
Resolution and quality trade places
Lowering JPEG quality removes subtle image detail. Lowering render scale reduces the pixel grid itself. A balanced pass changes both gradually; an aggressive pass can make small type, seals, or fine lines unreadable.
There is no universal safe compression percentage. The meaningful threshold is whether every required detail survives at the size the recipient will view or print.
- ■Names and identification numbers
- ■Fine print and footnotes
- ■Stamps, signatures, and seals
- ■Barcodes and QR codes
Preserve a recovery path
Keep the untouched source outside the browser workflow. Give the compressed export a new filename so it cannot silently replace the original.
When the target is impossible without visible damage, split the document only if the portal permits multiple files, rescan at a sensible resolution, or ask the receiving organization for an approved alternative.
Put the limit first
Run one local compression pass, then inspect every page before submitting.
Open the compressor →