YAML to JSON Converter

How it works

People search YAML to JSON converter when a Compose file, Kubernetes manifest, or GitHub Actions workflow has to become an object they can feed to jq, a REST body, or a spreadsheet. Most sites upload the file. This page does the conversion in the tab.

1. Paste or drop — .yml, .yaml, or even .json (JSON is valid YAML). Nothing is uploaded.
2. Read every document — --- separators become a JSON array instead of silently dropping all but the first document. That is the usual Kubernetes / Kustomize case.
3. Pick a schema — YAML 1.2 (default) keeps unquoted yes / on / no / off as strings. YAML 1.1 turns them into booleans, which older Docker Compose and Ansible still expect. We highlight those words so you can see the difference before you copy.
4. Pretty or compact — 2-space JSON for reading, one line for a request body.
5. Copy or download — converted.json stays on your machine. The last paste and schema stay in this browser only.

This is not a YAML linter and not a Kubernetes apply tool. The product is a YAML to JSON converter that does not send infra config to a third-party server.

Close the tab and the bytes are gone.

FAQ

Why did debug: yes become "yes" instead of true?

YAML 1.2 (what most modern parsers use) treats yes as a string. YAML 1.1 treated yes / on / y as booleans. Toggle YAML 1.1 if the consumer is an older Compose or Ansible stack.

What happens to multi-document YAML?

Each --- block becomes one array item. A single document stays a single JSON value — not wrapped in [ ].

Do you upload my YAML?

No. Parse and stringify run locally. There is no account. Do not paste secrets into any converter you do not control; this one at least never leaves the tab.

Can I convert JSON back to YAML?

Not on this page. JSON is already valid YAML 1.2, so dropping a .json file still pretty-prints it. The search intent for YAML to JSON converter is one direction.