JSON to YAML Transformer
Loading tool…
Kubernetes manifests, GitHub Actions, and many configs are easier to read as YAML, while APIs speak JSON. Paste JSON and get YAML with the same structure. Anchors, custom tags, and comments are not invented for you; this is a structural conversion.
How to use the JSON to YAML Transformer
- Paste valid JSON. Format it first if you are unsure it parses. Conversion will not guess through a syntax error.
- Convert. Objects become indented maps. Arrays become lists. Strings that look like booleans or numbers should be quoted in the JSON if you need them to stay strings.
- Check the YAML in the target tool. Paste into kubectl, a workflow file, or the YAML to JSON tool to round-trip and confirm nothing you care about changed type.
When it helps
- Hand-editing a generated config. An API returned JSON, but you want a manifest you can comment and commit.
- Writing a pipeline sample. Start from a JSON fixture in a test and produce the YAML example for the docs.
Common questions
Will comments in my JSON survive?
Standard JSON has no comments. If your file has them, it will not parse until you remove them.
Why did yes become a boolean?
That happens when the input was already a JSON boolean or when a later YAML parser reads an unquoted yes. Quote strings that must stay text.
Does it support multiple documents?
One JSON value becomes one YAML document. Split multi-document files yourself.
Is the result safe to apply to a cluster?
It is only as correct as the JSON you pasted. Read the manifest before you apply it.