Contact
How to contact json-yaml.com. Bug reports, format requests, and corrections to the reference material are all welcome.
Get in touch
One address, read by a person. Expect a reply within two working days.
What is useful to include
Reporting a bug
The smallest input that reproduces it, which page you were on — the JSON validator and YAML validator are the usual suspects — and what you expected instead. A three-line document that fails is far more useful than a three-hundred-line one. If the input contains anything sensitive, replace the values before sending — the structure is what matters.
Requesting a format or a feature
Tell us what you are actually trying to do, not only the format pair. Knowing that you are converting Terraform output for a policy check leads to a better tool than knowing you want HCL support.
Correcting the documentation
Quote the sentence and say what is wrong with it. These get fixed fastest.
What we cannot help with
We cannot debug your specific configuration file, review your infrastructure, or advise on your deployment. For those, the tool vendor's documentation or a community forum will serve you better. Bug reports about this site, however, are always welcome.
No newsletter, no sales list. Your address is used to reply to you and nothing else.