YAML to JSON Converter
Paste a YAML document and get formatted JSON back. Parse errors come with the line and column, so a broken config is quick to find.
YAML
JSON
About this tool
YAML is what people write and JSON is what programs read, so the conversion happens constantly — pulling a Kubernetes manifest into a script, feeding a CI config to a tool that only speaks JSON, checking what a Docker Compose file actually resolves to. The parse is strict: anchors are expanded, YAML 1.1 booleans like yes and no become true and false, and comments are dropped, because none of them survive in JSON.
How to use it
- 1Paste your YAML into the input panel — a config file, a manifest, anything valid.
- 2The JSON appears immediately, indented and highlighted.
- 3Press Copy to take it. Converting the other way is one click away in JSON to YAML.
Frequently asked questions
›Is every YAML file convertible to JSON?
Almost. YAML is a superset of JSON, so the common cases map directly. What has no JSON equivalent: anchors and aliases (they get expanded), multiple documents in one file separated by ---, dates and other typed scalars, and non-string keys.
›Why did my YAML fail with an indentation error?
YAML forbids tabs for indentation — only spaces. A single tab character anywhere in the indentation makes the whole document invalid, and editors often insert them invisibly.
›Why did "yes" become true?
YAML 1.1 treats yes, no, on and off as booleans. If you meant the string, quote it: "yes". The same applies to version numbers, where 1.20 becomes the number 1.2.
›Are comments preserved?
No. JSON has no comment syntax, so anything after a # is dropped during conversion. Keep the YAML file as the source of truth if the comments matter.
›Does this send my config to a server?
No. Parsing happens in your browser, which matters here — YAML files tend to be deployment configs with hostnames and secrets in them.