How to Convert YAML to JSON

YAML and JSON describe the same kind of data — objects, arrays, and scalars — so converting between them is straightforward. The catch is YAML's whitespace sensitivity. Here's what to know.

They model the same data

Every YAML document maps to a JSON structure. This YAML:

name: DevUtilsNow
free: true
tools:
  - json
  - base64

is the same data as this JSON:

{
  "name": "DevUtilsNow",
  "free": true,
  "tools": ["json", "base64"]
}

Indentation in YAML plays the role of { } and [ ] in JSON — nesting is expressed by how far a line is indented.

Rules that matter

• Indentation is structure. Use spaces, never tabs, and keep it consistent — a single misaligned line changes the meaning or breaks the parse.
• Types are inferred. true, 42, and null become a boolean, number, and null; quote a value ("true") to keep it a string.
• Lists use - items; maps use key: value pairs.

Why convert to JSON?

Many tools and APIs accept JSON but not YAML, and JSON's explicit brackets make the structure unambiguous — handy when a YAML file isn't parsing and you want to see the actual shape. For choosing between formats, see JSON vs XML vs YAML vs CSV.

Try it

Paste YAML config and get valid JSON instantly — everything runs in your browser, nothing uploaded.