YAML to JSON

Nothing you paste here leaves your browser. There is no server to send it to — the conversion happens on your own device, and nothing is uploaded, stored or seen by anyone. Paste it, or drop a file on the page.

What this conversion costs you

YAML can hold things JSON cannot, and they have to go somewhere. Comments disappear, because JSON has nowhere to put them. Dates become strings. Anchors and aliases are expanded, so a value referenced in five places appears five times — the document means the same thing and is no longer written the same way.

How it works, and why nothing is uploaded

YAML is read by js-yaml, which is twelve kilobytes of MIT-licensed code served from this site. It is the one format here that is not handled by code written for this site, and deliberately so: YAML is full of traps, and a partial parser would not fail, it would quietly give you the wrong data. Writing JSON is built in too.

Everything happens in the page you are looking at. There is nothing to upload, no queue, no size limit but your own memory, and nothing that could be read by anybody — because it is never sent.

Where to go next

• JSON to YAML — the same conversion the other way
• YAML to CSV — the shape every spreadsheet opens
• YAML to XML — the shape older systems expect

What this does not do

It converts one document at a time and does not validate against a schema, transform with XSLT, or query with JSONPath. It will tell you when your input does not parse, and where, rather than producing something that looks converted.

Nothing is uploaded, so it cannot work on a file that is not on the device you are using, and it does not remember what you converted a moment ago. Close the tab and it is gone.