JSON ↔ YAML

Convert JSON to YAML format and YAML back to JSON

What is it and how does it work?

This tool converts between JSON and YAML in both directions — JSON to YAML and YAML back to JSON. They describe the same kind of data (objects, arrays, strings, numbers, booleans), but serve different audiences: JSON is the compact, bracket-heavy format that APIs and programs exchange, while YAML is the indentation-based format designed for humans to read and edit, which is why configuration files for tools like Docker, Kubernetes, GitHub Actions and CI pipelines are written in it. Converting lets you move data between an API world and a config world without rewriting it by hand.

The conversion is structural: nested objects become indented blocks, arrays become dash-prefixed lists, and the values carry across unchanged. Going from JSON to YAML usually makes a dense payload far easier to read and lets you add comments; going from YAML to JSON produces the strict, quoted form a program or API expects. Because YAML relies on indentation to express structure, the converter handles that mapping precisely so you do not have to count spaces. Everything runs in your browser, keeping your config and data private.

Common use cases

• Writing config from an API sample: convert a JSON example into YAML to drop into a Kubernetes, Docker Compose or CI configuration file.
• Feeding YAML to a program: convert a hand-written YAML config to JSON for a tool or endpoint that only accepts JSON.
• Making data readable: turn a dense JSON object into indented YAML to review its structure or annotate it with comments.

Frequently asked questions

When should I use YAML instead of JSON?

YAML is better when humans write and read the file directly — configuration, pipelines, infrastructure definitions — because it is less noisy and supports comments. JSON is better for data exchanged between programs, where strictness and universal parser support matter more than readability.

Does YAML support everything JSON does?

Yes — YAML is a superset of JSON, so any JSON document is also valid YAML and converts cleanly. The reverse is not always true: YAML has features (comments, anchors, multiple documents) that have no JSON equivalent and are dropped or expanded when converting to JSON.

Why is YAML so sensitive to indentation?

YAML uses indentation instead of brackets to express nesting, so the number of leading spaces defines structure. Mixing tabs and spaces or misaligning a line changes the meaning. The converter produces consistent indentation, which avoids the most common YAML mistakes.

Are comments preserved when converting?

Converting YAML to JSON drops comments, because JSON has no comment syntax. Converting JSON to YAML cannot invent comments, but it gives you a clean structure to add them to afterwards.

JSON

JSON Formatter · JSON Minifier · JSON Validator · JSON to CSV · JSON Flatten · JSON Compare