Export JSON to CSV with explicit spreadsheet safety

Use a non-empty array of objects and review how nested values and formulas are represented.

Start with rows, not an arbitrary document

The converter accepts a non-empty array of objects. Each object is one row. A single object, scalar array or null row is rejected because it does not define a supported table.

Columns are the union of keys in first-seen order. A key missing from a row becomes an empty cell. null also becomes an empty cell, so CSV cannot distinguish these cases after conversion.

[{"name":"Ada","score":12},{"name":"Jane","active":true}]

Understand nested and typed values

Numbers and booleans become text cells. Nested objects and arrays become JSON strings inside quoted CSV fields. They are not expanded into extra columns or rows.

On a later CSV → JSON conversion, every cell will be a string. A round trip therefore does not preserve JSON types, missing keys or null values. Keep the original JSON if these distinctions matter.

Keep formula protection enabled

Spreadsheet applications may interpret cells beginning with =, +, - or @ as formulas. By default the tool adds an apostrophe before such values, including when a leading whitespace or control character hides the prefix.

The same protection is applied to header cells. It may change a negative number into a text cell. Disable protection only when you understand the destination application and trust all source values; spreadsheet behavior varies.

Inspect the downloaded file

The output uses UTF-8 and CRLF record endings. Cells containing a delimiter, quotation mark or newline are quoted; inner quotation marks are doubled. Select the same delimiter in the destination import dialog.

Test a harmless value such as =1+1 before importing a larger file. Inspect the raw CSV to confirm the apostrophe is present with protection enabled, then verify the import treats the cell as text.