YAML ⇄ JSON Converter
Config format conversion in both directions.
Why convert between YAML and JSON
YAML is what humans write — Kubernetes manifests, GitHub Actions workflows, docker-compose files, CI configs. JSON is what machines exchange — REST APIs, tooling, structured logs. This converter bridges the two: paste a GitHub Actions workflow and get JSON to script against, or paste an API response and get readable YAML to hand-edit.
Conversion is fully typed: numbers stay numbers, booleans stay booleans, nested lists and objects round-trip exactly. Powered by the js-yaml library running locally in your browser — your config never leaves the page.
FAQ
Why did my "no" become false?
YAML 1.1 treats unquoted yes/no/on/off as booleans. Quote them ('no') if you need the literal string — the same rule applies to Norwegian locale issues famously found in YAML package lists.
My YAML tabs cause an error
YAML forbids tabs for indentation — spaces only. That error message is the single most common YAML complaint; replace tab characters with 2 or 4 spaces.
Which YAML version is used?
js-yaml's default schema, closest to YAML 1.2 core — the flavor used by JSON-compatible configs. Anchors (&) and aliases (*) are supported.