Skip to content
MyPDFilesLocal PDF tools

Compress PDF

Compress PDF for Web

Try reducing a published PDF's download size without assuming every image will suit a low-resolution target.

Processed locally in your browser. Your file is not uploaded to any server. How this works

  1. 01Add your file
  2. 02Compress PDF for Web
  3. 03Download

Runs in your browser · nothing uploaded

About compress PDF for web

A PDF published on a website is a download, so reducing its bytes can shorten transfer time, especially on a slow connection. That does not translate directly into a predictable time to first page: progressive display depends on the viewer, server behaviour and file structure. This tool does not linearize PDFs for fast web viewing. Its fixed 72 DPI target is an aggressive image setting, not a universal match for browser display density. Fine scanned text, high-density screens, zooming and print can all need more detail. Supported images are downsampled only where placement can be measured, and may still be JPEG re-encoded below the target. Only smaller image replacements are accepted. JPEG quality is adjustable, while the displayed level selector is overridden by that explicit quality and the fixed DPI target. For another DPI target, use Compress PDF rather than changing the level here. Object-stream rewriting also runs, with limited metadata cleanup on by default. Cleanup targets eight standard Info keys and the catalog XMP reference; internal paths or other private data may remain in custom fields, page metadata, content or detached XMP bytes. The complete rewrite is returned only if smaller, otherwise the original bytes and metadata are unchanged. Inspect the returned PDF before publication and keep the master; reduced size is not proof of readability or sanitization.

How to compress PDF for web

  1. 01

    Add the document you intend to publish

    Add one unencrypted PDF, up to 250 MB and 5,000 pages. Image-heavy reports, brochures and guides may offer savings, but the result depends on their content and encoding.

  2. 02

    Check the fixed resolution target

    This page uses 72 DPI where supported image placement can be measured. It cannot be raised here; use Compress PDF if readers need more detail at zoom or in print.

  3. 03

    Set JPEG quality

    Start at 70% and inspect detailed images. Changing the level selector does not affect this page's explicit quality or fixed DPI settings; adjust the quality slider instead.

  4. 04

    Compress and publish

    Check the returned size and inspect the PDF before posting it. A -compressed.pdf download can contain the unchanged original, and limited metadata cleanup does not make it safe to publish automatically.

What this tool does

  • Fixed 72 DPI target for supported image downsampling, with a visible-detail trade-off to check
  • Limited metadata cleanup requested by default; hidden-data erasure is not guaranteed
  • JPEG quality remains adjustable; the level selector is overridden by explicit quality and fixed DPI
  • Output size reported before you publish, so you can judge it against your page budget
  • Runs locally, so unreleased documents are not uploaded to a third party during preparation

Limitations worth knowing

Every PDF tool has constraints. Stating them plainly is more useful than discovering them halfway through your work.

  • This tool does not linearize PDFs. Whether a viewer can show the first page before the full download completes depends on the viewer, server and file.
  • The fixed 72 DPI target may soften scanned text or images on high-density screens, at zoom or in print. It does not certify screen or print quality.
  • Without supported images to re-encode, any saving comes from structural rewriting and limited metadata cleanup. Little saving does not prove the PDF is already optimal.
  • Accepted image changes are lossy, so keep the master. This page accepts one unencrypted PDF up to 250 MB and 5,000 pages; browser memory can limit practical processing further.

How your file is handled

This tool runs entirely inside this browser tab. When you choose a file, your browser reads it from your own disk and hands the bytes to JavaScript running on this page — no network request carries your document anywhere. You can confirm that yourself: open your browser’s developer tools, switch to the Network panel, and run the tool. You will see no upload.

Nothing is stored after the fact. Closing or reloading this tab discards the file, the result and everything derived from them, because none of it ever left your machine. Read how local processing works.

Questions about compress PDF for web

Is 72 DPI enough for every web PDF?

No. It is a low-resolution target, not a universal browser pixel density. Images that look acceptable at one viewing size can become soft when zoomed, printed or shown on a high-density display, especially if they contain small scanned text. The setting only affects supported images where placement can be measured and a smaller replacement is accepted. Test the returned file in the viewing conditions you expect.

Should visitors be able to print the PDF?

If readers need to print, check the requirements rather than assuming this fixed 72 DPI target is suitable. Use the main Compress PDF page to choose a different target, or provide a separately checked print version alongside a lighter reading copy. Higher JPEG quality alone cannot restore pixels discarded by downsampling, and this tool does not validate print conformance.

Does a smaller PDF help my search ranking?

This tool cannot predict search rankings. A smaller returned PDF can reduce transfer size, but indexing and ranking depend on many factors outside compression. The engine does not deliberately edit text drawing operators; it can change text contained in images through lossy processing. Check readability and searchability yourself rather than treating a size reduction as an SEO guarantee.

What metadata could a published PDF leak?

PDFs may contain author and software details, company fields, timestamps, document IDs or file-system paths in several places. Publishing the file can expose that information. This page's cleanup targets eight standard Info keys and detaches the catalog XMP reference, but other stores and detached XMP bytes may remain. It is not secure sanitization, and an unchanged-original result retains all original data. Inspect the returned file before publishing.

Tools that pair with this one

Read more about this

Background