Frequently asked questions
Is the YAML an exact equivalent of my JSON?
Yes. YAML can express everything JSON can, and the converter writes it so that reading the YAML back gives the same data: the same types, the same order of keys and the same numbers.
Why are some text values wrapped in quotes?
YAML guesses types from unquoted text, so the text value "true", "null", "123", "2024-01-01" or "no" would be read as a boolean, null, number or date. The converter quotes any text that would otherwise change meaning, along with text that has special characters, leading or trailing spaces or line breaks. Ordinary text is left unquoted for readability.
How are multi-line texts handled?
Text containing line breaks is written as a single quoted line with \n escapes. That is always correct and survives any YAML parser, but if you want a readable block, you can edit it by hand into YAML's | block style after converting.
Which YAML version does it produce?
Block-style YAML that both YAML 1.1 and 1.2 readers understand. Numbers with exponents are written in a form older parsers also accept, for example 1e5 becomes 1.0e+5.
Can I convert YAML back to JSON?
Not here yet. This page converts from JSON to YAML only.
Is my JSON uploaded or stored?
No. Everything runs inside your browser, so your data never leaves your device. Our server only records that one operation was converted, along with your network address, so the daily limit shown above the tool can be applied.





