Loading tool…
ToolWrenConvert YAML configuration into JSON, or turn JSON back into clean YAML. Handy for editing config files, Kubernetes manifests and CI pipelines.
Loading tool…
YAML ⇄ JSON is a free, private online tool that lets you convert YAML to JSON or JSON to YAML in your browser. It runs entirely in your browser, so nothing you enter is uploaded to a server.
Privacy: this tool runs entirely in your browser. Your input is never sent to, received by, or stored on any server — there are no uploads and no tracking of what you enter.
YAML and JSON describe the same data model — maps, lists and scalar values — but YAML is indentation-based and friendlier for humans, while JSON is ubiquitous in APIs and tooling. Converting between them is a constant need in DevOps.
It handles nested maps, lists, and scalar types (strings, numbers, booleans and null). Paste YAML to get formatted JSON, or paste JSON to get readable YAML.
Keep YAML indentation consistent (two spaces is standard). For complex anchors, multi-document streams or advanced tags, use a full YAML library — this tool targets everyday config files.
YAML ('YAML Ain't Markup Language') is a human-friendly data-serialisation format built around indentation rather than brackets. It expresses the same data model as JSON — maps, lists and scalars — but reads more like an outline, which is why it became the standard for configuration in tools like Docker Compose, Kubernetes, GitHub Actions and Ansible. This converter moves data between YAML and JSON in both directions.
JSON is strict and ubiquitous; YAML is concise and comment-friendly. JSON requires quotes and braces everywhere, while YAML uses indentation and infers types, so it is pleasant to edit by hand. The flip side is that YAML's flexibility can surprise you — which is exactly why a converter helps: author config in readable YAML, then convert to JSON for an API or a strict parser, or convert an API's JSON into YAML to drop into a config file.
Converting YAML to JSON, the tool parses indentation levels into nested maps and lists, recognises list items (-) and key/value pairs, and infers scalar types — numbers, booleans, null and strings. Converting JSON to YAML, it walks the structure and emits properly indented keys, list items and quoted strings where needed. The result round-trips for the common shapes you meet in real configuration files.
YAML's automatic type inference is powerful but occasionally treacherous. The classic example: the country code NO can be read as the boolean false, and a value like 1.10 may lose its trailing zero. Times and dates can also be coerced unexpectedly. When precision matters, quote the value to force it to stay a string — and use a converter like this to see exactly how your YAML is being interpreted.
Reach for this whenever you edit Kubernetes manifests, CI/CD pipelines, or Docker Compose files and need to check the equivalent JSON, or when an API hands you JSON that you want to drop into a YAML config. Seeing both representations side by side also makes YAML's indentation rules click. As always, conversion is entirely client-side, so even config that embeds secrets stays on your machine.