YAML ↔ JSON

Client

Convert between YAML and JSON in your tab—paste on either side, format, and copy. A small JSON catalog example is pre-filled so you can try JSON → YAML immediately.

Learn more: JSON and YAML

Translate between JSON and YAML for configs, CI files, or APIs that accept one or the other.

YAML in one sentence

YAML is often used for human-edited configuration: indentation shows nesting, and quotes are needed less often than in JSON. Under the hood many tools parse YAML into the same kinds of maps and lists JSON uses.

Which to choose

JSON is strict and ubiquitous in web APIs; YAML can be easier to read for large static config. Convert when you need to paste into a system that only accepts one format.

JSON & YAML

?

JSON → YAML uses JSON.parse then yaml.dump. YAML → JSON uses yaml.load with the default schema, then JSON.stringify.

Anchors, custom tags, or multiple documents may not round-trip exactly—validate output for production configs.

Sample JSON is pre-filled—click JSON → YAML to fill the right panel. Parsing uses js-yaml in your browser.

Common use cases

  • Turn Kubernetes-style YAML into JSON for tools that only accept JSON, or the reverse for human-edited configs.
  • Pretty-print either side after pasting minified or single-line payloads.
  • Share a readable YAML block with teammates who prefer JSON in the editor.

Common mistakes to avoid

  • Assuming every YAML feature maps 1:1 to JSON

    YAML anchors, merges, and tags may not round-trip through JSON. Validate complex files in the environment that will consume them.

FAQ

Are documents uploaded?

No. Conversion and formatting run in your browser.

More tools

Related utilities you can open in another tab—mostly client-side.