Convert JSON and YAML without hiding data loss

How to use the workspace

1. Select JSON or YAML as the source and paste the document.
2. Choose an action. Conversion requires an explicit target; minify is only available for JSON.
3. Review output notices alongside the result. A valid document is not necessarily appropriate for the system that will consume it.

A concrete starting point

{
  "service": "edge",
  "replicas": 3,
  "enabled": true
}

Try formatting with two or four spaces, then converting to YAML. Compare the resulting scalar types as well as the appearance.

Read the result carefully

Validation returns a validity result without a transformed document. Formatting and conversion report whether text changed and how comments were handled. Numeric values need special care because ordinary JavaScript numbers cannot exactly represent every JSON integer.

Common mistakes to avoid

• YAML comments have no direct JSON equivalent and may be removed during conversion.
• Unsupported or ambiguous structures should produce a clear error, not a silently rounded or coerced document.
• Syntax validation is not schema validation for your application.

Limits & privacy

1 MiB input, 2 MiB serialized output, depth 64, 50,000 nodes and bounded aliases. No document is uploaded or used as executable HTML.