Convert JSON to YAML and YAML back to JSON — for Kubernetes, Compose, Ansible, CI configs and any tool that speaks both.
Everything runs in your browser — your data is never uploaded.
JSON and YAML describe the same data structures — objects, arrays, strings, numbers, booleans and null. The converter parses your input into memory and re-serializes it in the other format, so the result is semantically identical: same keys, same values, same nesting.
Why convert? Kubernetes and Docker Compose want YAML, but most APIs and tools emit JSON; Ansible playbooks are YAML while cloud responses are JSON. Being able to flip between them makes pasting API examples into configs (and back) painless.
Errors are reported with position information — invalid JSON shows the parser position, invalid YAML shows the line number — so a stray comma or bad indent is easy to find.
Conversion happens locally in your browser. Your data is never sent to any server and never stored.
Choose the JSON → YAML direction, paste your JSON and click Convert. You get clean 2-space YAML ready for Kubernetes, Compose or Ansible. Invalid JSON shows the exact parser error.
Switch to YAML → JSON, paste the YAML and convert. The output is standard formatted JSON — perfect for tools and APIs that expect it.
Almost. Every JSON document is valid YAML (flow style), and YAML adds block style, comments and anchors. Edge cases exist — like duplicate keys or non-string keys — but everyday config files convert perfectly.
No — JSON has no comments, so they're dropped. Converting back will not restore them. Keep the YAML as the source of truth when comments matter.
Multi-megabyte documents convert quickly since everything runs locally in your browser with no round trip.
Yes. The conversion is 100% client-side — nothing is uploaded, which matters for configs containing tokens or internal endpoints.