Loading page content
Paste JSON and get YAML, or paste YAML and get JSON. Conversion runs both directions on every keystroke, and nested objects, arrays, and multi-line block strings survive the trip intact.
Paste JSON on the left and convert to YAML, or paste YAML on the right and convert to JSON. Handles nested objects, arrays, and multi-line strings.
The two formats overlap but do not match. YAML has anchors, comments, multi-line block scalars, and unquoted strings; JSON has none of those. Converting YAML to JSON therefore drops comments and resolves anchors, and converting JSON to YAML has to decide when a string needs quoting. This tool uses js-yaml, the same parser most Node tooling uses, so the output matches what your CI will actually read.
The usual reason to reach for this is config translation: a Kubernetes manifest you were handed as JSON, a docker-compose file you want to templatize, a GitHub Actions workflow you are porting from a generator that emits JSON. It is also the fastest way to sanity-check indentation on a YAML file that a linter is rejecting: if it converts to JSON cleanly, your indentation is fine and the problem is schema, not syntax.