Paste JSON or YAML and convert instantly in either direction — type-safe, lossless, and formatted the way config files expect. One-click copy on the result.
Paste any valid JSON — objects, arrays, strings, numbers, booleans and null are all supported.
QADIR OS agents read, rewrite and keep your JSON, YAML and env files in sync across every repo and environment — automatically, on your own machine.
Join Early AccessJSON and YAML are two ways of writing the same thing: nested data made of maps, lists and scalar values. JSON wins for APIs and data interchange because it is strict and unambiguous. YAML wins for configuration because it is easier for humans to read and edit — it uses indentation instead of braces, allows comments, and drops the quote-and-comma noise. This converter moves your data between the two without you retyping a single line, and because YAML is a superset of JSON, a round trip is lossless.
{
"service": "api",
"replicas": 3,
"ports": [80, 443],
"tls": true,
"owner": null
}
service: api replicas: 3 ports: - 80 - 443 tls: true owner: null
Both directions preserve your data types, so a number stays a number and a boolean stays a boolean — they are never silently turned into strings.
| JSON | YAML | Notes |
|---|---|---|
{ } object | indented key: value block | Two-space indent by default |
[ ] array | dash-prefixed list | - item per element |
"text" | quoted only when needed | Bare words stay unquoted for readability |
42 / 3.14 | 42 / 3.14 | Numbers kept as numbers |
true / false | true / false | Booleans preserved |
null | null | Empty values kept explicit |
Reach for YAML whenever a human has to read or edit the file by hand: Kubernetes manifests, Docker Compose files, GitHub Actions and other CI workflows, Ansible playbooks and most application config all use it. Reach for JSON when a machine is the audience — API request and response bodies, package.json, and data you store or transmit. A common workflow is to author config in YAML for readability, then convert to JSON when a tool only accepts JSON. This tool does both.
No. JSON and YAML share one data model, so structure and values survive a round trip intact. The only differences you will see are cosmetic — indentation instead of braces, fewer quotes, and no trailing commas. If you convert JSON to YAML and back to JSON, you get equivalent JSON.
Everything runs in your browser as plain JavaScript. Your JSON or YAML is never uploaded, logged or stored on any server — refresh the page and it is gone. That makes it safe to paste API keys, environment files, and confidential configuration.