Input (YAML)
name: Ada
active: true
roles:
- admin
- userYAML → JSON parses human-friendly YAML and outputs the equivalent JSON. Mappings become objects, sequences become arrays, and scalars become strings, numbers, booleans, or null. Because every JSON document is itself valid YAML, the two formats share a common data model, making this handy for feeding config files written in YAML into tools and APIs that expect JSON.
YAML (YAML Ain't Markup Language) is an indentation-based data serialization format prized for readability in configuration and CI pipelines. JSON (JavaScript Object Notation) is a stricter, brace-and-bracket format that's the lingua franca of web APIs. This converter resolves YAML's indentation, anchors, and scalar types into explicit JSON structure, so you can move from authoring convenience to machine-friendly interchange.
The main file is the entry point for each run.
Use the Input panel to pipe standard input to your program when it needs data.
Run sends your code to a fresh hosted runtime and streams the result into the output panel.
Your draft stays in this browser, and Share creates a separate snapshot link.
name: Ada
active: true
roles:
- admin
- user{
"name": "Ada",
"active": true,
"roles": ["admin", "user"]
}server:
host: localhost
port: 8080{
"server": {
"host": "localhost",
"port": 8080
}
}count: 42
ratio: 3.14
label: "01234"
note: null{
"count": 42,
"ratio": 3.14,
"label": "01234",
"note": null
}users:
- id: 1
name: Ada
- id: 2
name: Linus{
"users": [
{ "id": 1, "name": "Ada" },
{ "id": 2, "name": "Linus" }
]
}message: |
line one
line two
title: Demo{
"message": "line one\nline two\n",
"title": "Demo"
}point: { x: 1, y: 2 }
tags: [red, green, blue]{
"point": { "x": 1, "y": 2 },
"tags": ["red", "green", "blue"]
}defaults: &defaults
retries: 3
timeout: 30
prod:
<<: *defaults
timeout: 60{
"defaults": {
"retries": 3,
"timeout": 30
},
"prod": {
"retries": 3,
"timeout": 60
}
}The editor uses Monaco, the engine behind VS Code, with language-aware editing tools and familiar keyboard controls.
Paste indentation-based YAML on the left; the tool parses it into a data model.
Mappings emit as JSON objects, sequences as arrays.
Scalars resolve to JSON strings, numbers, booleans, or null.
Anchors and aliases are dereferenced into expanded JSON values.
Block and flow styles both parse to the same structure.
Implicit typing (e.g. true, 42, null) is resolved, not left as text.
YAML is parsed locally in your browser; nothing is uploaded.
Safe for config files that contain tokens or secrets.
Every JSON doc is valid YAML, so you can round-trip JSON back through it.
Use it to feed YAML configs into JSON-only APIs and tooling.
Output
JSON output