What this tool does
Paste JSON and get back YAML — the same data, in the format most CI configs, Kubernetes manifests, and Docker Compose files actually use day to day.
What changes in the conversion
- Quotes mostly disappear. JSON requires quotes around every string key and value; YAML only needs them when a value would otherwise be ambiguous (starts with a special character, looks like a number, or matches a reserved word).
- Arrays become a dashed list instead of square brackets, and nested objects become indented blocks instead of curly braces.
- A top-level array or bare scalar (just
42or"hello") converts just as validly as an object — YAML doesn't require a document to be a mapping at the top level.
FAQ
Why does a value like "yes" come back quoted?
To stop it from being misread as the boolean true by a YAML 1.1 parser (the classic yes/no/on/off ambiguity YAML Validator checks for) — the converter quotes a string whenever leaving it bare would change its meaning.
Does this preserve key order?
Yes — JSON object keys retain the order they were written in (per the JSON spec for string keys), and that order carries straight through to the YAML output.
Is my data uploaded anywhere?
No — everything happens entirely in your browser. Nothing is sent to a server.
Try it yourself
Need the reverse direction instead? YAML to JSON converts a YAML document back into JSON.