JustUtils

PDF compression guide

Test PDF Compression Quality, Not Just File Size

Compare PDF compression modes, inspect text and image quality, and catch flattened links, forms, signatures, or accessibility before sharing.

By JustUtils9 minute readReviewed
A safer three-step decision path
STEP 1

Understand the input

Identify what must survive.

STEP 2

Choose the trade-off

Match settings to the real task.

STEP 3

Verify the output

Check the result before replacing anything.

A smaller PDF is useful only if it still does the job

File size is easy to measure, which makes it tempting to treat the smallest result as the winner. That test misses the expensive failures: a searchable report becomes a stack of images, a form can no longer be completed, a link stops working, or 8-point text becomes tiring to read. Start by listing what the recipient must be able to do with the file.

For example, an application portal may require “under 5 MB, readable on screen, no form fields needed.” A contract may require “selectable text, intact links, and the original digital signature.” Those two files should not use the same compression method even when their starting sizes are identical.

What the three JustUtils modes actually change

ModeImplementationLikely trade-off
Preserve PDF featuresRewrites the existing PDF with object streams; it does not rasterize pagesText, links, forms, and page data survive, but savings may be modest or zero
BalancedRenders every page at 144 DPI and stores it as JPEG with a 0.76 quality factorStrong reduction for scans and image-heavy pages; page content is flattened
Smallest fileRenders every page at 108 DPI and uses a 0.58 JPEG quality factorSmaller output, with a greater risk of soft small text and visible image artifacts

In the two raster modes, the page is rebuilt as one image. It may look similar, but its text is no longer selectable and links, forms, annotations, accessibility structure, and signatures are flattened. Use the PDF compressor only after deciding whether that behavior is acceptable.

Build a five-page representative test set

You do not need to inspect every page at maximum zoom. Choose pages that expose different failure modes, then use the same set for every candidate output:

  1. The smallest body text. Include footnotes, subscripts, or dense terms and conditions.
  2. A photograph or shaded chart. Look for blockiness, halos, banding, and lost labels.
  3. Thin lines. Test tables, diagrams, light gray rules, and small colored text.
  4. An interactive page. Include a hyperlink, form control, bookmark, annotation, or selectable ID number.
  5. An unusual page. Include landscape orientation, a large sheet, transparency, or a scanned signature.

If the document has fewer than five pages, inspect every page. If it has hundreds, add the first and last page plus at least one page from each distinct source or scan batch.

Write pass-or-fail criteria before comparing outputs

Replace “looks fine” with checks another person can repeat. A portal submission might require an output below 5,000,000 bytes, legible 8-point text at 100% zoom, correct page count, and a successful test upload. A reference manual might instead require searchable text, working internal links, readable diagrams, and no fixed size ceiling.

Record each criterion as pass, fail, or not applicable for Preserve, Balanced, and Smallest. Stop at the least destructive mode that passes every required check. If no mode passes, the evidence points to a different workflow—such as removing unneeded pages, optimizing source images, or asking the recipient for another delivery method—rather than silently accepting unreadable output.

Run the comparison without overwriting evidence

  1. Keep the original unchanged and record its byte size and page count.
  2. Create a Preserve result first, then Balanced, then Smallest. Give each a distinct filename.
  3. Open all results in the same PDF reader at the same zoom level.
  4. Check the representative pages at fit-to-width, 100%, and the zoom level used for detailed reading.
  5. Search for a known phrase, copy an account number, open a link, and try any required form field.
  6. Record output size only after the functional and visual checks pass.

This order gives you a stopping rule: accept the least destructive result that meets the delivery limit. There is no benefit in flattening a document merely because an even smaller copy can be produced.

Why no compressor can promise an exact percentage

A scanned magazine may contain millions of noisy pixels per page, while a digitally generated invoice may contain only fonts and drawing commands. A file may already use compressed JPEG images or efficient object streams. Re-encoding the first document can save a great deal; rewriting the second may barely change it and can occasionally make it larger.

If a portal has a hard limit, aim below it rather than exactly at it. File-size displays can use decimal MB or binary MiB, and another system may add metadata. A practical margin prevents a technically close result from being rejected.

Decision record you can reuse

Write one line with the chosen mode and the checks performed: “Balanced; 3.8 MB; pages 1, 7, 12, 19, and 24 checked at 100%; text readable; selectable text not required; uploaded to the destination successfully.” This makes the trade-off explicit and gives another person enough information to repeat the test.

Sources and implementation references