By ByteGuide Tools · Reviewed 31 October 2026

A reproducible example showing quoted fields, leading zeros, nested values and safe spreadsheet checks.

JSON represents structured values, while CSV represents rows and fields. Converting between them is useful when moving a small dataset into a spreadsheet or inspecting a table in code. It is not always a lossless round trip. Decide which columns and data types must survive before converting, and test a few representative rows before trusting a large result.

Begin with a small JSON array

[{"name":"Ada","code":"008","score":8},{"name":"Lin, Jr.","code":"009","score":9}]

Paste this example into JSON to CSV. The export contains name, code and score columns. The comma in “Lin, Jr.” stays inside a quoted field, rather than creating a fourth column. All cells are quoted, and quotation marks inside values are doubled. These are common CSV conventions described in RFC 4180; a destination may still use a different delimiter or import setting.

Check JSON syntax separately

Use JSON formatter if the source does not parse. JSON property names and strings use double quotes, and trailing commas are invalid. Pretty printing changes presentation, not the meaning of an application-specific schema. The formatter cannot tell you whether a required business field is absent. The MDN JSON guide explains the underlying syntax and data types.

Understand what this converter preserves

JSON to CSV combines the distinct object properties into columns. A missing property becomes an empty cell, and a nested object becomes JSON text within a cell. If you need an address’s city and postcode in separate columns, flatten that structure first. Empty text, null and a missing property may no longer be distinguishable after export.

CSV to JSON intentionally keeps values as strings

When converting the exported CSV back to JSON, code “008” remains a string with its leading zeros. A score also becomes a string, even if it began as a JSON number. Convert known numeric fields explicitly in your own application. Automatic guessing could turn a product code into a number or interpret a date using the wrong regional convention.

Open the spreadsheet carefully

Choose an import mode that treats identifiers as text. ByteGuide prefixes formula-like CSV values with an apostrophe as a precaution, so inspect those cells when a downstream system expects exact original text. The converter accepts comma separators, a unique nonempty header row and a consistent column count. For a semicolon-separated export, return to the source application and select comma-separated CSV.

Finally, compare row counts and several special cases: a comma within a name, an empty value, a leading-zero code and any nested data. Keeping the original export is often more valuable than assuming that a successful conversion message proves that all meaning survived.

Use the related tools

• JSON formatter
• JSON to CSV
• CSV to JSON

All guides · Editorial approach · Report a correction