YAML to JSON Converter
Read a YAML config as JSON your tools can parse.
YAML
JSON
About the YAML to JSON converter
Paste a YAML file and read it back as JSON. Useful when you need to feed a Helm values file, a GitHub Actions workflow or a Docker Compose file into something that only understands JSON.
The parser covers the subset of YAML that configuration files actually use: nested mappings, sequences, quoted and plain scalars, block scalars, inline flow collections and comments.
What is supported
Nested maps and lists to any depth, `key: value` pairs, dash-prefixed sequences, inline `[a, b]` and `{a: 1}` collections, `|` and `>` block scalars, `#` comments and `---` document markers.
Scalars are typed the way YAML specifies: unquoted `true`, `false` and `null` become booleans and null, numeric literals become numbers, and anything quoted stays a string.
What is not supported
Anchors and aliases (`&name` / `*name`), custom tags, and merge keys are outside the subset handled here. Those are rare in hand-written config and would need a full YAML engine.
If your file uses them, the error message will point at the line so you know what to simplify.
Indentation errors
YAML derives structure entirely from indentation, so a single stray space changes meaning. When a line does not line up with the block above it, you get the line number and the offending text rather than a generic parse failure.
Frequently asked questions
Why did my version number become a decimal?
Unquoted `1.10` is a number in YAML, and numbers drop trailing zeros. Quote it in the source — "1.10" — to keep it as text.
Are tabs allowed for indentation?
Not in YAML, and not here. The specification requires spaces. Most editors can convert tabs on save.
Can I paste a Kubernetes manifest?
Yes, as long as it is a single document. For multi-document files, split them at the --- markers first.