CSV is useful when a spreadsheet or import system needs rows and columns rather than nested API data. Start with an array of objects so each object can become one row.

Open the JSON to CSV Converter to follow the workflow. Processing runs in your browser; the tool does not upload the input for conversion.

A practical workflow

  1. Paste an array of objects. Use one object per intended data row.
  2. Choose a delimiter and safety mode. Select comma, semicolon, tab or pipe; keep spreadsheet protection on for spreadsheet use.
  3. Review rows and columns. Process the input and inspect the generated CSV, including nested cells.
  4. Download converted.csv. Import the file with the same delimiter in your destination application.

Try a concrete example

The following demonstration input is also available in the workspace. Replace it with your own data after checking the expected behaviour.

[{"name":"Ada","role":"Developer"},{"name":"Ben","role":"Designer"}]

With the default settings, the result is:

name,role
Ada,Developer
Ben,Designer

Define a consistent row model

The converter collects the union of property names from all objects. If a later object has an extra key, that key gets a column. A missing property becomes an empty cell. CSV does not preserve all distinctions between an absent value, an empty string and a null value, so review those cases before using the file for an import.

Nested data needs an explicit decision

Objects and arrays inside a cell are written as JSON text. This preserves their visible structure inside one cell rather than guessing how to flatten it. A downstream system may need a separate flattening step or a relational table. Inspect at least one nested cell in the destination application.

Spreadsheet protection changes certain cells

Spreadsheet software can interpret cells beginning with characters such as = as formulas. The default safety option prefixes formula-like text with an apostrophe. That is useful for a spreadsheet, but it changes the literal cell value. Turn it off only when your destination needs raw data and handles formula interpretation safely.

If the result needs attention

Use an array of objects. The spreadsheet-safety option adds an apostrophe to formula-like text; turn it off only when exact raw cells are needed.

Read the exact error before changing the input. Keep a copy of the original, reduce the sample when investigating a large file, and use the destination application to verify that the result has the meaning you intended. The tool processes the supplied data; it cannot infer an unstated application schema or project requirement.

For related inspection, use the JSON Formatter or JSON Diff Checker. They help make structure and changed values visible before you move the data into another workflow.

Sources and further reading

Turn the next step into a project

Need help with a brand identity, business website or launch assets? Explore SOPIDOTECH services and client projects, or discuss your brief.

Keep learning