Why local PDF compress matters

PDFs often hold contracts, IDs, medical letters, or drafts you would not paste into a random upload form. A local compressor reads the file with the browser File API and never sends the bytes to our servers. That is the privacy story for LocalPdfCompress: structural rewrite stays in the tab. This page says what that does and does not change. It is not a claim that the documents become anonymous, or that nobody can ever see them.

For a step-by-step DevTools checklist with expected vs problem requests, use the dedicated trust page. The policy wording is in privacy.

Why choose a local PDF compressor (no upload)

Use one file you are willing to inspect, such as a short public PDF or a non-sensitive sample. Do this on the home tool.

1. Open the browser’s network panel. You do not need to reload. If the page assets are already cached, the list may stay short, and that is fine.
2. Drop the file. Mode changes stay in the page. They are not saved to an account.
3. Compress. The status line reports progress. That work is local.
4. Look at the request list. You may see the document, the stylesheet, tool.js, and pdf-lib.min.js from this host if they were not cached. You should not see a POST or PUT whose body is your PDF.
5. Download. The link is a blob: URL created in the tab from the PDF bytes, then the browser saves the file into your downloads folder. That folder is outside the no-upload claim. A synced downloads folder can copy it to a cloud drive you configured.
6. Press Clear, or close the tab. The in-memory selection is dropped. We cannot send the PDF back to you later. It was never received.

What the host still sees when compress stays local

You pick a PDF with the file picker or by dropping it. The tab reads the bytes and rewrites pages with pdf-lib. The finished PDF is a Blob handed to URL.createObjectURL for the download link. There is no document URL field and no server-side fetch of a remote PDF. Closing the tab ends the session state because nothing was written to account storage. There is no account.

Hosting still delivers the static site from Cloudflare Pages. That delivery can include an IP address and the URL of the page in ordinary request logs. Those logs are not your document. Optional Cloudflare Web Analytics, if it is enabled, is described by its vendor as privacy-first analytics that does not collect or use visitors’ personal data. It is a page-view beacon, not a copy of the PDF. Details are in the privacy policy. Response headers also set a Content-Security-Policy with script-src 'self' that does not list an advertising script host.

No-upload is not the same as secrecy

Shoulder surfing, malware, a shared computer, and a file you later email are all still ways the document gets out. A private browsing window still processes the file locally and still writes a download if you save one. It does not change this design. Local compress removes a converter company’s copy of the bytes during the process step. It does not lock the room, and it does not redact pages you left in the packet.

Sensitive-document habits still matter. Prefer a local compress when the packet includes personal identifiers, draft contracts, or anything your organization treats as confidential. Soft size limits (~25 MiB) are honesty about browser memory — not an invitation to push huge archives into a tab on a shared phone. Image downsampling is still not in this version; privacy and shrink strength are separate axes. See honest limits.

Local compress for email and tickets

Many privacy-sensitive packets also need to become attachments. Local rewrite lets you try a smaller PDF without uploading the draft to a converter first. You still choose whether to send the download. Mail and ticket systems you send to are outside this page’s no-upload claim. Rights in the document remain yours to respect — local processing does not grant a license. Terms: terms. Practical steps: compress without uploading and reduce file size.

What we do not claim

• Not a substitute for your organization’s DLP tools, MDM policy, or certified redaction workflow.
• No claim of 等保 certification, e-discovery readiness, or regulatory compliance.
• Not a DRM bypass, password cracker, or “unlock any PDF” service.
• If a document must never touch a browser, use offline desktop software on a machine that matches your policy.
• Not a guarantee the file shrinks; keep the smaller of before/after.

The same engine, different stakes: compress without upload, reduce file size, and limits. Publisher and contact: about · contact.

Publisher-review clarity without changing the no-upload design

Reviewers and careful readers look for a working contact address, an about page that names the publisher, and privacy/terms that match the product. Those pages exist on this site and stay on the same URLs. This experiment does not run advertising scripts today; if that ever changes, privacy and about would need an honest update first. Until then, treat “no ads on this pages.dev experiment” as the published rule.

Local compress is still a browser. Extensions, malware, or a screen recorder you installed can see what the tab can see. LocalPdfCompress does not receive the file, and it does not claim to block other software on the device. Files never leave this device through this page — that is the claim you can verify on trust.