Does browser-local compression work on large PDFs?

It depends on your device's available memory. The current free limit is 100 MB per file. A Day or Project Pass raises that ceiling. Very large PDFs (hundreds of pages, high-resolution scans) may hit browser memory limits regardless of the pass.

Will I lose text quality?

In Preserve mode, selectable text, links, bookmarks, and form fields are kept intact. In Aggressive mode, pages are rasterised to images, which removes selectable text and structural elements. Choose based on what matters for the output.

Is my PDF uploaded to a server?

No. The Compress PDF tool processes the file entirely in your browser. The source file stays on your device. No upload, no server queue, no file-retention question.

How much smaller will the file get?

Compression ratios vary by content. A scan-heavy PDF may shrink 60-80% in Aggressive mode. A text-heavy PDF with small images may shrink 10-30% in Preserve mode. The tool shows the result size before you download.

Browser-Local PDF Compression: How It Works

What browser-local PDF compression means

When you compress a PDF using the Compress PDF tool on NiftyWebTools, the work happens inside your browser. The file is read into memory, processed using JavaScript libraries running in the tab, and the compressed result is offered for download — all without the file leaving your device.

This is different from most online PDF compressors, which upload the file to a remote server, process it there, and return the result. The hosted model works, but it means the file travels over the network and sits on someone else's infrastructure for at least the duration of processing.

Browser-local compression removes that step. The file stays on your machine from start to finish.

How it works under the hood

The tool uses pdf-lib (for structural PDF manipulation) and browser-native canvas APIs (for image re-encoding) to process the file entirely in JavaScript.

The workflow:

1. You select or drop a PDF file. The browser reads it into an ArrayBuffer in memory.

2. The tool parses the PDF structure — pages, fonts, images, form fields, metadata.

3. Depending on the compression mode, it either re-encodes embedded images at lower quality (Preserve mode) or rasterises each page into a compressed image (Aggressive mode).

4. The result is assembled into a new PDF and offered as a downloadable blob.

5. When you close the tab or navigate away, the browser discards the working memory.

No network request carries the file content. No /api/upload call is made. The only network calls the page makes are the static page load and, if you accepted telemetry consent, an anonymous tool_used event counter.

Two compression modes

Preserve mode

Preserve mode re-encodes images embedded in the PDF at reduced quality while keeping the document structure intact. Selectable text stays selectable. Links, bookmarks, and form fields survive the compression. The page layout does not change.

This mode is right when:

The document has selectable text that readers need to copy or search.
The PDF contains links, form fields, or bookmarks that must work in the output.
You want a smaller file without losing document structure.

The tradeoff is compression ratio. Preserve mode reduces file size by shrinking images, but if the PDF has few images (or they are already compressed), the reduction may be modest.

Aggressive mode

Aggressive mode rasterises each page into a JPEG image, then reassembles those images into a new PDF. The output looks like the original pages, but every page is now a flat image — no selectable text, no links, no form fields, no bookmarks.

This mode is right when:

The PDF is a scan or a collection of image-heavy pages where text selection does not matter.
You need a much smaller file and can accept the structural loss.
The document will be viewed or printed, not edited or searched.

The tradeoff is real: you lose everything except the visual appearance. A form becomes an image of a form. A link becomes a picture of a link. Choose Aggressive only when you understand what it removes.

What browser-local compression does not do

Browser-local compression has genuine limitations:

No OCR. If the input PDF is a scan (image-only), Preserve mode cannot extract or index the text. The tool does not add text where none exists. OCR requires a server-side or AI-powered pipeline.
No font subsetting. The tool does not remove unused font glyphs. If the PDF embeds a full font file, that weight stays in the output.
No linearisation. The output PDF is not linearised (optimised for fast web viewing). Linearisation is a server-side optimisation that some hosted tools offer.
Memory-bound. The browser has finite memory. Very large PDFs (hundreds of pages, high-resolution images) may cause the tab to slow down or crash. The current free limit is 100 MB per file for this reason. A Day or Project Pass raises that ceiling, but the browser's physical memory is still the hard constraint.

Hosted PDF compressors can offer features that browser-local tools cannot, because they run on a server with more memory, disk, and access to specialised libraries. That is the core tradeoff: browser-local removes the upload step, but it also removes the server's capabilities.

When to use browser-local compression

Browser-local compression is the better choice when:

Privacy matters. Contracts, invoices, client documents, medical records, financial statements — any file where uploading to a third party adds review friction.
Speed matters. No upload, no server queue, no download wait. The result appears as soon as the browser finishes processing.
The task is simple. Compress a few files, download the results, move on. No account, no project, no workflow.

It is the worse choice when:

The file is very large. A 500-page scanned document at high resolution may exceed browser memory.
You need OCR, font optimisation, or linearisation. Those require server-side processing.
You need batch processing at scale. Processing 100 files sequentially in a browser tab is possible but slow compared to a server pipeline.

Try it

Open Compress PDF, drop a file, choose Preserve or Aggressive, and download the result. The tool shows the original and compressed sizes so you can see the tradeoff before committing.

If the file exceeds the free limit, a Day or Project Pass raises the ceiling for that session. No account, no subscription.

For sharing compressed files via QR code, see the companion guide: How to Make a QR Code for a File.