Advertisement
Paste JSON and click To YAML to get clean, readable YAML with 2-space indentation, or paste YAML and click To JSON to parse it into formatted JSON. The editor auto-detects which language you pasted, validates it as you type, and points at the exact line when something is wrong. Everything runs locally in your browser.
No. Conversion happens entirely in your browser with JavaScript — your configs, manifests, and pipelines are never sent to a server, so the tool works offline and is safe for sensitive files.
Mappings and sequences (block and flow style), comments, quoted and plain scalars with YAML 1.2 typing, a leading document marker, and | / > block scalars for multiline text. Anchors, aliases, custom tags, merge keys, and multi-document streams are not supported — the parser reports a clear error instead of silently guessing.
No — the parser follows modern YAML 1.2 typing, so only true/false are booleans and yes/no/on/off stay strings. Unquoted numbers like 1.0 become JSON numbers; quote them ("1.0") to keep them as strings — exactly as YAML defines it.
A JSON string containing line breaks becomes a YAML literal block scalar (|), which keeps every line break exactly and stays human-readable. Going the other way, both literal (|) and folded (>) blocks parse back into ordinary JSON strings.
Yes — that is the design goal. The generated YAML quotes anything ambiguous (like "true", "1.0", or text with a #), so converting JSON to YAML and back returns exactly the same JSON, keys, types, and all.