Take it step by step
- List the features you need: searchable text, form fields, links, signatures or simply readable pages.
- Start with a lossless setting and compare bytes.
- If a smaller image-based result is acceptable, try a quality preset on a copy.
- Read output warnings and independently inspect the export.
A situation to try.
An application scan may tolerate modest image downsampling. A form with interactive fields needs a preservation check before any flattening or rasterization.
Use the tool’s synthetic example first where available. The example here explains a decision; it is not a reported benchmark result.
Before you call it done.
- Test selectable text and form fields.
- Compare fine details at 200%.
- Keep the original when editing may be needed later.
Know the limits.
A visually similar page may have lost its editable structure.
This tool’s current boundary: Lossless reserialization only in this build. Image recompression is not available. Already optimized files may not shrink.
Our lossless compression check.
Three synthetic PDFs were processed through the actual compression adapter. PDF.js independently read and rendered all five input/output pages. Extracted text and rendered pixels matched at scale 1 in this Windows/Node test.
| Fixture | Input bytes | Output bytes | Saved | Text layer |
|---|---|---|---|---|
| cv | 1,823 | 1,167 | 35.98% | Retained |
| scan | 8,670 | 8,241 | 4.95% | Absent before and after |
| brochure | 27,538 | 25,871 | 6.05% | Retained |
The source fixtures used uncompressed object streams. These reductions do not predict results for already-optimized files. Forms, signatures, attachments, accessibility and browser/mobile performance were not certified by this check.
Download and reproduce the evidence
- cv: input PDF · output PDF
- scan: input PDF · output PDF
- brochure: input PDF · output PDF
Versions, method and SHA-256 hashes (JSON) · Raw results (CSV)
Reproduction: run npm test -- tests/tool-evidence.test.ts in the project checkout. The downloadable report records the environment. Timing is a single Node adapter run, not a browser speed score.
Evidence and scope
Technical source guidance and task-specific output checks. These do not establish that every file, browser or device passes.
Use the checks above on your own exported result. A source explains the format or mechanism; it is not proof that this export preserved every feature.
Technical reference: PDF-LIB: page operations and exports ↗
Choose the right tool for this step.
Compress PDF
Make PDFs smaller with local lossless optimization.
On your deviceWhy use it: Try lossless storage optimization.
Before you start: Inspect the output independently.
Target-size PDF optimization
Attempt a measured size target with raster-based presets.
On your deviceWhy use it: Choose a raster-based size attempt only when suitable.
Before you start: Read the rasterization warning before processing.
Preparation tools process locally. Official service links take you to the authority’s website. Inspect any exported copy before sharing it.