JSON to YAML Converter

How this reads your output

The direction is detected from what you paste, so this converts both ways without choosing a mode. The care is in the output: any string that YAML would read as another type gets quoted. That covers yes, no, on, off, anything numeric, and version strings, all of which would otherwise change type on the way through and produce a configuration file that is subtly not what you wrote.

What the results mean

Ambiguous strings quoted

Values that YAML would otherwise retype. Each one would have been a silent change, which is why the count is worth a glance.

Nesting depth

How deep the structure goes. YAML indentation errors get harder to spot with depth, so deeply nested configuration is worth restructuring.

Keys

Total keys across the structure, a rough measure of how much configuration is involved.

Common problems and fixes

A country code or a version number changed meaning

YAML retyped it. The code NO becomes the boolean false, and the version 1.10 becomes the number 1.1. Quoting fixes both, which this converter does automatically in that direction. The rule to remember: anything that looks like a number or a boolean but is really an identifier must be quoted.

A converted file will not load

Check for tabs, which YAML forbids for indentation and rejects rather than interpreting. Then check depth, since a single misaligned line changes which parent a key belongs to without any syntax error. Both are why editors need a YAML mode configured for spaces.

Frequently asked questions

More in DevOps

• JSON Formatter / ValidatorFormat and validate JSON — with the error pinned to a line and column.