Shard Tools

How to compress a PDF locally in your browser

By Roshan · Updated

Compressing locally means your browser processes the PDF on your device. This guide shows how to check that boundary and inspect the resulting document, not just its smaller file-size label. Keep the original as a separate file before starting.

Compress a PDF to 200 KBCompress a PDF to 300 KBRead the privacy policy

Choose the local browser workflow

Open a browser PDF compressor and read the receiving site's maximum bytes and page requirements. Shard Tools uses 1 KB = 1,024 bytes: a 200 KB target means 204,800 bytes. For a strict 200,000-byte allowance, choose 195 KB or less and check the downloaded file's actual size.

This workflow is different from Edge Assisted MCP. Those remote actions send file bytes to Cloudflare for processing. Opening a browser-local compressor does not require using the MCP endpoint.

Observe the network while processing

Before selecting a document, open developer tools and the Network panel. Clear the log, select a non-sensitive sample PDF and run compression. Inspect any new requests and their payloads. File selection and processing should not produce a request carrying the PDF bytes.

Scripts, fonts and processing libraries may download when a page or tool starts. A request appearing in the log is not automatically a file upload, and an empty built-in counter is not a complete security audit. Repeat the check for the specific action you intend to use.

Understand a smaller result

A structural rewrite may preserve selectable text but save little on an image-heavy scan. Raster compression redraws pages as images and can reduce quality and dimensions. It can also remove selectable text, interactive forms or links. A modified document should not be assumed to retain a valid digital signature.

For a ten-page PDF targeting 300 KB, the average budget is only about 30 KB per page before shared overhead. That arithmetic is a warning about the constraint, not a prediction that every page will remain legible.

Check the downloaded PDF

Open the saved output independently. Confirm the page count and order, zoom into small text and tables, and test any text selection or form behavior you need. Compare measured bytes with the limit; a download button alone does not prove the target was reached.

If the result is over the limit or illegible, keep the original. Ask the recipient whether a larger allowance or separate page batches are acceptable. A large document can also exceed your browser's available memory; a smaller batch helps only when the recipient permits it.