YAML to JSON

Key concepts

YAML JSON conversion is for moving deploy config or part of Docker Compose into JSON for front-end or test code. This parser reads about key: value, indented nesting, and - lists. Numbers, booleans, and null become JSON types. Anchors and aliases, pipe/angle multiline, brace flow style, complex keys, and custom tags are not supported.

Spaces are safer than tab indentation. Keys at the same level must share indentation. Conversion runs only in the browser; files are not uploaded. Convert complex Helm charts or documents with many anchors in an environment that has a dedicated YAML library. This screen is for short config snippets.

Example

If input is name: tvinghub, tags: with - a - b, and ok: true, you get {"name":"tvinghub","tags":["a","b"],"ok":true}. YAML 1.1 special booleans such as ok: yes can differ from what you expect, so true/false is better. If there is no space after the colon, the parser sometimes cannot split key and value, so add one space. If keys at the same indent level are misaligned, nesting breaks and you get completely different JSON. Copy only the block you need instead of the whole deploy file to find the failure point more easily. When trying the same input several times, reset and paste again so it does not mix with the previous output. On a shared computer, clear the input when you finish so the original is not left on the monitor. Closing the browser tab also discards what you just pasted; you do not need to send a delete request to a server. Button names and field titles match the tool at the top of the screen, so you can follow along as you read. If the result is empty, first check that required fields are filled and that an error message is not hidden. This article is usage guidance and does not mean input is kept in external storage.

Related: JSON → YAML · JSON formatter · CSV → JSON