Convert JSON to YAML
online, free & instant

Clean YAML output in three steps

No account. No upload. No nonsense.

Related JSON tools

Common questions answered

What is YAML?

YAML (YAML Ain't Markup Language) is a human-readable data serialization format widely used for configuration files. Unlike JSON, YAML uses indentation instead of braces, supports comments, and allows multi-line strings. It is the standard format for Kubernetes manifests, Docker Compose files, Ansible playbooks, and GitHub Actions workflows.

JSON and YAML are fully interconvertible: every valid JSON document has an equivalent YAML representation. This tool converts JSON to YAML 1.2, preserving all data types and structures. Objects become YAML mappings with key: value pairs, arrays become dash-prefixed sequences, and primitives map directly to their YAML equivalents.

{
  "name": "Alice",
  "roles": ["admin", "editor"],
  "settings": {
    "theme": "dark",
    "notify": true
  }
}

name: Alice
roles:
  - admin
  - editor
settings:
  theme: dark
  notify: true

Get the most out of this tool

• Use YAML for configuration files that humans edit frequently — the lack of brackets and commas reduces syntax errors.
• YAML interprets "yes" and "no" as booleans — quote strings when in doubt to prevent implicit type coercion.
• YAML supports comments (#) while JSON does not — convert to YAML when you need to annotate configuration values.

JSON to YAML conversion in depth

YAML (YAML Ain't Markup Language) is a human-friendly data serialization format that uses indentation to represent structure, similar to Python. While JSON uses curly braces and square brackets, YAML represents objects as key-value pairs separated by colons and arrays as dash-prefixed list items. YAML is a superset of JSON — every valid JSON document is also valid YAML — but YAML's native syntax is far more concise for configuration files.

The conversion from JSON to YAML is straightforward because every JSON construct has a direct YAML equivalent. JSON objects become YAML mappings: the braces are removed, each key-value pair appears on its own line with a colon separator, and nesting is expressed through increased indentation rather than brackets. JSON arrays become YAML sequences: the square brackets are removed, and each element is preceded by a hyphen and a space on its own line.

YAML offers significant advantages over JSON for human-authored configuration. YAML supports comments (# comment), multi-line string blocks (using | or > block scalars), and anchors (&anchor) with aliases (*anchor) for reusing repeated values. None of these features exist in JSON. For configuration files like CI/CD pipelines (GitHub Actions, GitLab CI), Kubernetes manifests, and Docker Compose files, YAML is the standard choice precisely because of these capabilities.

String quoting in YAML is optional for simple values. A YAML string like name: Alice does not need quotes around Alice. However, strings that look like other YAML types — booleans (true, false, yes, no, on, off), numbers, null, or strings containing special characters — must be quoted. The converter handles this automatically, adding quotes only where necessary to prevent ambiguity.

YAML has a common gotcha: boolean coercion. In YAML 1.1 (used by older parsers like PyYAML by default), the strings "yes", "no", "on", and "off" are parsed as booleans. This frequently causes bugs in Kubernetes labels, Ansible variables, and CI configuration where the letter "no" or a country code like "NO" (Norway) is unintentionally treated as false. YAML 1.2 eliminated this ambiguity, and the converter follows the safer YAML 1.2 conventions.

Kubernetes and Helm chart development is one of the most common contexts where JSON-to-YAML conversion is needed. Kubernetes API objects are defined in JSON internally but almost universally written as YAML. Helm charts use YAML templates. When a tool generates JSON output (like kubectl get pod -o json), converting it to YAML makes editing and storing the configuration much more practical.

When developers use this tool

Additional frequently asked questions