Skip to content
hushvert

YAML converter

YAML and JSON convert in your browser, losslessly and privately. Nothing is uploaded; the conversion happens on your device.

What is YAML?

YAML is a human-friendly data format built for configuration: indentation instead of braces, comments, and a clean look that made it the default for Kubernetes, Docker Compose, and CI pipelines. It maps one to one onto JSON, so the two convert losslessly. People reach for YAML when a human has to read and edit the file by hand.

Convert YAML to another format

Convert another format to YAML

Common questions about YAML

What is YAML and where is it used?
YAML is a human-readable data format that uses indentation instead of braces and brackets. It carries the same data model as JSON but is easier for people to read and edit, and it allows comments. You see it most in configuration: CI pipelines, container and infrastructure configs, and application settings.
Can I convert YAML to JSON without uploading it?
Yes. YAML converts to JSON and back, and both directions run client-side in your browser in pure JavaScript, so nothing uploads. That is genuinely useful for a config file that contains tokens or secrets: the bytes stay on your device, verifiable in the Network tab or via the airplane-mode demo on /privacy-proof.
Why convert between YAML and JSON?
JSON is what machines and APIs usually expect; YAML is what people prefer to hand-edit. Converting YAML to JSON gives you a machine-friendly version of a human-written config, and JSON to YAML gives you a readable version of API output. The underlying data is preserved either way.
Are comments kept when I convert YAML to JSON?
No. JSON has no syntax for comments, so any comments in your YAML are dropped when you convert to JSON. The actual data (keys, values, structure) is preserved exactly; only the human annotations are lost, because the target format cannot represent them.
Does my YAML need to be valid first?
Yes. YAML is indentation-sensitive, so use consistent spaces (not tabs) and even nesting. The conversion parses the file first and stops on a syntax error rather than guessing. If a file will not convert, an indentation or colon-spacing mistake is the usual cause.