YAML to JSON

How it works

1. Paste the YAML. The JSON appears as you type.
2. Choose how the JSON is indented, or one line if it is going straight into something else.
3. If a line cannot be read, the message says which line and why — fix it and the output comes back.
4. Copy the JSON, or download it.

Frequently asked questions

Is my YAML sent anywhere?

No. It is parsed in this page. YAML files tend to be deployment configs, and those are exactly the files not to paste into a site that posts them to a server.

Which parts of YAML does it read?

The parts configuration files are written in: mappings, lists, nesting by indentation, quoted and bare scalars, numbers, booleans and nulls, inline collections like [80, 443] and {cpu: 2}, comments, and block text in both the `|` and `>` forms with their chomping markers.

And which parts does it refuse?

Anchors and aliases (&name, *name), tags (!!binary), merge keys and complex keys, plus a file holding more than one document. Each of those changes what the file means, and a converter that dropped them would hand you valid JSON that says something different from your YAML. It stops and names the line instead.

Why did my value come out as a number?

Because YAML says it is one: 007 is the number 7, and yes is a boolean in YAML 1.1. Quote the value — '007' — to keep it as text. This is the single most common surprise when moving between the two formats.

Tabs give an error.

YAML does not allow tabs for indentation, so a file indented with them is invalid rather than unsupported here. Replace them with spaces — most editors can do it for a whole file at once.