YAML to JSON Converter
Example
Input:
name: Ali age: 30 tags: - dev - ops
Output:
{
"name": "Ali",
"age": 30,
"tags": [
"dev",
"ops"
]
}About this converter
Converting YAML to JSON is how config files get consumed by tools that only speak JSON — and how humans check what a YAML file really says, since JSON's explicit brackets settle every ambiguity of indentation. This converter implements the everyday YAML subset faithfully: block mappings and sequences by indentation, plain/single/double-quoted scalars, comments, numbers, booleans, null, and flow collections ([a, b] and {k: v}). The genuinely exotic corners — anchors/aliases, merge keys, tags and multi-document streams — are not silently faked; if your file uses them, pre-process with a full YAML tool. One classic trap it does handle: the country code NO and words like on/off, which YAML 1.1 parsers famously read as booleans.
Frequently Asked Questions
Which YAML features are not supported?
Anchors (&a) and aliases (*a), merge keys, custom tags and multi-document files. Everyday config YAML — including GitHub Actions and Kubernetes style — converts cleanly.
Why did my date become a string?
JSON has no date type, so timestamps are emitted as strings — exactly what JSON consumers expect.