If you've ever tried to compress a PDF before attaching it to an email, you've seen the pattern: every result in Google is a tool that asks you to upload your file. You hand your tax return, a signed contract, or a pile of medical scans to someone's server, wait, and download something back that's usually 3–12% smaller.
That pattern is so universal most people assume it's the only way. It isn't. This guide walks through what PDF compression actually does, when it can and can't help, and how to do it in your own browser without the file leaving your device. I'm going to be unusually honest about what you can realistically expect — most tool pages quietly oversell compression, and users end up disappointed.
The honest math: why lossless PDF compression rarely saves more than 15%
Here's the first thing every marketing page glosses over. A PDF is mostly three things: a container for text+fonts, optional embedded images, and metadata (who made it, when, creator software, etc.). Lossless compression — the kind that doesn't touch picture quality — can only shrink the container, never the pictures inside.
That means the savings ceiling depends on what's actually in your file:
- Pure text PDFs (invoices, bank statements, articles): typically 5–15% lossless savings. The text is already tightly packed; there's not much slack.
- Text with a small number of images: 10–25%. The metadata + stream overhead is a bigger share of total size.
- Image-heavy PDFs (scanned documents, magazines, presentations): 2–8% lossless. The images dominate the file size, and lossless can't touch them.
On our test file — an 18.5 KB text PDF with bloated metadata — Toolbelt's compressor saved 32.4%. That's an above-average result, because the file was deliberately stuffed with redundant metadata for testing. Real-world PDFs you pick off your desktop will usually land in the 5–15% band.
The method that's actually lossless
When you need a smaller PDF but can't sacrifice any sharpness — text must stay selectable, scanned receipts must stay readable, signatures must stay crisp — you're looking at three specific techniques. Good lossless compressors do all three at once:
- Strip unused metadata. Title, author, subject, keywords, creator tool, modification dates, custom XMP packets. These can add kilobytes and tell nobody anything useful about the content.
- Remove embedded page thumbnails. Some export tools (older Word, Publisher, certain scanners) embed a low-res preview for every page. Modern PDF readers generate these on the fly, so the embedded copies are pure waste — often 8–30 KB per page.
- Re-pack with object streams. PDF internally is a directory of numbered objects. Modern PDF writers use compressed object streams that bundle small objects together — most older PDFs don't, and repacking them can shave another few percent.
None of these touch a single pixel. The text is still selectable. Scanned pages still OCR the same. Page count, layout, forms, hyperlinks, annotations — all preserved bit-for-bit.
Do it in your browser (no upload, no account)
Toolbelt's Compress PDF runs all three techniques client-side. Here's what the flow looks like end-to-end.

- Drop your PDF
Drag from Finder/Explorer, or click browse your computer. Files up to 200 MB work — the only real limit is your device's RAM. PDFs over 200 MB start to stress mobile Safari, so split them first if needed.
- Click Compress PDF
The file stays on your device. The button flips to "Compressing…" while the library works through metadata, thumbnails, and object stream re-packing. For a typical 20-page PDF this takes 1–3 seconds on a mid-range laptop, 4–8 seconds on a phone.
- Read the honest verdict and download
The result card shows the before/after size, the percentage savings, and exactly what was stripped. If the file was already optimised, the card says so — "Already lean · No size change this time" — instead of quietly shipping you back a copy of the original with a 0.1% "improvement" and a Pro-tier upsell.

Slim down PDFs without losing a pixel.
How to verify no upload happened (takes 15 seconds)
This is the part no upload-based tool can replicate. Any claim about "privacy" or "security" on an upload tool is asking you to trust them. With a client-side tool, you don't have to.
- Open Chrome/Firefox/Edge DevTools (
F12orCtrl+Shift+Ion Windows,⌘⌥Ion macOS). - Switch to the Network tab.
- Click the 🚫 Clear button to empty the log, or reload the page to start fresh.
- Upload a PDF and click Compress PDF.
- Watch the log.
What you'll see: prefetch requests for sibling pages (Toolbelt uses Next.js, so hovering a link prefetches it for faster navigation — these are all GET requests with an ?_rsc=... query string). What you won't see: any POST, PUT, or outbound request containing your PDF. No request to a third-party domain. No file payload in any request body.
Here's the actual network log from our test run:
When lossless isn't enough
Sometimes you need a scanned 200-page book to fit under a 10 MB email limit, and lossless gets you to 180 MB. In that case you genuinely do need to re-encode the images inside the PDF at a lower quality — that's lossy compression, and it's a separate operation with a different tradeoff.
The honest answer is: Toolbelt doesn't have a lossy PDF compressor yet (it's on the roadmap). For now, three workable alternatives:
- If the PDF is mostly scanned pages: extract the pages as images, run them through Toolbelt's Compress Image tool at 75–85% quality, then merge them back into a PDF. Tedious but local and precise.
- If you're a power user and comfortable on the terminal:
gs -sDEVICE=pdfwrite -dPDFSETTINGS=/ebook -dNOPAUSE -dQUIET -dBATCH -sOutputFile=out.pdf in.pdfwith Ghostscript gives you a dial for aggressiveness (/screen</ebook</printer</prepress). Installs are free for every platform. - If the file contains sensitive content and you really don't want to install anything: macOS Preview has a built-in "Reduce File Size" quartz filter (File → Export → Quartz Filter). It's lossy and not tunable, but it runs locally.
None of these require uploading your file.
Common mistakes that make compression worse
- Don't "compress" a PDF by printing to PDF. Printing a PDF to PDF strips searchable text, turns it into a flat rasterised image, and usually grows the file — not shrinks it.
- Don't rename a scanned image file to
.pdf. A JPG renamed to.pdfisn't a PDF; it's a broken file that PDF readers will reject. Use a proper image-to-PDF converter. - Don't compress PDFs that are already under the target size. If your email limit is 25 MB and your PDF is 3 MB, skip compression. Every compression cycle risks subtle layout quirks in downstream viewers; the only reason to run it is because you genuinely need the savings.
Why this site doesn't upload your files
I'm Shahzaib Hassan, an AI automation engineer in Lahore. I build this site as a side project partly because I was tired of the same pattern: searching for a simple file tool, landing on a page that wants an account, uploading a sensitive file, and ticking a "you won't resell my PDF, right?" box on trust. The tools on Toolbelt all run in your browser because they can — a modern browser is a surprisingly capable runtime, and nothing about compressing a PDF requires a server. If a tool on this site ever needs your data to leave your device (some AI tools do, for obvious reasons), it'll be upfront about that and the data will go directly from you to the provider you choose, not through us.
Frequently asked questions
What's the maximum file size Toolbelt's Compress PDF can handle?
Why did my PDF only shrink by 2%?
Is text still searchable after compression?
What about password-protected PDFs?
Can I compress an entire folder of PDFs at once?
pdf-lib library that this tool is built on.Does Toolbelt run on mobile Safari?
Is Toolbelt's Compress PDF open source?
pdf-lib, which is open source. Toolbelt's UI layer is in a private repo for now but the compression technique is straightforward — strip Info dict entries, delete Thumb references, and save with useObjectStreams: true. Roughly 50 lines of pdf-lib code.Slim down PDFs without losing a pixel.