YAML JSON Workbench
Convert YAML to JSON and back without silently changing what your document said.
Up to 2 MiB, 64 levels deep. Nothing leaves your browser.
Worth knowing
- An integer in this document is larger than JavaScript can hold exactly. Its digits are written through to the JSON unchanged rather than rounded or quoted.
{
"name": "Zerdly",
"enabled": true,
"answer": "yes",
"items": [
1,
2,
3
],
"id": 9007199254740993
}What this converter will not do
- Round a large integer. 9007199254740993 is one more than JavaScript can hold exactly. Its digits are written through to the JSON unchanged — not rounded to …992, and not quoted, because the document said it was a number.
- Turn
yesinto true. Under YAML 1.2 core it is the string "yes". It was a boolean under 1.1, and a converter that still does that has changed your document. - Keep the last of a duplicate key. Three lines saying
name:is an error, not a value. - Drop documents. A multi-document stream is refused until you ask for an array, and then every document appears once.
- Invent a JSON equivalent. Custom tags, sets, binary, NaN, Infinity, non-string keys and circular aliases are refused by name rather than converted into something that means something else.
Comments and anchors cannot survive a trip through JSON. Converting back gives you the same data, not the same file.
Runs entirely in your browser. Your input is not uploaded or stored.
How to use this calculator
- Choose a direction, then paste your document. The conversion updates as you type.
- Set the indent, and say whether a multi-document YAML stream should become a JSON array.
- Copy or download the result. Any warning about what the document contained is shown above it.
How it works
YAML is read as YAML 1.2 core, which is the version almost every modern tool means. That matters most for the word yes: under YAML 1.2 it is the string "yes", and only YAML 1.1 turned it into true.
An integer too large for JavaScript to hold exactly has its digits written through to the JSON unchanged — not rounded, and not quoted, because the document said it was a number. 9007199254740993 stays itself instead of becoming …992.
A document that the parser recorded errors against is refused rather than converted. A tolerant parser will hand you a value for a broken document, and that value is a guess.
Worked example
answer: yes. Converting `answer: yes` gives {"answer":"yes"}. If you need a boolean, write `answer: true` — the converter will not decide that for you.
Common mistakes
- Expecting `yes`, `no`, `on` and `off` to become booleans (that was YAML 1.1).
- Assuming comments survive: JSON has none, so they are lost by the format, not by the tool.
- Pasting a multi-document stream and expecting one object back.
Tips
- Runs entirely in your browser. Your input is not uploaded or stored.
Frequently asked questions
Why is my big number not quoted?
Because quoting it would change its type. The digits are preserved exactly; whatever reads the JSON decides how to hold them.
Can it convert a YAML file with anchors and aliases?
Yes — they are resolved, because JSON has no way to express them. A document that refers to itself in a loop is refused rather than expanded forever.
Is anything uploaded?
Runs entirely in your browser. Your input is not uploaded or stored.
Related tools
- JSON Table Exporter
- XML Layout Workbench
- Local ZIP Workshop
- CSV to JSON Converter
- JSON Formatter & Minifier
- Base64 Encoder / Decoder
Explore more in PDF, Image, File, Data & Developer Tools.
Cite this tool
Zerdly. (2026). YAML JSON Workbench. Retrieved from https://www.zerdly.com/tools/yaml-json-workbench/
Tip: Enter any known values to calculate the remaining results.
Designed to run locally in your browser. Tool inputs are not intentionally stored by Zerdly unless stated otherwise.



