JSON to YAML Converter

When another program reads the YAML

A string is quoted whenever a YAML 1.1 or 1.2 reader could take it for something else. That covers yes, no, on, and off in any case, the single letters y and n, null and ~, numbers with leading zeros such as 0123, hex and octal forms, and dates and times such as 2024-01-05 or 12:30. PyYAML, which many Python tools and Ansible use, would otherwise read on as true and 0123 as the octal number 83. JSON numbers, booleans, and null stay unquoted, so their types survive.

Tidying the output for people

Keys keep the order they had in the JSON, apart from keys that are whole numbers, so put the fields a reader looks for first, such as name, image, or version, at the top of each object before converting. Comments can be added after conversion with #; they survive editing but not another trip through JSON. Indentation is two spaces throughout, and a YAML file must never be indented with tabs, so keep that setting in your editor when changing the result.

Many tools that read YAML also accept JSON directly, since JSON is valid YAML 1.2. Converting is for readability and comments, not compatibility.

How to use it

1. Paste JSON or choose a file.
2. Check the YAML.
3. Copy or download it.

Privacy & limitations

The text is converted in your browser and never uploaded, which matters when the file is a config or an export you would rather not hand to a stranger. Values are quoted where needed so the output parses back to exactly what went in.