JSON ↔ YAML

Kubernetes and Docker Compose usually speak YAML; apps and frontends usually speak JSON. Convert so you don't copy fields twice.

Paste a JSON object, click JSON → YAML, and nesting plus arrays are kept. YAML → JSON sends a manifest to tools that only accept JSON.

Common structures are covered. Anchors, complex tags, and rare YAML syntax deserve a human look at key fields.

Conversion stays local. Config that contains secrets or internal hosts does not need to be redacted first.

Why you shouldn't bounce YAML and JSON too many times

Comments, key order, and multiline string writing are easy to lose. When comments matter, treat the YAML in the repo as source and JSON as an intermediate.

Use it with Diff

When two Compose or values.yaml files are hard to compare, convert both to JSON, then use Diff for paths and values. That is steadier than scanning indent by eye.

How to use it

Paste JSON or YAML. Confirm you did not glue two documents together.
Choose JSON → YAML or YAML → JSON.
Scan images, ports, and environment variables.
Copy into the config repo, or send it to Format / Diff.
Split multi-document YAML (several ---) first, then convert each.

When to use it

Move app JSON config into Helm / Compose YAML.
Turn a K8s manifest into JSON for a deploy script that only accepts JSON.
Unify two environments as JSON before you compare configs.
Copy a YAML sample from docs and turn it into JSON for API debugging.

Keep in mind

Comments cannot be kept on the way to JSON.
true / on / yes may become booleans in YAML. Check string fields after convert.
Large manifests convert, but the browser uses memory. Production pipelines still belong on a CLI.

FAQ

Are comments kept?

Comments cannot be kept on the way to JSON. YAML output follows structure — don't expect original comments to survive.

Is multi-document YAML supported?

It follows common single-document handling. Split documents separated by --- first.

How do I use this with Format?

Convert to JSON first, then Format or Diff two environments' configs.

Is the config uploaded?

No. Everything stays in the browser.

Can anchors and aliases convert?

Complex anchor / alias may expand or drop. Check referenced sections after convert.

What if indent is wrong?

YAML is indent-sensitive. If parse fails, check mixed spaces and tabs.

When should I use TOML convert instead?

Use YAML for K8s / Compose. Use TOML for Cargo and some toolchains.

Can a JSON array root convert?

Yes. Some YAML documents start with a list and stay an array on the way back to JSON.