JSON to CSV

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from JSON to CSV

JSON to CSV converts JSON records to CSV. A collection of similarly shaped JSON objects can become rows, with property names used as column headers. Nested objects and arrays do not fit a flat table automatically. Decide whether to flatten them or represent them as cell text. Check commas, embedded quotes, newlines, and values that spreadsheet software might reinterpret as formulas. Use the worked example to understand what a successful result looks like, then compare it with a small sample of your own input. Keep the original available until you have checked the output in its destination. Conversion establishes a representation; it does not establish that the underlying information is correct or that the receiving application accepts every supported feature.

Guide updated October 13, 2026

How to use this tool

1. Enter or load JSON records using the input controls. Begin with the worked example or a small sample for which you know the expected result.
2. Review any available conversion options, then inspect the CSV result. Resolve a reported parse error at its source before attempting to reuse the output.
3. Check the example below against your own data. Check commas, embedded quotes, newlines, and values that spreadsheet software might reinterpret as formulas.
4. Copy or save the resulting CSV content using the controls provided, then validate it in the application or parser that will actually consume it.

SEE IT IN PRACTICE

A worked example

[{"name":"Ada","score":10}]

name,score
Ada,10

The two object properties become two columns, and the object becomes one data row. Quoting may vary with export settings.

Nested records need a table decision

A customer object with several phone numbers is not naturally a single flat row. You might place the list in one cell, create multiple rows, or export a related table; each choice has different meaning. Inspect the converter’s chosen representation instead of assuming the output is lossless. Sparse properties also need a consistent empty-cell policy.

A consistent set of columns

JSON objects in an array can have different property sets. A CSV file instead needs a stable sequence of columns, so verify how missing and additional properties are represented across rows. Review the header union rather than only the first object. Keep a unique record identifier when flattening nested data; it helps reconnect rows if a repeated child collection must be exported separately.

When this tool is useful

• Prepare spreadsheet-ready API exports while retaining a separate copy of the source.
• Use a small example to troubleshoot inconsistent property sets and identify a representation mismatch.
• Create simple rows for a tabular import without manually rewriting every field or symbol.

Tips for a better result

• Nested objects and arrays do not fit a flat table automatically. Decide whether to flatten them or represent them as cell text.
• Check commas, embedded quotes, newlines, and values that spreadsheet software might reinterpret as formulas.
• After changing formats, compare meaningful values rather than whitespace alone. Read the CSV output with its intended parser when exact types or escaping matter.

Frequently asked questions