JSON to YAML
- Safe quoting
- Config ready
- Nothing uploaded
Readable YAML, with the ambiguous values quoted so nothing changes meaning.
Paste input on the left to see yaml.
Everything runs in your browser — nothing is uploaded.
About to yaml
Converting JSON to YAML produces the format configuration files use. The risk is YAML's type coercion: no, on and off are read as booleans. JSONic quotes any string that would change meaning and emits empty collections explicitly as [] and {} rather than leaving a bare key.
YAML is what config files want. The risk in converting to it is YAML's type coercion: the strings no, on, off and y are read as booleans, and 1.20 loses its trailing zero. This quotes anything that would change meaning, and emits empty collections explicitly as [] and {} rather than leaving a key with nothing after it.
Questions
Which values get quoted, and why?
Strings that YAML 1.1 would read as booleans (yes, no, on, off, y, n, true, false), as null, or as a number. Without quoting, a country code of NO becomes the boolean false — a genuinely well-known source of production incidents.
Is the output safe to use as Kubernetes or CI config?
Yes for the data itself. Those systems expect specific top-level schemas, so the conversion gives you correct YAML, not a valid manifest.
Can I convert YAML back to JSON here?
Not yet. A YAML parser that quietly mishandles anchors, multi-line scalars or type coercion would be worse than not offering one, so that direction is waiting on a vetted parser.