JSON to YAML converter.
Paste JSON on the left, get YAML on the right. Free, instant, and private — the conversion runs entirely in your browser, so nothing is uploaded anywhere.
Converting something big? Browser tools hold everything in tab memory. The jsonbolt desktop app parses JSON at 3 GB/s and exports YAML from files this page couldn't even open — see the two-keystroke workflow ↓
Going the other way? YAML to JSON converter →
Convert JSON to YAML faster without the browser
If you convert JSON more than once a week, the copy–find-a-tab–paste loop is the slow part. The jsonbolt desktop app removes it: a global hotkey opens whatever JSON is on your clipboard, and YAML export is two clicks away. It parses files at 3 GB/s, so this works on multi-gigabyte documents that would kill a browser tab.
Copy JSON anywhere
A terminal, an API client, a log file, a browser tab — if it's on your clipboard, it's ready.
Press Win + J⌃ ⌥ J
jsonbolt launches and opens your clipboard in one step — even a 1 GB payload renders instantly. (Opt-in: Settings → Launch.)
Export as YAML
File → Export Selection Value As → YAML writes a file; Copy Selection Value As puts it straight back on the clipboard. Select any subtree to convert just that branch.
Free for personal use — no signup. YAML, CSV, and XML export are built in.
JSON vs YAML: what actually changes
YAML 1.2 is a superset of JSON — every valid JSON document is already valid YAML. Converting doesn't change your data at all; it re-serializes the same objects, arrays, and scalars into a syntax built for human eyes: indentation instead of braces, quotes only where needed, and support for comments.
| JSON | YAML | |
|---|---|---|
| Comments | Not supported | # like this |
| Structure | Braces, brackets, quoted keys | Indentation |
| Multi-line strings | \n escape sequences | Block scalars (|) |
| Trailing commas | Syntax error | No commas to trail |
| Typical home | APIs, machine-to-machine data | Kubernetes, GitHub Actions, docker-compose, OpenAPI, app config |
When to use which: if the file lives in a repo and humans edit it by hand, YAML earns its keep — comments alone justify it in config. If a service emits or consumes it, stay with JSON: stricter grammar, universal parsers, no indentation ambiguity.
How this converter handles the details
- Two-space indentation, keys kept in their original order.
- Strings are quoted only when YAML would misread them. Values like
"yes","no","1.25", or"null"stay quoted so they remain strings when parsed back — the classic "Norway problem", where an unquotedNOturns intofalse. - Multi-line strings become block scalars (
|), so embedded text stays readable instead of collapsing into\nsoup. - Empty containers come out as
{}and[]. - Numbers, booleans, and null pass through unchanged.
- Everything runs locally. The converter is ~2 KB of JavaScript on this page; your data never leaves the tab.
FAQ
How do I convert JSON to YAML?
Paste your JSON into the input pane at the top of this page. The YAML equivalent appears instantly in the output pane — copy it to your clipboard or download it as a .yaml file. The conversion runs locally in your browser.
Is my JSON uploaded to a server?
No. This converter is a small script that runs entirely in your browser. Your data never leaves your machine, so it's safe to convert payloads that contain API keys, tokens, or internal data.
What is the difference between YAML and JSON?
They represent the same data structures — objects, arrays, strings, numbers, booleans, null. JSON uses braces, brackets, and quotes; YAML uses indentation, supports comments, and has readable multi-line strings. YAML 1.2 is a superset of JSON, so every valid JSON document is already valid YAML.
When should I use YAML instead of JSON?
Use YAML for files humans read and edit — Kubernetes manifests, CI pipelines, docker-compose, application config. Keep JSON for data that programs exchange, like API requests and responses. A good rule: if it lives in a git repo and people edit it by hand, YAML; if a service emits or consumes it, JSON.
Are .yml and .yaml the same?
Yes — same format, two file extensions. The YAML project recommends .yaml; .yml survives from tools that required three-letter extensions. Kubernetes, GitHub Actions, and docker-compose accept both.
How do I convert a very large JSON file to YAML?
Browser converters — this one included — hold the whole document in the tab's memory, which gets painful past a few hundred megabytes. The jsonbolt desktop app parses the file at 3 GB/s: open the file (or press Win + J⌃ ⌥ J to open clipboard JSON), select the root or any subtree, then File → Export Selection Value As → YAML.