About this site
About json-yaml.com: a set of format converters that never send your documents anywhere, and reference notes written to be correct rather than exhaustive.
Why this exists
Most online converters take your document, post it to a server, and send the result back. For a public API response that is fine. For a Kubernetes secret, a database connection string, or a config file from a private repository, it is a data transfer to a third party that you did not intend and cannot audit.
Every converter on this site runs in your browser. The page loads a parser, and the parser runs on your machine. There is no endpoint to send anything to.
How it is built
- Static HTML and CSS, generated ahead of time. No framework, no hydration.
- YAML parsing by js-yaml, served from this domain rather than a CDN.
- JSON parsing by the browser's native
JSON.parse, which is what the JSON validator reports errors from. - CSV, XML, and TOML handling written for this site.
- No analytics that identify you, no advertising network, no third-party scripts. The open-source projects behind it are credited on the attributions page.
- Built to WCAG 2.2 level AA and tested on every release; the accessibility statement sets out how, and what still has rough edges.
- Nothing is stored. Reload the page and your document is gone.
About the writing
The reference material on this site is written to be correct rather than comprehensive. Where a conversion is lossy, that is stated. Where a format cannot represent something, that is stated too, instead of silently guessing.
If you find something wrong — a bad claim, a broken example, a parser behaviour that does not match what is described — please write in. Corrections are the most useful mail this site gets.