Browser-only workflow

Compress PDFs locally by re-rendering pages in the browser

Rasterize each page on this device, tune DPI and JPEG quality, and download a smaller PDF without sending files to a worker.

UseKit Home Open workspace Tradeoffs

Compression settings

Open one PDF, choose a preset, then rebuild a JPEG-backed PDF locally. Searchable text, links, and forms will be flattened into page images.

Local processing No upload Strict-smaller fallback
Preset
Select a PDF to start.

What this tool does

This workflow rasterizes each page locally, recompresses it as image-backed PDF output, and helps you shrink scanned or image-heavy files without sending them to a server.

Best for

  • Scanned or image-heavy PDFs where file size matters more than text selection.
  • Email and web sharing where local-only handling matters more than native PDF structure.
  • Reducing uploads from phones, scanners, or office copiers before handoff.

Not for

  • Interactive forms, accessible PDFs, or documents that must keep real text semantics.
  • Contracts, manuals, or reports where link targets and annotations must remain native.
  • Workflows that need exact PDF internals preserved instead of a smaller visual copy.

Input

Open one PDF at a time, preview the first page, then choose a preset or custom render settings such as DPI, JPEG quality, grayscale, and strict-smaller fallback.

Output

The result is a newly built compressed PDF plus a local summary of size change, render profile, fallback attempts, and final page-render facts.

How to use

  1. Select the PDF and confirm the first-page preview looks right.
  2. Start with a preset, then adjust DPI or JPEG quality only if the preview suggests it.
  3. Run compression, compare size and legibility, then download the final PDF if the tradeoff is acceptable.

Privacy / local processing

  • The PDF stays in the browser session unless you explicitly download the result.
  • No worker deployment or external upload is required for this local path.
  • Compression runs with pdf.js rendering and pdf-lib output assembly on this device.

Limits / tradeoffs

  • Each page becomes a rendered image, so searchable text, links, annotations, and forms are flattened.
  • Very low DPI or aggressive JPEG settings can damage barcodes, signatures, and fine print.
  • Strict-smaller helps avoid pointless downloads, but it does not guarantee the output is good enough for every workflow.

FAQ

Will this help with scanned PDFs from copiers or phones?

Yes. That is the main use case, especially when most of the file is already page imagery.

Will selectable text and form fields survive?

No. The compressed result is rebuilt from rendered page images, so native PDF text and fields are flattened.

Why can the result still be large?

Some PDFs already use efficient image compression, and conservative settings may keep more detail on purpose.

Should I keep the original file?

Yes. Keep the original whenever you may need searchable text, better print fidelity, or a second pass with different settings.

Last updated

April 5, 2026