Need a Kubernetes manifest, CI config, or docker-compose file in YAML from a JSON source — or the reverse? Convert either direction in one click, entirely in your browser.
Paste or open a JSON document, then choose YAML… from the Save menu to
export it as a .yaml file, indentation and all. Going the other way is just as direct: choose
YAML from the import-format dropdown in the Open menu to load a
.yaml/.yml file (or paste YAML text directly) and get back valid JSON.
Nested objects and lists map the way you'd expect — a JSON object becomes a YAML mapping, a JSON array becomes a YAML sequence — so config structure survives the round trip intact.
Example — this JSON:
{
"service": "billing-api",
"replicas": 3,
"env": {
"NODE_ENV": "production",
"LOG_LEVEL": "info"
},
"ports": [8080, 8443]
}
exports as this YAML:
service: billing-api
replicas: 3
env:
NODE_ENV: production
LOG_LEVEL: info
ports:
- 8080
- 8443
Open this example in the editor →
The link above pre-loads the config example above into Text mode. From there, open Save
in the toolbar and choose YAML… to export it.
No. Both directions run entirely in your browser — your document never touches a server.
Yes. Open > choose YAML from the import-format dropdown to load a
.yaml/.yml file (or pasted YAML text) and get it back as JSON.
No — JSON has no equivalent for YAML comments or anchors/aliases, so a round trip through JSON drops them. Structure and values survive; YAML-only syntax does not.
Working with newline-delimited records instead of a config file? See NDJSON Viewer.