The choice is not simply “large” versus “small”. It is whether the output must retain document features or whether an image-based reading copy is acceptable.
| Decision | Content-preserving approach | Image-based approach |
|---|---|---|
| Starting goal | Reduce unnecessary structure while keeping existing page content | Represent pages as images with chosen quality settings |
| Best starting question | Can a smaller copy be made without changing what users need? | Is a picture-based copy acceptable for this recipient? |
| Text and interaction | Review the result; do not infer complete feature preservation from the name | FileStation warns that its image mode removes selectable text and interactive content FileStation: Compress PDF |
| File-size expectation | Savings may be modest | Depends on source material and settings; a target is not guaranteed FileStation: Compress PDF |
| Required check | Inspect layout and all important features | Inspect legibility and confirm that missing text/interaction is acceptable |
A scan, a text report and an interactive form have different needs. Start by naming those needs instead of choosing a compression level in isolation. Adobe’s optimization documentation illustrates how different controls affect different parts of a PDF. Adobe Help: Reduce PDF file size with advanced options
A practical starting point: begin with the least disruptive option; move to a more destructive transformation only when the task permits it. This is a proposed decision rule, not a claim that one mode always produces a smaller file or preserves every feature.