How to Convert JSON to YAML

Same data, different punctuation

JSON and YAML both represent objects, arrays, strings, numbers, booleans, and null. The difference is how they mark structure. JSON uses braces, brackets, and commas. YAML uses indentation and dashes.

{
  "service": "api",
  "port": 8080,
  "tags": ["web", "public"],
  "tls": { "enabled": true }
}

The same data in YAML:

service: api
port: 8080
tags:
  - web
  - public
tls:
  enabled: true

Notice that YAML dropped the quotes around keys and simple strings, replaced the array with a dash list, and used indentation instead of braces for the nested object.

Why teams reach for YAML

YAML is common in configuration because it is easy to scan and to edit by hand. Docker Compose, Kubernetes manifests, and many CI pipelines use it. The indentation makes nesting visible without counting brackets, and the reduced punctuation means less noise per line.

JSON is stricter and less forgiving to write by hand, which is exactly why it is a better wire format. So a common pattern is to convert JSON to YAML when a human is going to maintain the file, and keep JSON for data that machines exchange.

Every JSON document is valid YAML

One useful fact: YAML is a superset of JSON. That means valid JSON is already valid YAML, and a YAML parser will accept it. Converting to YAML is really about rewriting it in the cleaner indented style rather than making it parseable. The reverse is not true. Plenty of valid YAML uses features that have no JSON equivalent, such as comments and anchors.

Convert it

1. Paste or import your JSON into the converter and choose YAML.
2. Read through the output. Well-formed JSON produces clean YAML with no surprises.
3. Copy or download the result for your config file or docs.

Details to check after converting

• Strings that look like other types: a value like "true" or "12345" as a string may need quotes in YAML so it is not read as a boolean or number. A careful converter quotes these for you.
• Empty values: JSON null becomes null or an empty value in YAML. Confirm it reads the way your parser expects.
• Special characters: strings with colons or leading symbols sometimes need quoting in YAML to stay unambiguous.

If you need to go the other direction later, remember that any comments or anchors you add to the YAML will not survive a round trip back to JSON, since JSON cannot express them.