Everything runs on your machine — your file is processed right here in your browser and never uploaded to any server.
Input
YAML
Loading...
Output
JSON
Loading...

About this tool

YAML dominates the configuration world: Kubernetes manifests, docker-compose files, GitHub Actions workflows and countless CI pipelines are all written in it. But when you need to send that data to an API, inspect it with jq, or embed it in a JavaScript project, JSON is usually the required format. This tool converts between the two representations as you type, turning indented YAML documents into equivalent JSON on the right-hand side.

Because YAML and JSON share the same underlying data model, the conversion is faithful: mappings become objects, sequences become arrays, and scalars keep their types, so a replica count stays a number and an enabled flag stays a boolean. That makes it a quick way to debug a Helm values file, feed a compose definition into a script, or double-check exactly how a tricky piece of YAML indentation is actually being interpreted.

How to use

  1. Paste your YAML document into the left editor, or click Load File to open a .yml or .yaml file.
  2. The equivalent JSON is generated instantly in the right editor as you type; fix any indentation mistakes and the output updates in real time.
  3. Review the result to confirm nesting and types came through the way you expected.
  4. Click Copy to grab the JSON for another tool, or Download to save it to disk.
  5. Press Clear when you want to wipe both panes and convert a different file.

Your configuration files often contain hostnames, ports and internal service names, so this converter never sends them anywhere. Parsing happens locally in the browser process on your device, with no upload, no server-side step and no copy retained after you close the tab.

Frequently asked questions

What happens to the comments in my YAML file?

They are removed. JSON has no comment syntax at all, so there is simply nowhere to put them in the output. If the comments matter, keep your original YAML file as the source of truth and treat the JSON as a generated artifact.

Does indentation really matter when I paste YAML in?

Yes. YAML uses indentation to express structure, so a line indented at the wrong depth changes where it nests, and inconsistent spacing can make the document invalid. If the output looks wrong or fails to appear, check the indentation of the input first.

Will nested structures and lists survive the conversion?

They will. YAML mappings become JSON objects and YAML sequences become JSON arrays, at any depth of nesting. Numbers, booleans and null values are carried across as their native JSON equivalents rather than being flattened into strings.