JSON to CSV Converter

Convert JSON arrays to CSV format and CSV files to JSON with column mapping and data type detection.

Tested tool guide Tested browser tools Checked August 16, 2026

What JSON to CSV Converter does and how it behaves

JSON to CSV Converter changes a top-level JSON array of records into a comma-separated table and changes a CSV table back into JSON objects. It derives candidate columns from record fields, supports column mapping, and applies data type detection while reading tabular values. The common surprise is that the formats do not describe the same shapes: JSON can nest objects and arrays, but CSV has only rows and cells. CSV also carries limited type information, so an inferred number or boolean may not match the user's intended string. Review both field mapping and detected types before relying on a round trip.

How the result is produced

JSON records to CSV rows

For JSON-to-CSV conversion, each member of the top-level array is treated as a source record. Object keys provide the available fields, and the column mapping determines which field feeds each CSV column. Values from successive records then occupy rows beneath those headers. Records with missing, extra, or differently ordered keys require attention because a rectangular CSV table cannot preserve every structural distinction among heterogeneous JSON objects.

CSV rows to typed objects

For CSV-to-JSON conversion, a header row can supply candidate property names while later records supply values for JSON objects. Quoted delimiters and quoted line breaks belong to one CSV field under the common CSV format, so quoting affects row and column boundaries. Data type detection determines whether recognized cell text remains a JSON string or becomes another supported JSON value type; inspect that decision for every important column.

Good uses

Preparing a flat JSON array returned by an API for spreadsheet review, with selected object fields aligned under stable CSV headers and one source record represented per row.
Recasting a CSV export from a billing, inventory, or survey system as JSON records whose mapped properties match the field names expected by another import process.
Testing a migration sample before bulk conversion to see whether numeric-looking identifiers, blank cells, quoted commas, and boolean-like text receive the intended JSON representation.

Limits and checks

Nested JSON values do not have a native CSV equivalent. An object or array placed in a cell may need flattening, serialization, or a separate table, and a later CSV-to-JSON pass cannot infer the original nesting unless that representation is defined outside the CSV.
Type detection is interpretation, not proof. Leading-zero codes, long identifiers, date-like strings, boolean-like words, and empty cells are especially easy to misclassify. Compare each generated JSON value and its type with the source meaning, not merely with how the value looks on screen.
CSV is a family of dialects rather than a perfectly uniform interchange format. A file's delimiter, quoting rules, header convention, newline style, or encoding can affect parsing. If columns shift or rows split, confirm the source CSV format instead of assuming the resulting JSON records are correct.

Common questions

Will converting JSON to CSV and back reproduce the original JSON exactly?

No, not in every case. A flat array of uniform scalar-valued objects can map cleanly, but missing properties, explicit nulls, empty strings, and nested values can become indistinguishable or require conventions in CSV. Treat the conversion as a tabular representation. If exact round-trip fidelity matters, compare parsed values and types, not only the visible rows.

Why did a CSV identifier become a number in JSON?

Data type detection can interpret digit-only cell text as numeric data even when the value is actually an identifier. That distinction matters for leading zeros and long digit strings. Map the column as text if that control is available. If it is not, verify the generated JSON and restore strings before using the result as an import payload.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.