Contact
Email: hello@getpdflocal.com — this is the only contact channel, and messages are read by the person who writes the tools.
Because every tool runs on your own device, there is no server log, no job record and no stored file for us to look up. A message is the only way a problem reaches us, so it is worth writing one properly.
Please do not send the document
This is the one firm rule. There is no need to attach the file — the entire point of the site is that we never receive your documents, and an inbox is a far worse place for a passport scan or a signed contract than your own laptop. Describe the file instead: what kind of PDF it is, roughly how many pages, whether it was scanned or digitally generated, whether it is encrypted, and what produced it — Word, LaTeX, a scanner app, another converter. That is almost always enough to reproduce the problem.
Reporting a bug
A report that can be acted on contains:
- The tool you were using, by name.
- Your browser and version, and your operating system.
- What you expected to happen, and what happened instead — including the exact wording of any message shown.
- Whether the problem is reproducible, and if so, whether it happens on every file or only one.
- Anything unusual about the file, described as above.
If a conversion produced a visibly wrong result, the single most useful addition is an image of the output with the wrong region circled — with any confidential content cropped or covered first.
Requesting a tool
Requests for tools that do not exist yet are welcome and are read properly. What makes one actionable is the reason behind it: describe the job you are trying to finish, not just the feature name. "Stamp a date and a reference number on 300 invoices without opening each one" is a specification. "Add batch processing" is not.
Corrections and factual errors
The guides aim to be technically accurate and they state their limits on purpose. If one is wrong, overstated, or out of step with the current PDF specification, say so, and point at the clause or source if you can. Corrections are applied to the page and its review date is updated. A page that turns out to be wrong is corrected rather than quietly deleted.
Response times
This is a small project, so replies are not instant. Real messages are read and answered, usually within a few days. A message containing reproduction steps will always be answered faster than one that does not.
Security
If you believe you have found a security problem, put the word "security" in the subject line and describe the issue and its impact. Please do not test anything against third-party services while reporting, and do not include working exploit code aimed at anyone else's systems.