Question 1

Is it possible to lose data when converting JSON to YAML?

Accepted Answer

No, assuming you are using a compliant converter. Because YAML 1.2 is a strict superset of JSON, every data type in JSON (strings, numbers, booleans, nulls, arrays, objects) has a direct, mathematically equivalent representation in YAML. The structure, hierarchy, and values will remain 100% identical. The only things "lost" are the syntactical brackets and quotes, which are structural, not informational.

Question 2

Can I convert YAML back into JSON easily?

Accepted Answer

Yes, the process is entirely reversible. A YAML to JSON converter simply parses the YAML into an Abstract Syntax Tree and emits it using JSON's rigid bracket syntax. However, be aware that if your original YAML file contained human-written comments (using the # symbol), those comments will be permanently destroyed during the conversion to JSON, as JSON has no mechanism to store them.

Question 3

Why did my converter output dashes (-) for some items and not others?

Accepted Answer

In YAML, a dash followed by a space (- ) explicitly denotes an element within an array (a list). If your original JSON contained data wrapped in square brackets [ ], the converter translates those brackets into a vertical list of dashed items. Items without dashes represent key-value pairs inside an object (dictionary), which originated from curly braces { } in your JSON.

Question 4

Why are some of my numbers enclosed in quotes after conversion?

Accepted Answer

A robust converter will automatically quote strings that look like numbers or booleans to prevent data corruption. For example, if your JSON contains the string "12345", the converter must emit "12345" in YAML. If it omitted the quotes, the YAML parser would read it as the integer 12345, fundamentally changing the data type. Quotes explicitly force the YAML parser to treat the value as text.

Question 5

Does indentation size matter in the generated YAML?

Accepted Answer

Yes, indentation is the most critical structural element in YAML. While the exact number of spaces (e.g., 2, 3, or 4) does not matter as long as it is consistent within a block, the standard convention is two spaces per level. You must never use Tab characters for indentation in YAML, as the official specification explicitly forbids them, and doing so will cause standard parsers to throw fatal errors.

Question 6

Can JSON handle everything YAML can handle?

Accepted Answer

No. While YAML can represent everything JSON can, the reverse is not true. YAML supports advanced features like relational anchors and aliases (allowing you to define a value once and reference it multiple times), custom data types, and complex keys (where an array or object acts as a dictionary key). If you use these advanced YAML features, you cannot cleanly convert that YAML back into standard JSON without resolving or losing those specific structures.

JSON to YAML Converter

Command Palette