🗜️ Compress PDF Size

Why Your PDF Weighs So Much (And What You Can Actually Do About It)

A presentation deck emailed as a PDF. A scanned contract you need to send to a client. A product catalog that somehow balloons to 47 megabytes before anyone's touched a single page. If you've ever stared at a file size wondering why text and a few photos need this much space, the answer usually lives inside the PDF's hidden anatomy.

PDFs are container formats. Inside one file you'll find fonts, metadata, document structure, color profiles, and — most importantly for file size — images. Not the images as you see them on screen. The original images, often stored at the full resolution of whatever camera or scanner produced them, sometimes layered behind a compressed version, sometimes uncompressed entirely because whoever assembled the document didn't think to check.

The Image Problem

Here's what typically happens. A marketing team creates a brochure in InDesign. They drop in product photos at 300 DPI because the print shop required it. They export to PDF for the web. Nobody changes the export settings. The result is a 28-megabyte file where a 4-megabyte one would have looked identical on any screen anyone would ever read it on.

Screen displays cap out around 96-150 DPI. A photo that needs 300 DPI for offset printing carries roughly four times as many pixels as a web-optimized version — and none of those extra pixels are doing anything useful on a laptop or phone. Resampling that image to screen resolution, then re-encoding it at a moderate JPEG quality, typically recovers 40 to 70 percent of the original file size without any visible degradation.

The JPEG quality number matters more than most people realize. JPEG compression works by discarding information the human visual system is least likely to notice — high-frequency detail in textures, subtle color gradients in backgrounds. Quality 95 keeps almost everything. Quality 70 keeps quite a bit less, but for photographs of products, people, or scenery, the difference on screen is genuinely hard to spot unless you're zooming in and looking for it. Quality settings below 60 start introducing visible artifacts on smooth gradients and sharp edges, which is why this tool offers three calibrated presets rather than a continuous slider.

What Browser-Based Compression Can and Cannot Do

This tool works entirely in your browser. Your PDF is never transmitted to any server — the compression logic runs locally using JavaScript's Canvas API, which lets us decode embedded JPEG images, redraw them at the same dimensions, and re-encode them at a lower quality setting. The result replaces the original image stream in the PDF, and the file comes back smaller.

There are real limits to this approach. PDFs that consist mostly of text and vector graphics won't compress much — those elements are already stored compactly, and there's no image data to downsample. A 10-page contract with no photos might return from compression exactly the same size it went in, which is the honest result rather than a broken one. Scanned documents are different: a scan is literally one large image per page, and those typically benefit enormously from compression.

Some PDFs use internal compression methods (Flate/zlib streams for binary image data) that require decompression before processing. This tool currently handles DCT-compressed (JPEG) image streams, which cover the majority of image data in PDFs created by standard applications like Word, PowerPoint, Adobe products, and most online PDF generators. Specialized PDF types — particularly CAD exports, certain print-production files, and encrypted PDFs — may fall outside what's addressable client-side.

The Three Quality Presets Explained

High (0.95): Near-lossless for most content. You'll recover some space from files with many large images, but the savings are modest — typically 10 to 25 percent. Choose this if the PDF contains important diagrams, fine-print legal documents with embedded graphics, or anything where visual fidelity is non-negotiable.

Medium (0.85): The default for good reason. This is the point where size reduction becomes meaningful — often 30 to 50 percent on photo-heavy files — while image quality remains professional. Product photos, presentation slides, and marketing materials all look clean at this setting. Most people examining the output side-by-side with the original won't spot a difference unless they zoom in on complex photographic textures.

Low (0.70): Use this when file size is the priority and the PDF is going through email, a web form with strict attachment limits, or a messaging app. Photographic content at this setting shows subtle softening in complex areas, but text remains sharp (it's not affected by image compression at all) and diagrams stay crisp. For internal documents, drafts, or anything viewed primarily on phone screens, quality 70 is often perfectly adequate.

Before You Compress: A Few Things Worth Checking

If a PDF is large because it contains a high-resolution vector illustration or complex typography, compression via image resampling won't help much. The fix there is usually re-exporting from the source application with web-optimized settings. Similarly, if a PDF is encrypted with a password, the embedded data is scrambled in a way that prevents stream-level manipulation — you'd need to decrypt it first.

Scanned PDFs sometimes respond better to dedicated OCR software that can strip the raw scan layer and replace it with a compact image-plus-text representation. Tools like Adobe Acrobat, Smallpdf, or ILovePDF offer this for complex cases where client-side compression hits its ceiling.

For documents you'll be compressing regularly — monthly reports, recurring invoices, recurring newsletter archives — it's worth establishing a workflow at the source. Most PDF export dialogs have an "Optimize for web" or "Screen quality" option that applies the right settings before the file is created, rather than trying to recover space after the fact.

That said, for the immediate need — a file that exists, is too large, and needs to be smaller now — dropping it into a browser-based tool that never touches a remote server is both faster and more private than uploading to a third-party service.