Contact
One address, read by a person. No ticket numbers, no chatbot, no form that silently drops your message.
There is deliberately no contact form on this site — a form would need a backend, and the whole point of these tools is that nothing gets transmitted. Email works better anyway: you get a copy of what you sent, and attachments such as a screenshot or a sample file arrive intact.
Reporting a bug
Bug reports are the most useful thing you can send. To make one actionable, please include:
- Which tool — the page name, or the URL from the address bar.
- What you expected and what actually happened. “It gives the wrong hash” is hard to act on; “MD5 of the empty string returns nothing instead of d41d8cd98f00b204e9800998ecf8427e” is a fix in ten minutes.
- A minimal example that reproduces the problem. Strip out anything confidential first — a two-line snippet is almost always enough.
- Browser and operating system, including version. Behaviour can differ between Chrome, Safari, and Firefox, particularly around clipboard access and image decoding.
- A screenshot, if the problem is visual or an error appears in the developer console.
Please do not send real credentials, private keys, or customer data, even as an example. Substitute fake values of the same shape — the tool cannot tell the difference, and the fix will be the same.
Requesting a tool
Suggestions are welcome, and several tools on the site started as a request. A request is much more likely to be built if it describes the actual task rather than the interface: “I need to turn a folder of product photos into WebP at 800px wide” is more useful than “add a WebP tool”. It also helps to say whether the job has to stay in the browser — anything involving a heavy library, a large model, or server-side computation is a different kind of project.
Not every request gets built. Tools that would need an account, a payment, or a server are usually out of scope.
Privacy and data questions
If something in the privacy policy is unclear, or you believe the site is handling data in a way it should not, write to the same address and put “privacy” in the subject line. Reports of that kind are treated as a priority.
Copyright and takedowns
If you believe content on this site infringes a right you hold, send the details — the URL, the work in question, and your basis for the claim — and it will be reviewed promptly.
Response time
This is a small independent project, not a support desk. Most messages get a reply within a few days. Bug reports with reproducible examples are answered first; general enquiries sometimes take longer, and there is no guaranteed response time.