YAML to JSON

Read a YAML config into JSON: nested maps, sequences, block scalars, inline collections and comments, with the ambiguous parts refused rather than guessed.

Indent

24Min

YAMLyaml

JSONjson

The result appears here

Maps, sequences, quoted strings, comments, block scalars and inline collections are read. Anchors, aliases, tags and multiple documents are refused rather than half-read, because a config that comes back subtly wrong is worse than one that comes back rejected.

Questions

Which YAML does it read?+

The subset config files are written in: nested maps and sequences, quoted and plain scalars, comments, block scalars with | and >, and inline [] and {} collections. That covers a GitHub workflow, a docker-compose file and a Kubernetes manifest.

Why are anchors refused?+

Because expanding them wrong is worse than saying no. Anchors, aliases, tags, directives and multi-document files are rejected with a message instead of being half-read.

Why did my key `on:` stay a string?+

Because it should. YAML 1.1 turns on, yes and no into booleans, which is how a GitHub workflow's on: becomes true: in half the parsers out there. Keys are read as text here; values still get the booleans.

Related tools

JSON to YAMLConvert JSON into readable YAML: quotes only where they are needed, block scalars for multi-line strings, and sequences written the way people write them.JSON formatter and validatorFormat, validate, sort or minify JSON. Unquoted keys, trailing commas and comments are accepted, so a pasted console log works as well as a strict file.CSS to JS objectConvert CSS rules or a bare declaration list into JavaScript style objects, camelCased and quoted, ready for a style prop or a CSS-in-JS file.

Questions

Related tools

The tools are free. So is most of the library.