UtilityPilot.Find a tool

Data & Tables

JSON to CSV Converter

Turn a JSON array of object records into a downloadable table. Choose nested-object flattening and keep only the columns you need.

Processed in your browserPrivacy details ↗

5 MiB per input · 50,000 records · 200 columns

Adjust your options

Spreadsheet-safe export can change formula-like cells by adding an apostrophe. Turning it off preserves raw values; use raw exports only in a trusted importer.

No sign-up. No upload.

How to use this tool

  1. Paste an array of objects, or select its JSON file.
  2. Choose flattening, output delimiter and optional column positions.
  3. Convert, inspect the table preview and download the complete CSV.

How the operation works

Keys are collected in first-seen order across all records. Nested object fields can become dot-separated columns. Arrays stay serialized JSON inside one cell rather than multiplying rows. Missing and null values both become empty cells, so this conversion is not generally reversible. A literal dotted key conflicting with a flattened path is rejected.

Start with an array of object records

The accepted shape is a nonempty JSON array whose items are objects. Wrap a single object in square brackets if it represents one record. A scalar array such as [1,2,3] has no named record fields and is not accepted. An empty array provides no header schema.

Column names are collected in first-seen order across all records. If the second object introduces a new key, its column is added rather than discarded. Missing fields become empty cells. Select column positions only after understanding that combined schema; positions begin at one, and the order you enter becomes the output order.

Choose a nested-data strategy

With flattening enabled, nested object fields become dot paths such as address.city. Arrays remain serialized JSON in one cell; they do not multiply a record into several rows. With flattening disabled, nested objects are also serialized inside cells. This avoids inventing a relationship between parallel arrays or guessing a database join.

A literal key containing a dot can conflict with a path produced by flattening. Such a collision is rejected, rather than overwriting a value. If a document has a large wrapper object around the relevant records, extract that array deliberately after inspecting it in JSON Viewer.

CSV escaping and spreadsheet-safe export

A field containing the selected delimiter, a quote or a line break is quoted. Quotes inside quoted fields are doubled. For example, a cell containing Tea, "hot" needs the CSV spelling "Tea, ""hot""". These structural rules keep punctuation inside its original field.

Spreadsheet-safe export is enabled by default. It prefixes formula-like values with an apostrophe so a spreadsheet is less likely to treat them as formulas. This deliberately changes such cell values. Turn it off only for a trusted importer when exact raw strings are required. The receiving application can still infer dates and numbers, so import identifier columns as text.

What can change during conversion

CSV has no general equivalent of JSON types or nested structure. Null and a missing value both become empty cells here. Numbers and booleans become text representations; reading the file in another program may apply different typing rules. A round trip through CSV to JSON is therefore not guaranteed to reconstruct the original document.

The preview shows at most 50 records, while the exported result contains all accepted records within the 5 MiB input, 50,000-record and 200-column limits. For configuration-format conversion instead of a table, use JSON / YAML Converter. Keep the original JSON whenever data types matter.

A worked example

[{"id":"00123","address":{"city":"Lahore"}}]

id,address.city 00123,Lahore

A nested array is not automatically expanded into several rows. Spreadsheet software may infer types when opening the result; import identifier columns as text to preserve leading zeros.

Processing and privacy

JSON to CSV converts records locally; keys and values are not sent to a conversion server. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.

Frequently asked questions

Can I convert a single object?

Wrap it in square brackets to make a one-record array. Empty arrays have no tabular schema and are rejected.

What happens to nested arrays?

They stay serialized JSON inside one cell; they do not multiply into several rows.

Are null and missing different?

Both become empty cells in CSV, so a round trip cannot reconstruct the distinction.

Why prefix formula-like cells?

Spreadsheet-safe mode reduces the chance a spreadsheet treats the cell as a formula. Turn it off only for trusted importers.

How this tool was checked

JSON to CSV was checked with nested objects, arrays kept inside one cell, dot-path collisions, missing and null fields, column reordering and identifiers with leading zeros. See the testing method or report a failure.