You can compress a PDF without uploading it by running the optimizer inside the browser tab: the file is read from disk into memory, rewritten there, and handed back as a download. What this tool performs is a lossless structural rewrite, not a lossy image recompression, and it has no target size field.
It packs objects into compressed object streams, deflates streams that were stored uncompressed, and rebuilds the cross reference tables; Maximum mode also linearizes the file. Text, links, bookmarks and form fields survive, images are copied rather than re-encoded, and files are limited to 50 MB. How much a document shrinks depends entirely on how loose its structure was: files from older generators often drop by a real percentage, while a small file from a modern app can come out slightly larger because the rewrite has its own overhead.
Almost every "compress PDF" page on the web promises the same two things: an exact size, and the implication that the quality cost is zero. Both are usually untrue. Real size reduction on a PDF comes from either removing content or re-encoding the images inside it, and once images are re-encoded, quality is a dial someone had to choose. This page explains what a browser optimizer can and cannot do, so you can decide whether your document is a candidate before you spend time on it.
Compress PDF
Rewrite a PDF's internal structure to remove wasted bytes, with the real before and after sizes reported. The file never leaves your device.
What a lossless PDF rewrite actually does
The optimizer used here is qpdf 11.7.0, compiled to WebAssembly and run inside the page. It performs four operations, and none of them touch the visible content of a page.
| Operation | What it removes | Which mode applies it |
|---|---|---|
| Object streams | Per-object headers and padding scattered through the file | Standard and Maximum |
| Stream compression | Data blocks that were written uncompressed | Standard and Maximum |
| Cross reference rebuild | Loose offset tables and incremental update leftovers | Standard and Maximum |
| Linearization | Nothing. It reorders the file for faster first page display | Maximum only |
Everything a reader can see, select or click is copied through unchanged. Text stays text and remains searchable, links remain clickable, and bookmarks, form fields and annotations all survive. The file is never flattened into page images, which is the crucial difference between this tool and a service that advertises a fixed reduction.
Which PDFs shrink, and which do not
A file can only lose weight if it still carries something wasteful. That depends almost entirely on which program wrote it and how.
| Your PDF | Typical result | Why |
|---|---|---|
| Exported by an older office suite or print pipeline | Often 10 to 40 percent smaller | Uncompressed streams and a loose cross reference table to reclaim |
| Saved repeatedly with incremental updates | Usually smaller | Obsolete object revisions are discarded by the rewrite |
| Produced by a modern app from scratch | Often unchanged, sometimes larger | Nothing to remove, and the new structure has its own overhead |
| A scan or photo gallery | Barely changes | The bulk is already-compressed image data that is copied, not re-encoded |
The "sometimes larger" row is the part other tools do not tell you. A measured example from this tool: a three page PDF of 1295 bytes came out at 2568 bytes. The objects had to be gathered into a new object stream and the file was linearized, and both of those cost a few hundred bytes on a file that small. It is a valid PDF, it opens normally, and the original was still the better copy to keep. When that happens the tool reports the increase as an ordinary result rather than an error, and says so in plain language instead of pretending the run failed.
How to reduce PDF size without uploading it
- Add the PDF. Drop the file into the optimizer or click to browse. It is read locally, and the file size is checked against the 50 MB cap before anything else happens.
- Pick Standard or Maximum. Standard packs the objects into compressed streams at level 6. Maximum uses level 9 and adds linearization, which is about how the file is arranged rather than how small it gets.
- Read the before and after numbers, then decide. The panel shows both sizes and the percentage change. If the result is smaller, download it. If it is not, keep the original and move on to one of the alternatives below.
The original file on disk is never modified, so a run that gains nothing has cost you a few seconds and nothing else. The engine is about 1.3 MB and downloads on first use, after which the tool works offline.
When the file will not get smaller
Two situations account for nearly every disappointing result, and both have a different fix.
The PDF is mostly images
Scans, phone photos, exported presentation slides and anything with a photographic background all store most of their bytes as image data. A lossless rewrite cannot touch that data, so the size barely moves. What actually works is re-encoding the images at a lower quality, and the browser route to that is indirect: send the PDF to the PDF to JPG converter to render each page as a JPEG at a quality you choose, then rebuild a PDF from those images. This can cut a scan by far more than any structural optimizer, because it is genuinely lossy. The cost is that the text layer is gone: what was searchable becomes a picture of text.
The file carries pages you do not need
Removing content beats compressing it every time. A membership application that ships with four pages of terms you are not submitting is a quarter of the file in pure waste. Delete the pages first with the Organize PDF tool, which lets you reorder and remove pages visually, and only then run the optimizer on what remains. On a scanned document that is the single largest saving available anywhere in this toolset.
The document is over the 50 MB cap
The optimizer accepts files up to 50 MB and states the limit on the drop zone rather than failing silently halfway through. Above that, split the document, optimize the parts, and merge them back with the Merge PDF tool. It is three browser steps, no upload, and the result is a document that opens normally.
What this tool deliberately does not do
- No target size. There is no field for "make this 100 KB". Hitting an exact number requires re-encoding images at a computed quality and iterating, which is a lossy operation with a visible cost. A tool that offers the field is quietly choosing that quality for you.
- No image recompression, so no guarantee of a reduction. The savings depend on the input. Nothing here can promise a percentage.
- No downsampling of image resolution. A 300 DPI scan stays 300 DPI. Reducing DPI is a separate, lossy decision.
- No page deletion or content editing. Those live in other tools, on purpose, so the optimizer stays a safe operation on whatever you hand it.
- No password support. An encrypted file has to be unlocked before the engine can rewrite it, and the tool says so instead of producing a broken output.
Why a browser optimizer is a different trade
Server-based compressors have one real advantage: they can run a true image recompression pipeline in the background, which is why their marketing numbers exist. The trade is that the document goes to a machine you do not control, and for a contract, an invoice, a medical record or an ID scan, that is the part that matters more than a few hundred kilobytes. A local rewrite keeps the file where it was, works without a connection after the first load, and needs no account. When the structural rewrite genuinely cannot help, this page says so and points at the alternative, rather than inventing a number.