Convert YAML configuration into JSON — anchors, block scalars and deep nesting included — entirely inside your browser.
YAML and JSON describe the same shapes — maps, lists, scalars — so conversion is mechanical rather than lossy. YAML is written by humans (comments, no braces, readable indentation); JSON is consumed by machines (unambiguous, universally parsed).
YAML has features JSON lacks: comments, anchors and aliases for reuse, multiple documents in one file, and typed timestamps. Comments disappear in conversion, aliases are expanded into their full value, and only the first document is converted. Dates become strings, since JSON has no date type.
YAML 1.1 famously parsed NO as the boolean false, breaking country-code lists. YAML 1.2 fixed this, and the parser here follows 1.2 — but if your file was written for an older tool, quote ambiguous scalars to be safe.
Going the other direction? Use JSON to YAML. For tabular data, see CSV to JSON.
Yes. Parsing uses a full YAML 1.2 implementation, so anchors (&name), aliases (*name) and block scalars (| and >) all behave as expected. One exception: a multi-document file — several documents separated by --- in one stream — is rejected, because JSON has no way to represent a stream of documents. Convert each document separately.
No. Parsing happens in your browser — which matters, because YAML files are exactly where API keys, database passwords and deployment secrets tend to live.
Almost always indentation: YAML forbids tabs for indentation, and mixed spacing breaks nesting silently. The error message reports the offending line.
JSON has no comment syntax, so YAML comments are dropped. Keep the YAML as your source of truth if the comments matter.
Aliases are expanded into ordinary JSON values rather than preserved as references. YAML timestamps become strings because JSON has no dedicated date type.