Question 1

Will a JSON array of objects turn into a multi-document YAML file (separated by ---)?

Accepted Answer

No — a JSON array always becomes a single YAML sequence (a list under one document), never multiple --- separated documents. Multi-document YAML has no equivalent concept in JSON, so this conversion only ever produces one document; the reverse direction (YAML to JSON) does handle multi-document YAML input, converting it into a JSON array, but that is intentionally a one-way capability.

Question 2

How are null, empty arrays, and empty objects written in the output?

Accepted Answer

As null, [], and {} respectively — null stays the literal word null, and empty arrays/objects use YAML's compact flow style ([] and {}) rather than being expanded across multiple lines, since there is nothing to indent.

Question 3

Why do I get a line and column number in the error instead of just 'invalid JSON'?

Accepted Answer

Because the error is caught at the JSON-parsing step, before YAML conversion even starts, and this tool reuses the same precise error-location logic as the JSON tools — locating the exact character the parser failed on rather than reporting a generic message.

Question 4

Does the output preserve the exact number formatting from my JSON (like 2.0 vs 2)?

Accepted Answer

No — JSON is parsed into JavaScript numbers first, which don't distinguish 2 from 2.0, so both convert to the same YAML number. If you need to preserve trailing zeros or specific numeric formatting, that information is lost the moment the JSON is parsed, before conversion even begins.

JSON to YAML

Clean, Indented Output

Handles Large Documents

Local Processing

Frequently Asked Questions