PDF compression guides
How to Compress a PDF to 1 MB, 2 MB, or a Specific Size
Treat the requested size as an external acceptance limit, then work toward it without sacrificing the parts of the document that matter.
Last updated
If a portal requires a PDF under 1 MB, 2 MB, or another limit, treat that number as an external byte ceiling rather than a quality setting. Calculate the reduction required, compress a copy with the mode suited to its contents, and check the downloaded file's exact size. If another pass harms readability, remove unnecessary pages, split the document, or choose another delivery route.
How much reduction does the size limit require?
required reduction (%) = (input bytes − size limit bytes) ÷ input bytes × 100An 8 MB PDF must lose 75% of its bytes to reach a 2 MB limit: (8 − 2) ÷ 8 × 100 = 75%.
Use the same unit for the starting file and the limit. A website may label its cap in MB while enforcing a raw byte threshold, so the portal's rejection or acceptance is the final test. Leave a small margin instead of tuning a file to the displayed boundary.
| External limit | Practical starting point | If the file is still too large |
|---|---|---|
| 1 MB | Use a copy and start with the mode that matches the document; a large scan may need substantial image reduction. | Remove irrelevant pages or split by section before making small text unreadable. |
| 2 MB | Calculate the required percentage, compress once, then compare the download with the portal limit. | Try a more suitable image or scan workflow only when visual inspection supports it. |
| 5 MB | A normal mixed document may need only one careful pass. | Check whether another attachment or the complete submission, rather than this PDF alone, exceeds the cap. |
How do you work toward the limit in PDFStay?
- Keep the original and work on a copy whose current size you have recorded.
- Choose standard compression for a typical digital document, image compression for image-heavy pages, or scanned-PDF compression for pages that are mostly raster scans.
- Download the result and compare its file properties with the portal's limit.
- Open the exact download, inspect every page, and zoom into small text, signatures, diagrams, and codes.
- Make another change only when the remaining gap justifies the additional quality risk.
What should you change when the first result misses the limit?
| What you observe | Next action | Reason to stop |
|---|---|---|
| Photos or screenshots dominate the pages. | Use the image-focused route and review edges, labels, and gradients after downsampling or lossy image compression. | Stop when important detail becomes soft or blocky.2 |
| Each page behaves like a scanned image. | Use the scanned-PDF route and inspect small type, stamps, and handwriting. | Keep an archival or evidentiary original unchanged. |
| The submission contains appendices or blank pages the recipient does not need. | Remove only pages that are genuinely outside the requested submission. | Do not alter a signed, numbered, or legally complete record. |
| The recipient accepts several files and the document has clear sections. | Split at a logical boundary and label the parts clearly. | Do not split a workflow that requires one intact PDF. |
How do you verify that the final PDF is acceptable?
PDFStay's benchmark page and downloadable JSON show fixed-fixture byte counts, page counts, browser context, and test dates. They are useful for reproducing the published examples, but they cannot predict whether a different PDF will reach your limit or remain suitable for its intended use.3, 4
- Confirm the exact downloaded file is below the portal's enforced limit.
- Compare its page count with the original or the intentionally reduced set.
- Check searchable text, links, form fields, signatures, and bookmarks that matter to the workflow.
- Inspect the smallest meaningful content at the zoom level a recipient will use.
- Submit early enough to change route if the portal still rejects the file.
FAQ
Can PDFStay guarantee a PDF will be exactly 1 MB or 2 MB?
No. The current public interface does not offer an exact-size target control, and document contents place practical limits on safe reduction. Check the downloaded bytes and the document itself.
Should I keep compressing until the portal accepts the file?
Only while the document remains fit for its purpose. If text, signatures, diagrams, or codes become unreliable, remove unneeded pages, split when allowed, or use another approved delivery method.
Is a displayed MB value always the same as the portal's byte limit?
Not necessarily. Interfaces can round file sizes or use different conventions. The receiving portal's actual acceptance check is authoritative, so leave some margin.
Sources
- PDFStay — Compress PDF workflowPDFStay first-party methodologySource reviewed:
- Adobe Acrobat — PDF Optimizer settingsofficial technical documentationSource reviewed:
- PDFStay reproducible compression checksPDFStay first-party methodologySource reviewed:
- PDFStay compression benchmark data (JSON)PDFStay first-party dataSource reviewed: