Contact
We read everything that arrives. Please don't attach real personal documents — a description of what went wrong is more useful and safer for you.
Reporting a problem with a tool
The most useful report tells us which tool you used, what you expected, what happened instead, and which browser and operating system you were on. If a conversion produced something odd, a description of the source document's structure — how many pages, whether it was scanned, whether it had tables — helps more than the file itself.
Requesting a feature
Tell us the task you're trying to finish rather than the feature you have in mind. It often turns out an existing tool covers it, and when it doesn't, the underlying task tells us how to design the new one.
Response times
This is a small project. We aim to reply within a few business days, and security reports come first.