Contact

FilesProcess is run by one person, and that person reads the mail. There is no ticket system and no bot in front of it.

Reporting a tool that got it wrong

This is the most useful mail you can send, and the one most likely to turn into a fix. Please do not attach the file – the whole point of this site is that your documents stay with you, and that applies to the inbox too. What actually helps:

• The tool page you used, e.g. /pdf/pdf-to-word.
• What you expected the output to be, and what it actually was.
• Your browser and device – “Chrome on Windows”, “Safari on an iPhone”.
• Roughly how big the file was, and whether it was scanned or digitally created.
• Any message the page showed you, copied out as text.

If the file is one you can share – something you made up for the test rather than a real document – say so and I will ask for it. Most bugs are reproducible from the description alone.

Before you write: three answers that are already published

• “Is my file really not uploaded?” How it works shows you how to check it yourself in two minutes, and the upload test measures what other tools send.
• “Why can’t it do X?” Each tool page has a limitations section, and privacy and limits collects the ones that apply to every browser-based tool.
• “Is it free / is there a catch?” It is free, there is no account, and about explains what pays for it.

Suggesting a tool

Worth sending, with one thing included: what you were trying to get done when you went looking for it. A tool request on its own is a guess; the task behind it usually says whether the browser can do the job at all.

Press, takedowns and everything else

Same address. FilesProcess stores no user documents and operates no accounts, so there is rarely anything to take down – but if something on the site itself is wrong, say which page and I will correct it.