The form
Write to us
Pick a topic and draft the message; the button hands it to your own mail client with the subject line already set. Nothing is transmitted, stored or queued by this site on the way, because there is no backend that could do it.
Subject line: [Tool issue] · Nothing is sent until your mail app does it. This form has no server behind it.
Topics
Where each request belongs
All five topics arrive at the same inbox and get handled by whoever maintains the relevant part of the site. The prefix in the subject line is what sorts them.
| Topic | Subject prefix | Who reads it | What happens next |
|---|---|---|---|
| A tool produced wrong output | [Tool issue] | The maintainer of that converter | A reproduction is built from your description, then the fix ships with the next deploy |
| A guide or comparison is inaccurate | [Correction] | Whoever wrote the page, against the cited clause | Checked against the specification clause, not another blog post |
| A converter or format is missing | [Feature request] | Backlog owner | An honest yes or no, rather than an open-ended maybe |
| Licensing or reuse of the written material | [Licensing enquiry] | Site operator | Scope of reuse answered in writing before anything is republished |
| Cookies, data handling, policy questions | [Policy question] | Site operator | Answered from the policy pages, and those pages get rewritten if the answer is not there |
Bug reports
What makes a report actionable
A converter failing on one document and failing on all documents are different bugs with very different fix costs, and the only way to tell them apart is the reproduction. Include:
- The page URL, so the right tool is obvious (several formats share a name across categories).
- What you pasted — its shape and the offending construct, not the file. Ten lines that trigger it beats ten megabytes.
- What came back, and what you expected instead. "It threw" is a start; the error text quoted from the panel is better.
- Which browser and version, and whether the input came from another tool, a database export, or a spreadsheet.
- For size or precision complaints: the payload size and the largest number or longest string involved.
Architecture
Why there is no contact form backend
Every page here is a static file and every tool is JavaScript that runs in the tab. There is no application server, no database and no inbound endpoint, which means a conventional "send" button would have to talk to something that does not exist. Adding one would put a form handler, a datastore and a retention problem in front of a site whose privacy position is that it receives nothing.
The consequence for you is small: the message sits in your draft folder until your mail app sends it, and the thread lives in your mailbox rather than a ticket system you would have to log into later.
Boundaries
What we cannot do
- Recover your data. Nothing you convert reaches us, so nothing can be returned. Backups stay your side of the line.
- Give a response-time guarantee. There is no support contract, no SLA and no phone queue. Mail is read on working days and answered by whoever maintains the affected page.
- Sign compliance paperwork on request. No ISO or SOC attestation exists, and there is no processing agreement to sign, because no processing happens on our infrastructure.
- Debug your file remotely. Without seeing the input — which you should not send — the useful output is a minimal reproduction from you plus the rules the guide cites.
After you write
How corrections are handled
A confirmed error in a guide is fixed against the specification clause rather than against another blog post, the source list on that page gains or repairs the citation, and the page's Updated date moves. When a converter changes behaviour in a way that could alter output, the tool page says so in the same pass. If you reported it, you get the answer in the thread you started.
Policy and data questions are answered from the cookie policy; the terms of service cover what the tools license you to do. The address for anything the pages do not settle is [email protected].