We read everything that comes in. There is no ticket system and no chatbot — messages go to a person.
Reporting a problem with a tool
Because the tools run inside your browser, the details below make a bug far easier to reproduce. Please include what you can:
- Which tool, and the address of the page
- Your browser and version, and whether you are on desktop or mobile
- The file type and roughly how large the file was
- What you expected to happen, and what happened instead
Please do not attach the file itself unless you are comfortable sharing it — a description of its type and size is usually enough.
Requesting a tool
Suggestions are welcome, and requests genuinely shape what gets built next. The most useful ones explain the task you are trying to finish rather than the feature you have in mind — knowing that you need a photo under 100 KB for a visa application tells us more than “add a compressor”.
Reporting a security problem
If you find something that could put a visitor at risk — a way to make the page load code it should not, a file that leaves the device when it should not, a broken content security rule — send it to the same address with “security” in the first line. Please include the steps to reproduce it and give us a reasonable chance to fix it before publishing. We have no bug bounty to offer, but we will credit you on the fix if you want to be named, and we will tell you when it is deployed.
What we cannot help with
- Recovering a file. Nothing you open here reaches us, so there is no copy to retrieve. If a tool overwrote your only version, the original is gone — work on duplicates when a file matters.
- Accounts, subscriptions or billing. There are none. If an email claims you owe Filewhisk money, it is not from us.
- Legal or official advice. We can explain what a passport authority publishes or what an electronic signature law says, and we link the sources — but we cannot tell you whether your specific document will be accepted.
- Doing the work for you. Send us the problem rather than the file: we are not set up to receive documents, and would rather you did not send them.
What happens after you write
Messages go to a person, not a queue. Bug reports with reproduction steps usually get a reply within a few days and are fixed in the order of how many people they affect. Tool requests are collected and reviewed when the next batch of tools is planned; if yours gets built you will hear about it. We do not promise a response time, and we would rather say that plainly than publish a number we cannot keep.
Business enquiries
For advertising, partnership or press enquiries, use the same address and put the subject in the first line.