Loading…
Convert YAML into JSON with a standards-compliant parser — mappings, sequences, multiline strings, and multiple documents, all in your browser.
Your JSON will appear here after you convert.
Configuration is often written in YAML, but tools and APIs frequently expect JSON. This converter parses YAML with a standards-compliant parser and emits clean JSON.
name: John
age: 30
active: true
roles:
- admin
- editor{
"name": "John",
"age": 30,
"active": true,
"roles": ["admin", "editor"]
}[a, b]) is also supported.| and >) become multiline strings.YAML scalars are typed: true/false become booleans, numbers become numbers, and null/~ become null (YAML 1.2 core schema). Multiple documents separated by --- become a JSON array. Custom tags are not applied — values always stay data. Convert back with JSON to YAML.
Mappings, sequences, scalars, quoted and multiline strings, comments, and anchors/aliases (resolved to plain data) are all supported, using a standards-compliant YAML parser.
A single document produces its value directly. Multiple documents separated by --- produce a JSON array, one entry per document, and the document count is reported. No document is silently discarded.
Yes. YAML has native scalar types, so true/false become booleans, numbers become numbers, and null (or ~) becomes null, following the YAML 1.2 core schema.
Yes. It uses the parser's safe defaults: values are always plain data, with no code execution, no unsafe JavaScript tags, and no file or network access. Parsed data is only serialized to JSON and never merged into application objects.
You get a clear error message with the line and column of the problem, rather than a misleading partial result.