Take it step by step
- Read the portal’s actual format, page and size requirements. Keep an original.
- Remove pages you do not need before reducing quality.
- Try the target-size PDF tool, then inspect its measured output and warnings.
- If the target is missed, reduce image resolution gradually or split the document only when the portal allows it.
A situation to try.
For a 200 KB limit, check whether the portal means 200,000 bytes or 204,800 bytes. Leave a small buffer and verify the downloaded file, not just the preview.
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.
- Confirm all required pages remain.
- Read stamps, signatures and small print at normal size.
- Confirm the portal accepts the format and actual byte size.
Know the limits.
A dense scan may not fit 100 KB while staying legible. Start from a better scan when repeated compression makes it blurry.
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.
Target-size PDF optimization
Attempt a measured size target with raster-based presets.
On your deviceWhy use it: Attempt a measured file-size target.
Before you start: Rasterized exports can lose searchability and interactive structure.
Compress PDF
Make PDFs smaller with local lossless optimization.
On your deviceWhy use it: Try lossless optimization before reducing image quality.
Before you start: Not every input can be reduced.
Preparation tools process locally. Official service links take you to the authority’s website. Inspect any exported copy before sharing it.