Convert JSON to YAML

What it does

Example

{"replicas":2,"image":{"name":"nginx","tag":"1.27"}}

replicas: 2
image:
  name: nginx
  tag: "1.27"

Highlights

• Two-space block style, the convention config tooling expects
• Key order preserved, so converted files stay diffable
• Quoting only where YAML needs it — note the version string above
• The JSON is parsed first, so bad input fails with a position
• Round-trips with the YAML to JSON converter

Frequently asked questions

Is every JSON document convertible to YAML?

Yes. YAML 1.2 is a superset of JSON, so every valid JSON document has a YAML equivalent with the same structure and values.

Why is 1.27 quoted in the output?

Because it is a string in the JSON. Unquoted, YAML would read it as a number, so the quotes are what keep the round trip lossless.

Will key order change?

No. Mappings are written in the order the JSON was parsed, which keeps converted manifests reviewable in a pull request.

Are comments added or preserved?

Neither. JSON has no comments to carry over, and none are invented. Comments you add to the YAML afterwards are lost if you convert back.

How are multi-line strings handled?

They use YAML's block form rather than being wrapped or truncated, so the value parses back exactly as it started.

Related tools

• YAML to JSONFormatted JSON out, with real errors when YAML has no equivalent.
• JSON FormatterTwo-space indentation, key order untouched, undo still works.
• JSON ValidatorLine, column and reason for the first thing a parser rejects.
• JSON DiffStructural comparison with change-to-change navigation.