Processed locally
About this tool
JSON and YAML describe the same data structures: maps, lists and scalars. YAML trades brackets for indentation, which makes it the default for configuration files, while JSON dominates APIs.
Use it to move payloads into Kubernetes manifests, CI configs or docker-compose files — and back.
YAML comments can't be represented in JSON and are dropped when converting to JSON.
Frequently asked questions
Is every JSON valid YAML?
Yes — JSON is a subset of YAML 1.2, so any JSON document is already valid YAML. The reverse is not true.
What happens to comments?
JSON has no comment syntax, so YAML comments are dropped when converting YAML → JSON.
Which YAML version is used?
YAML 1.2 — plain scalars like 'on' or 'no' are kept as strings, avoiding the classic Norway problem.