PDF, video and audio size targets
Download a source or run it here using the same compressor as the homepage. The table reports the bytes from your run; no output size is assumed in advance. One KB here means 1,024 bytes.
| File | Input bytes | Target bytes | Output bytes |
|---|---|---|---|
| PDF output | 52,225 | 30,720 | 27,136 |
Reference method: the PDF uses the actual PDF processor with a Node canvas adapter; video and audio use native FFmpeg with the same encoding arguments and bitrate search as the browser processor. Browser encoders can return different sizes. See method and measurements.
One-page invoice → 30 KB
A fictional Docuivo invoice with embedded fonts. Compression renders pages as images: selectable text, links, forms and digital signatures are not preserved. Check all numbers and text at full size.
Video and audio processing loads the browser encoder on the first run. Keep this page open. A small target can reduce quality, still produce an oversized file, or be rejected; a completed run does not guarantee that the result suits your destination.
Email and upload portals both impose file-size limits, but they fail in different ways. Email systems may add encoding overhead and total-message limits. Portals may reject files based on their own interpretation of bytes, page count, format, or security checks. In both cases, targeting exactly the published maximum is unnecessarily risky.
Leave a safety margin
If the published limit is 10 MB, a result around 9–9.5 MB is usually safer than 9.99 MB. You do not need to crush the document to 2 MB unless there is another reason. The goal is to fit reliably while preserving readable pages.
Email and portal priorities are different
| Destination | Main concern | Practical approach |
|---|---|---|
| Message/attachment limits and transfer | Leave margin and keep the document comfortable to read on screen | |
| Application portal | Strict validation rules | Match accepted PDF requirements and target below the stated maximum |
| Cloud upload | Transfer time or storage | Compression may be optional if no hard limit exists |
| Print workflow | Visual fidelity | Avoid aggressive compression unless the recipient confirms it is acceptable |
Know what kind of PDF you have
- Text-native PDF: generated from Word, a browser, or design software; often already compact and searchable.
- Scanned PDF: pages are primarily images; usually much larger and more compressible.
- Mixed PDF: selectable text plus photos, diagrams, or scanned inserts.
- Form PDF: may contain fields, signatures, attachments, or interactive elements that need preservation.
A reliable send-or-upload checklist
- Save an untouched originalKeep a copy outside the compression workflow.
- Choose a target below the limitUse a small margin rather than the exact maximum.
- Compress once from the sourceAvoid repeated generations from already reduced copies.
- Review every pageCheck small text, stamps, diagrams, signatures, and image captions.
- Verify special featuresIf the PDF contains forms or searchable text, confirm whether the destination actually needs those features.
For scan-specific advice, see How to Compress a Scanned Document and Keep Small Text Readable.