JSON ↔ YAML Converter
Move between config file formats
Input
Options
Result
Nothing entered yet
Paste JSON or YAML and the converted result appears here.
JSON has no comments, so any YAML comments are lost in the conversion.
Kubernetes, GitHub Actions and Docker Compose want YAML; APIs and package files speak JSON. The two describe the same data, so converting is mostly mechanical — with one thing to watch, noted below.
How to use
- 1 Choose the direction.
- 2 Paste your JSON or YAML.
- 3 Set the indentation for YAML output.
- 4 Copy the result.
Frequently asked questions
What gets lost converting YAML to JSON?
Comments, anchors and aliases, and multi-document files. Comments are the painful one — a heavily annotated config loses all its explanation, so keep the YAML as the source of truth.
Why does YAML indentation matter so much?
Indentation is the structure, the way it is in Python. Two spaces versus four is a style choice, but mixing them or using tabs makes the file invalid — YAML forbids tabs for indentation entirely.
Why did my value change type?
YAML infers types, so unquoted yes, no, on and off become booleans, and 1.0 becomes a number. Version strings and country codes are the usual casualties — quote them to keep them as strings.