Contact

There is no support ticket system and no chatbot — just addresses that reach a person. Pick the one that fits and you will get a faster answer.

Something is broken

A tool failed, produced a bad file, or behaved strangely. Tell us which tool, which browser, and roughly what the file was like — page count and whether it was scanned is usually enough. Please do not attach the document itself.

hello@pdfspree.com

A tool you need that we do not have

The roadmap is genuinely shaped by these. Describe the job rather than the feature — what you are trying to get done matters more than what you think the button should be called.

hello@pdfspree.com

Privacy and your data

Questions about what we hold, or a request to access, correct or delete personal data. We hold very little: files processed without an account are deleted automatically, and files stored against an account are yours to delete whenever you like.

privacy@pdfspree.com

Security disclosure

Found a vulnerability? Send enough detail to reproduce it. We will not pursue anyone reporting a genuine issue in good faith who gives us a reasonable chance to fix it first.

security@pdfspree.com

Legal and copyright

Copyright notices, counter-notices and anything else legal. Sending these here rather than to the general address is what stops them sitting in a queue.

legal@pdfspree.com

An accessibility barrier

If something stopped you completing a task, we want to know what you were trying to do and what happened. These are treated as bugs, not feature requests.

accessibility@pdfspree.com

Before you email

Two questions come up often enough to answer here. If a tool says your file is encrypted, it is password-protected and has to be unlocked before anything else can read it. If a converted document came out with the layout scrambled, that is conversion being lossy rather than a fault — the file handling page explains where each tool’s limits are.

Please do not send us your documents

We do not need your file to investigate a bug, and we would rather not hold a copy of it. Describe what happened instead. If a file is genuinely required to reproduce something, we will ask, and we will tell you what happens to it first.

What to expect

A real reply, from a person, though not instantly — this is a small operation. Security reports get looked at first.