How ShellPDFs Compresses PDFs: Balancing Quality and File Size

PDF compression tools get a bad reputation because many of them produce blurry, degraded output. That happens when a compressor aggressively downsizes every image without considering what the document actually contains. ShellPDFs takes a different approach by offering two distinct compression paths, each designed for different priorities.

This article explains how ShellPDFs handles compression under the hood, what each mode does to your file, and how to choose the right one for your situation.

Two Compression Modes, Two Different Goals

ShellPDFs offers two ways to compress a PDF, and understanding the difference helps you pick the right one every time.

Private Compression (Lossless, Browser-Based)

Private Compression runs entirely inside your web browser using WebAssembly. Your file never leaves your device. This mode works by reorganizing the internal structure of the PDF — deduplicating embedded fonts, compressing content streams, removing orphaned objects, and stripping unnecessary metadata like thumbnail previews and revision history.

Because it never modifies actual content (text, images, or vector graphics), the output is visually identical to the original. The trade-off is that file size reduction is more modest — typically 5–40% depending on how much structural bloat the original contains. Documents that were already well-optimized will see smaller gains.

This mode is ideal when privacy is paramount (legal documents, medical records, financial reports) or when you need to preserve every pixel for print production.

Stronger Compression (Server-Side)

Stronger Compression uploads your PDF to ShellPDFs' server where Ghostscript processes it in an isolated worker. This mode can resample high-resolution images (for example, reducing 300 DPI photographs to 150 DPI for screen use), apply advanced Deflate parameters, and perform deeper structural optimization that requires more compute than a browser can handle.

The result is significantly smaller files — 40–80% reduction is common for scanned documents and image-heavy PDFs. The quality impact on images is minimal at typical screen viewing distances, but it is a lossy process: the original full-resolution images are not recoverable from the compressed output.

Server-processed files are encrypted during processing, handled by isolated workers with no shared filesystem, and deleted within one hour. Audit logs only capture job metadata (timestamps, file sizes, status codes) — never document contents.

When to Use Each Mode

The choice comes down to two questions: how sensitive is the document, and how much do you need to reduce the file size?

For confidential files where you cannot tolerate any server upload — contracts, patient records, tax returns — Private Compression is the right choice. You get meaningful size reduction with zero privacy risk, and the process is instant.

For files that need to fit within email attachment limits (most servers cap at 25 MB), portal upload requirements, or messaging apps like WhatsApp, Stronger Compression is usually necessary. The quality at 150 DPI is more than sufficient for on-screen reading, and most recipients will never notice the difference.

For print-bound documents, always use Private Compression. Resampling images to 150 DPI is fine for screens but can produce noticeable softness in printed output, especially for photography and detailed graphics.

What Happens to Your File

Understanding the processing pipeline helps build trust in the tool.

With Private Compression, the entire process happens in your browser tab. The PDF is loaded into memory, processed by a WebAssembly module, and the result is offered as a download. At no point does the file touch a network connection. If you close the tab, everything is gone.

With Stronger Compression, the file is uploaded over TLS 1.3 to an isolated processing worker. Ghostscript runs the compression, the result is made available for download, and both the original and compressed versions are scheduled for deletion. A cleanup process sweeps the storage directory every hour to ensure nothing persists beyond the retention window.

Practical Tips for Better Results

Start with Private Compression. If the resulting file is small enough for your needs, you are done — and your file never left your device. Only escalate to Stronger Compression if you need deeper reduction.

If your PDF contains pages you do not actually need to share, consider using the Remove PDF Pages or Split PDF tools first. Removing unnecessary pages before compressing often produces a smaller final file than compressing the full document.

For recurring workflows (monthly reports, quarterly filings), run a test with both modes on a sample file to understand the size-quality trade-off for your specific document type. The results are predictable across similar documents, so one test can inform your workflow going forward.

FAQ

Does ShellPDFs compression change document colors or fonts? Private (lossless) compression never touches colors or embedded fonts. Stronger (server) compression resamples images but leaves text, vector graphics, and fonts intact.

Which mode should I use for print-quality documents? Use Private Compression. It maintains original resolution and DPI while reducing size through structural cleanup.

How much smaller will my PDF get? Scanned documents: 40–80% smaller. Image-heavy PDFs: 30–60%. Text-only: 5–20%. Private lossless mode produces smaller gains but with zero quality loss.

Is my file safe during compression? Private mode never uploads your file. Stronger mode processes files on our server and deletes everything within one hour. No document content is ever logged.

Try It Now

Open the Compress PDF tool to reduce your file size. Start with Private Compression for instant, browser-based results, or switch to Stronger Compression when you need maximum reduction.