Contact for privacy, bugs, a11y
Email contact@localpdfcompress.pages.dev. This is a small static site on localpdfcompress.pages.dev, so a reply can take days, not minutes. There is no phone line, no live chat, no ticket portal, and no account dashboard. You can use the PDF compressor without ever writing to us.
What to write about
- Privacy wording. A sentence that does not match how compress behaves. Start from the privacy policy and the DevTools walk-through on trust.
- Broken page or wrong limit. A control, soft cap, or format rule that does not match the description on the tool (about 25 MiB per file, PDF only, structural rewrite only, no image downsampling, no password bypass).
- Accessibility. Keyboard use, labels, focus order, or contrast on the teal and coral pages.
- Guide corrections. A wrong step in compress without upload, reduce file size, limits, or local privacy.
What we cannot do from email
We cannot recover a compressed PDF. Processing never uploaded the file. Clear, a reload, or a closed tab drops the only copy that was in memory. Keep the download if you need it.
Do not email contracts, ID scans, medical letters, or unredacted packets. We do not need them to fix a sentence, and the mailbox is not a private converter. If a privacy question needs a Network-panel check, use a non-sensitive sample on your own device and describe what you saw.
We also cannot compress a file for you, crack a password, bypass DRM, run OCR, downsample images on a server, promise a typed email megabyte target, or raise a cloud memory quota. Those are outside this version, not a queue you can reach by mail. Limits and out-of-scope items are listed on the home page and in the terms.
What to include so a reply is possible
Name the page URL, what you expected, and what the browser did. Browser name and device type help when the failure looks like memory (“the tab reloaded after a large PDF on a phone”). If a sentence on the site is wrong, quote it. You can leave the PDFs out.
Useful extras, still without attaching the documents:
- Whether you used structural rewrite or rewrite + metadata strip, and roughly how many pages.
- Whether before/after grew or shrank (numbers from the size panel are enough).
- Whether the file was a normal PDF or something encrypted / damaged that the tool skipped.
- For a privacy concern: whether DevTools → Network showed a POST/PUT of the file (see trust).
- Whether you were trying to hit an email size limit — and the after size you saw — so we know if the wording on limits is unclear.
Common questions that are already answered on the site
- Encrypted PDF rejected. Unlock a copy you are allowed to open with another tool you trust, then compress that unlocked copy here. This is not a password bypass.
- File got larger. That can happen with structural rewrite. Keep the original. See limits.
- Signatures or bookmarks missing. The result is a new page-copy document. Check those separately before you share.
- Still too big for email. This MVP does not downsample images or take a megabyte target. See reduce file size.
- Did compress upload my file? Run the check on trust and read why a local PDF compressor matters.
After you write
A short acknowledgment may take a while. There is no service-level agreement. If the issue is a factual error on a public page, fixing the page is the goal. If you asked us to process a private PDF, we will decline — please use the on-device tool instead.