GizmoBench guides
Best PDF Compressor: Shrink Files Without Uploading Them
For most people, the best practical choice is a browser-based compressor that processes files locally and down-samples images at a balanced DPI, since images, not text, account for most of the bytes in an average PDF. Browser-based local tools like the Image Compressor embody this principle and are a sound starting point before you consider heavier desktop or server-side options covered below.
TL;DR:
- For scanned or photo heavy PDFs, lossy downsampling cuts file size by roughly 78% to 88%, while lossless optimization typically saves only 1% to 6%.
- Use 150 DPI for screen viewing, 200 DPI for print, and 72 DPI only when minimum file size outweighs softness in scanned text.
- Choose a local browser tool for sensitive files; free online compressors require uploads, while desktop or batch software suits print work or scheduled processing.
- Converting PDF pages to images removes searchable, selectable text and can strip forms or clickable links, so verify interactive features before using that workflow.
Table of Contents
- Which PDF Compressors Should You Try First?
- Why Do PDF Compressors Give Such Different Results?
- How Do You Choose the Right Compression Settings?
- How Do You Compress a PDF in Your Browser Step by Step?
- How Were These Compression Benchmarks Measured?
- So, What’s the Best PDF Compressor to Use?
- Start Compressing PDFs in Your Browser
- FAQ
- Sources
Which PDF Compressors Should You Try First?
Picking a tool depends on what kind of file you have and how much control you want over the result. A scanned contract behaves nothing like a text-heavy report, and the right tool for one is often the wrong tool for the other.
Here’s a practical shortlist, roughly in the order most people should try them:
- Browser-based local compressor (our Image Compressor and related tools): best for privacy and a quick balance of quality and size, since files never leave your device.
- Auto-mode server-side compressor: best when you need extreme shrinkage and can accept some quality loss, because these tools sample a file first and pick a lossy or lossless engine automatically.
- Desktop or batch applications: best for large-scale or print-focused jobs where you need fine control over color profiles, fonts and output fidelity.
- Free online-only compressors: best for a quick one-off reduction when the document isn’t sensitive and you don’t mind uploading it to a server.
The auto-mode category deserves a closer look because it solves a real problem: a single fixed compression method can make some files bigger instead of smaller. A benchmark from ERPFit found that sampling a file first, then routing image-heavy PDFs to a lossy engine and text-heavy PDFs to a lossless one, produced more reliable results than applying one method across the board.
Desktop and batch tools matter mainly for print production, where resolution and color accuracy carry real consequences. If you’re preparing a manuscript or book interior for print, a dedicated preflight checklist covers the checks that general-purpose compressors skip, like bleed, trim and font embedding.
Free online compressors fill a narrow but real niche: you need a smaller file right now, privacy isn’t a concern, and you’re willing to trust a server with the upload. They’re fine for a one-time resume submission; they’re a worse fit for anything containing financial, medical or legal information.
Why Do PDF Compressors Give Such Different Results?
The gap between compressors comes down to one distinction: lossless structural optimization versus lossy image downsampling. Understanding which one a tool is actually doing explains most of the confusion people run into when comparing results.
Lossless optimization cleans up the file’s internal structure without touching how anything looks. It removes duplicated fonts and images, deduplicates repeated objects, and recompresses internal data streams more efficiently. According to sample code from the Apryse Optimizer SDK, this category of tool commonly includes removing duplicate fonts and images and recompressing streams, all without changing pixel data. On a text-only PDF, that’s often where the savings stop, because there isn’t much redundant image data to remove.
Lossy image downsampling works differently: it reduces the actual resolution (DPI) of embedded images and recompresses them with codecs like JPEG, JBIG2 or JPEG2000. The Apryse SDK documentation lists JBIG2 as suited to monochrome scanned pages and JPEG2000 as a high-compression option for photographic content, with configurable quality and DPI parameters exposed to developers. This is where the big size reductions happen, because a 300 DPI scanned page is carrying far more pixel data than a screen or even a decent printer needs.
The numbers back this up clearly. The ERPFit benchmark tested both approaches on the same scanned, image-heavy files: Ghostscript-style downsampling cut file size by roughly 78% to 88%, while lossless structural optimization on the identical files saved only about 1% to 6%.
Typical compression outcomes: on scanned or photo-heavy PDFs, lossy downsampling achieves roughly 78% to 88% size reduction, while lossless optimization on the same files saves only a few percent, since there’s little duplicate or inefficient structural data left to remove.
A few points worth keeping in mind as you evaluate compressors:
- Vector content (text, lines, shapes) compresses through stream compression and object deduplication, with modest gains on already-efficient files.
- Raster content (scanned pages, embedded photos) requires actual resampling and codec changes to shrink meaningfully.
- Engine choice matters more than brand, since two tools using the same downsampling approach will land in a similar savings range regardless of interface.
- Recompression thresholds help avoid wasted effort. Testing recompression only on images above a certain resolution, rather than blanket recompression, can produce better visual results for the same file size, based on how SDK sample configurations expose per-image quality settings.
Licensing and engine availability vary by tool. Some commercial products license Ghostscript-style or SDK-based engines, while browser tools that process locally tend to implement their own downsampling logic to avoid sending data to a server at all. Neither approach is inherently better at compression; the difference is where the processing happens and what access you give up.
How Do You Choose the Right Compression Settings?
Before you compress anything, run through a short checklist.
- Identify what’s actually in the file. Open a few pages. If they look like photographs or scans, you’re dealing with raster content that benefits from downsampling. If it’s mostly typed text and simple graphics, lossless optimization alone may be enough.
- Decide what the file is for. A document going to print needs higher resolution than one that will only ever be viewed on a screen or attached to an email.
- Check your privacy requirements. If the PDF contains financial, medical, legal or otherwise sensitive information, a local browser tool that never uploads the file is the safer route.
- Assess whether you’re compressing one file or many. A single document is easy to eyeball; a batch of hundreds benefits from a consistent default setting applied uniformly.
Once you know the file type and purpose, DPI is the main lever. The ERPFit benchmark recommends 150 DPI as a practical default for screen viewing, since it balances legibility against size. For documents headed to a printer, 200 DPI preserves more visual fidelity. For the smallest possible file, such as an email attachment limit, 72 DPI gets you there, though text in scanned images can start to look soft at that level.
Always preview the result before committing to a batch run. Image quality at 150 DPI looks fine on most screens but can reveal softness in fine print or detailed diagrams once you zoom in, and that’s easier to catch on one test file than after compressing two hundred of them.
Pro Tip: Run your intended settings on a single representative file first, check the text and image clarity at actual size, and only then apply the same settings to the rest of your batch.
How Do You Compress a PDF in Your Browser Step by Step?
This workflow uses tools that process entirely on your device, so nothing uploads to a server. Core functions are free and don’t require an account.
Start with a quick visual check: open the PDF and look at a few pages. If they look like photographs, scanned paperwork or anything with continuous color gradients, you’re dealing with an image-heavy file that will benefit most from downsampling.
- Open the Image Compressor if you’re working with individual page images, or start from your PDF directly if your tool supports page-level compression.
- Choose a compression level. Start at the “recommended” or moderate setting rather than the most aggressive one.
- Preview the result at actual size, not just thumbnail size, paying attention to text edges and fine detail.
- Adjust DPI or quality downward only if the file is still too large and the preview still looks acceptable.
- Download the compressed file once you’re satisfied with the trade-off.
For multi-page scans that resist standard compression, a more hands-on route often helps: use PDF to Image to export each page, run the extracted images through the Image Compressor or Image Resizer to cut DPI directly, then use Image to PDF to reassemble the compressed pages into a single document.
A few practical notes:
- If your PDF contains forms or clickable links, flatten or verify those interactive elements after recompression, since some image-focused workflows can strip them if pages are rasterized during conversion.
- Embedded, searchable text stays intact through lossless optimization, but converting pages to images (as in the multi-step workflow above) turns that text into a flat image, which removes the ability to search or select it.
- Because this entire process runs locally in your browser, it’s a reasonable default for anything you’d rather not upload, though you should still confirm the claim applies to whichever specific tool you’re using.
How Were These Compression Benchmarks Measured?
The savings figures cited throughout this article come from a published benchmark that tested scanned and text-based PDFs under different compression engines, measuring file size before and after each run.
The ERPFit benchmark compared a Ghostscript-style lossy downsampling engine against a lossless structural optimizer, running both on the same set of files and recording the resulting file sizes. The approach also tested an auto-mode method: sampling the first several pages to decide which engine to apply, then running the full file and keeping whichever output came out smaller, a safeguard against the rare case where compression increases file size.
| File type | Engine used | Typical size change |
|---|---|---|
| Scanned or photo-heavy PDF | Lossy downsampling (Ghostscript-style) | −78% to −88% |
| Scanned or photo-heavy PDF | Lossless structural optimization | −1% to −6% |
Results vary by file because the ratio of image data to text data differs so widely between documents. A 40-page scanned report at 300 DPI has far more compressible image data than a 40-page Word-to-PDF export with a handful of logos. When you test your own files, treat these ranges as a reasonable expectation for similar file types rather than a guarantee, since factors like original scan resolution, color depth and existing compression all shift the outcome.
So, What’s the Best PDF Compressor to Use?
For most people, a browser-based compressor with local processing remains the best starting point: it costs nothing to try, protects sensitive content by never uploading it, and gets you into the 78% to 88% savings range on image-heavy files that the ERPFit benchmark documented for lossy downsampling.
That said, three situations call for a different tool. Print production work needs the finer resolution and color controls that dedicated desktop or preflight workflows offer. Legal or archival documents sometimes need to preserve exact fidelity, which argues for lossless optimization rather than any downsampling at all. And compressing thousands of files on a schedule is better suited to a server-side or desktop batch tool built for that scale.
For everything in between, which covers most everyday compression needs, start with a local browser tool, run one test file, and compare the before-and-after size and quality before processing the rest.
Start Compressing PDFs in Your Browser
Browser tools let you avoid choosing between convenience and privacy: everything runs on your own device, with no upload and no account needed for core functions.
The relevant tools for a PDF compression workflow are straightforward:
- PDF to Image: export PDF pages as images when you need finer control over downsampling.
- Image to PDF: recombine compressed images back into a single PDF.
- Everyday tools: browse the full set of calculators and utilities alongside our document tools.
FAQ
What is the best PDF compressor?
There’s no single “best” tool for every file, but a browser-based compressor that down-samples images locally is the best starting point for most people, since images drive most of the file size. For scanned or photo-heavy PDFs, this approach can achieve 78% to 88% savings, while server-side auto-mode tools and desktop batch apps serve more specialized needs like extreme shrinkage or print production.
How do you best compress a PDF file?
The most reliable method is to identify whether your file is image-heavy or text-heavy first, then choose lossy downsampling for scanned content or lossless optimization for text-based documents. A practical default is 150 DPI for screen viewing, moving up to 200 DPI for print or down to 72 DPI when file size matters more than visual sharpness.
Does Adobe have a free PDF compressor?
Adobe offers an online PDF compression tool as part of its Acrobat product line, though free usage is typically limited and may require an account for full access. Browser-based local tools that need no account are a privacy-focused alternative for quick compression tasks.
What is the best program to reduce the size of a PDF file?
The right program depends on your file type and goals: browser-based tools work well for everyday compression without uploading files, SDK-based optimizers like the one documented by Apryse suit developers building custom workflows, and desktop batch software fits large print-production jobs. For a quick, private reduction on scanned or image-heavy files, a local downsampling tool set to around 150 DPI is a solid default.