Contact

Last updated: 12 September 2026

One address, read by the person who builds and runs this site.

Good reasons to write

Bug reports — output that looks wrong, a parser error you believe is incorrect, or a browser where the page misbehaves.
Feature requests — capabilities you are missing, and why the current output does not cover them.
Privacy and data questions — anything about what the page does or does not collect, including the analytics described in the privacy policy.
Accessibility — contrast, keyboard navigation or screen-reader problems are treated as bugs.
Report a problem with the service itself — if you believe this site is being abused or served incorrectly.

Helpful things to include

For a bug report: the browser and version, roughly how large your input was, and the smallest JSON snippet that still reproduces it. A snippet that reproduces the issue is worth far more than a description of it.

Please do not send your data expecting us to look at it. The tool never sees what you paste, so it usually cannot help. If you lost JSON you had only in the input box, we cannot recover it — there is no copy anywhere but your browser.

Response time

Usually within a few working days. It is a one-person project without a support desk, so some messages get a longer answer than others; anything about correctness or privacy is prioritised.