Convert YAML to JSON

Convert YAML to JSON free in your browser. No upload, no signup, no watermark. Files stay on your device.

privatepowered by js-yaml
yamljson

drop a .yaml file

or click to browse

need the opposite?

convert JSON to YAML

jsonyaml

related

more yaml & json

jsoncsv

json to csv

jsonxlsx

json to xlsx

jsonxml

json to xml

jsontoml

json to toml

see all data & code converters →

guide

how to convert yaml to json

  1. Drop your YAML file

    Drag your YAML file into the drop zone above, or click the box to pick a file from your computer or phone. The browser reads the file directly — nothing uploads.

  2. Click Convert

    The page runs js-yaml on your device to decode the YAML Ain't Markup Language and encode it as JavaScript Object Notation. Most conversions finish in a few seconds; large or codec-heavy files (RAW, video) can take longer.

  3. Download the JSON file

    When the conversion finishes, the JSON file is ready to download. Save it anywhere on your device.

FAQ

common questions

Why convert YAML to JSON?

Three common reasons: (a) feeding YAML content into a program / API that expects JSON; (b) embedding YAML configuration in a JavaScript / TypeScript codebase that imports JSON natively; (c) validating against a JSON schema (YAML schemas exist but JSON tooling is more common). YAML is the human-editable format; JSON is the machine-readable / interchange format.

Will my YAML structure be preserved exactly?

Yes — the data round-trips cleanly. Every YAML mapping becomes a JSON object, every sequence becomes a JSON array, every scalar (string, number, boolean) translates directly. YAML's anchors and aliases (`&anchor`, `*ref`) get expanded inline in the JSON since JSON has no equivalent.

What happens to my YAML comments?

They're dropped. JSON doesn't support comments — the format spec explicitly forbids them. If your YAML has important documentation in comments, that context is lost in the JSON. For configurations where comments matter, keep the YAML as the source of truth and only convert to JSON for machine consumption.

Will the JSON be significantly larger or smaller?

Slightly larger usually. YAML's indented syntax is denser than JSON's bracket/comma-heavy form for small files; for very large configurations, JSON edges out due to less whitespace. Typical configs see a 10–30% size difference in either direction depending on structure.

What about YAML's multi-document feature (--- separators)?

Multi-document YAML files (separated by `---`) typically don't translate to a single JSON value cleanly — JSON has no multi-document concept. The converter usually takes the first document; for multi-document inputs you'd need to split and convert each separately.