How to Convert YAML to JSON
YAML is loved for configuration because it's clean and easy to read, but plenty of tools and APIs still want JSON. This converter parses your YAML properly — following indentation to build nested maps and sequences, understanding both block and inline flow style, and recognising real types so numbers, booleans and null come through correctly rather than as strings. Comments are stripped, quoted strings are unquoted, and if something's malformed you get a clear message instead of silent, broken output. Choose pretty or minified JSON, then copy or download. Everything runs in your browser, so nothing is uploaded.
Paste your YAML
Paste your config or load the sample; it's parsed locally with nothing uploaded.
Pick the format
Choose pretty printing for readability or minified for compact output.
Copy or download
Grab the JSON with one tap or save it as a .json file.
YAML vs JSON — What's the Difference?
YAML — YAML Ain't Markup Language
A whitespace-driven format designed to be effortless for humans to read and write. Structure comes from indentation rather than brackets, it supports comments, and it's the default for configuration in tools like Docker Compose, Kubernetes, GitHub Actions and Ansible. The flip side is that indentation matters, so a stray space can change meaning.
JSON — JavaScript Object Notation
A strict, bracket-based format that machines parse quickly and unambiguously. It has no comments and is more verbose than YAML, but its rigidity makes it ideal for data interchange and APIs. Converting YAML to JSON gives you a portable, tooling-friendly version of the same data.
Common Use Cases
Feed JSON-only tools
Convert a YAML config into JSON for a tool or API that doesn't accept YAML.
Inspect config data
Turn a Docker Compose or Kubernetes file into JSON to see its exact structure.
Programmatic access
Get JSON you can load directly in code without adding a YAML parser dependency.
Validate structure
Converting to JSON quickly reveals indentation mistakes in your YAML.
Migrate settings
Move YAML settings into systems and stores that expect JSON.
API payloads
Author a request body in readable YAML, then convert it to JSON to send.
CI/CD pipelines
Transform pipeline YAML into JSON for tooling that consumes JSON definitions.
Quick exploration
A fast, no-install way to see the data behind a YAML file.
Tips & Best Practices
Use consistent indentation
Stick to spaces, not tabs, and keep the same indent width throughout — YAML derives structure from it.
Quote ambiguous strings
Wrap values like yes, no, or on in quotes if you want them to stay strings rather than becoming booleans.
Mind leading zeros
Values like 007 are read as numbers and lose the zeros; quote them to keep them as strings.
Keep keys simple
Plain keys convert most cleanly; quote any key that contains a colon or special characters.
Minify for machines
Use minified output when the JSON feeds another program and pretty printing when a person reads it.
Troubleshooting
The structure looks wrong
Almost always an indentation issue. Make sure nested items are indented consistently with spaces, and that list items line up under their key.
A value became true or a number unexpectedly
YAML treats yes, true and bare digits as booleans and numbers. Quote the value if you need it to remain a string.
It reports a parse error
Check for tabs used as indentation, an unclosed quote, or a stray colon inside an unquoted value; quoting the value usually fixes it.
Comments appeared in output
Comments after a # are removed, but a # inside an unquoted value can confuse this — wrap such values in quotes.
Frequently Asked Questions
How do I convert YAML to JSON for free?
Paste your YAML above and clean JSON appears instantly. Copy it or download a .json file — free, no signup.
Does it handle nested maps and lists?
Yes. Indented mappings and sequences are parsed into correctly nested JSON objects and arrays to any depth.
Does it support flow style?
Yes. Inline flow collections like [a, b] and { x: 1 } are understood alongside standard block style.
Are numbers and booleans preserved?
Yes. Values like 42 and true are converted into real JSON numbers and booleans rather than strings.
What about comments?
Full-line and inline comments after a # are stripped, so they never appear in the JSON output.
How are quoted strings handled?
Both single and double-quoted scalars are unquoted correctly, including escaped characters in double quotes.
Can I keep a value as a string?
Yes — wrap it in quotes in your YAML. This is useful for things like postcodes, version numbers or values that look like booleans.
Can I minify the JSON?
Yes. Turn off pretty printing for compact, minified JSON that's ideal for sending over a network.
What if my YAML is invalid?
You'll get a clear message instead of broken output. The usual culprits are inconsistent indentation or an unclosed quote.
Is my data sent to a server?
No. Everything happens inside your browser, so your data never leaves your device — safe even for sensitive config.
Can I download the result?
Yes. Save the output as a .json file, or copy it straight to your clipboard.
Does it handle multiple documents?
Document separators are recognised; the primary document is converted, which covers the common single-document case.
Does indentation size matter?
Consistency matters more than the exact width. Use the same number of spaces for each level throughout the file.
Will tabs work for indentation?
YAML doesn't allow tabs for indentation. Use spaces — the tool normalises them, but genuine tab-indented YAML should be fixed at the source.
Does it work on phones?
Yes, in any modern browser on Windows, Mac, Android or iPhone with nothing to install.
Is this converter really free?
Completely free, forever — no account, no ads and no premium wall.
100% free · No signup · Processed in your browser · Data never sent
Last updated: August 2026 · FlipMyFormat YAML to JSON Converter
Written and maintained by the FlipMyFormat team · Runs entirely in your browser