Contact
One address for everything — bug reports, requests for a decoder we do not have yet, corrections to an explainer, or a question about how something works.
Last updated
Email us
contact@decoder.toolsWe read every message and reply to the ones that need a reply, usually within a few working days.
What to write about
- A decoder is wrong. Tell us which tool, what you put in and what you expected out. A sample input that reproduces it is worth ten paragraphs of description — as long as it contains nothing sensitive.
- A format is missing. Name the format and, if you can, point at the specification. Formats that several people ask for get built first.
- An explainer is inaccurate. Field widths, standard numbers, deprecated advice — if something on a tool page is wrong or out of date, we want to know and will fix it.
- A security issue. Report it privately to the same address and give us a reasonable window to fix it before disclosing publicly.
- Anything else. Questions, press, partnerships and general feedback all arrive at the same inbox.
Please do not send us live secrets
Do not paste production tokens, private keys, real customer data or anything else confidential into an email. We do not need it to reproduce a bug, and email is not a safe channel for it. A redacted sample, or a synthetic input that shows the same behaviour, is always enough.
This matters more here than on most sites: the whole point of decoder.tools is that sensitive data never leaves your machine. Emailing it to us would undo exactly that.
Answers you may not need to wait for
A lot of questions are already answered on the site. Each tool page has a FAQ section covering the questions people ask about that specific format, the privacy policy covers what is and is not collected, the terms of use covers the legal position, and the about page explains why everything runs locally.
Looking for a tool? The full catalog is searchable by name, format and keyword.