JSON ⇄ YAML Converter
Convert configuration between JSON and YAML in either direction — nested maps, lists, and lists of maps all supported.
Frequently asked questions
Which YAML features are supported?
The structures that make up real config files: nested maps, lists, lists of maps (- name: web), quoted and plain strings, numbers, booleans, null, and comments. Advanced YAML (anchors &/*, multi-line | and > blocks, custom tags) isn't parsed — for those, the YAML is more expressive than JSON can represent anyway.
Why do quotes appear around some YAML strings?
Strings that YAML would otherwise misread get quoted automatically: things that look like numbers or booleans ("true", "007"), and strings with special characters. Everything else stays clean and unquoted.
Why convert between them?
Tooling: Kubernetes, CI pipelines and docker-compose speak YAML; APIs and JavaScript speak JSON. Converting lets you lint, diff, or template one format with tools built for the other.
Last updated: 2026-07-13