Convert YAML to JSON or JSON to YAML instantly in your browser, covering mappings, sequences, and scalars.
Updated
/ 5 - Be the first to rate this tool Thanks for rating!
Verification failed - please try again.
Quick check
Please verify you're not a robot to submit your rating.
Give feedback
Tell us what you think about Convert between YAML and JSON online.
- Runs entirely in your browser — your data is never sent to a server
- Covers mappings, sequences, and both block and flow style
- Free, no account required
How it works
-
1
Choose YAML to JSON or JSON to YAML.
-
2
Paste your document.
-
3
Press the direction button to convert.
-
4
Copy the output.
About the YAML ↔ JSON
Kubernetes, Docker Compose, CI pipelines and OpenAPI specs are usually written in YAML, while scripts and APIs prefer JSON. This converter translates common YAML structures, nested maps, lists and scalar values, into formatted JSON, and turns JSON back into YAML with two-space indentation. It recognises numbers, booleans and null so values keep their types.
What you can do
- Convert YAML to indented JSON and JSON to YAML.
- Parse nested mappings, lists and lists of mappings written with - item syntax.
- Turn true, false, null, ~ and plain numbers into typed JSON values, and strip quotes from quoted strings.
- Read short inline lists and objects written in JSON style, such as [1, 2].
- Swap the output into the input to go the other way.
When it works best
- Checking what data a Compose file or Helm values file really contains.
- Pasting a YAML config into a JSON-only API, test or script.
- Converting a JSON response into YAML for a fixture or documentation example.
Things to know
- The conversion runs in your browser.
- This is a lightweight parser for everyday configs. Anchors and aliases, multi-line block scalars with | or >, multiple documents and tab indentation are not supported.
- Comments are dropped when converting to JSON.
- To clean up YAML indentation without converting, use the YAML Formatter. For TOML configs, use TOML ↔ JSON.
Frequently asked questions
No. Anchors, block scalars, multiple documents and tab indentation are not handled.
Yes. Numbers, true, false, null and ~ become typed JSON values.
No, they are dropped when converting to JSON.
Two spaces.