JSON to CSV

CSV is flat and JSON is not. Nested objects and arrays have to be flattened into columns or dropped, which is the single thing that goes wrong most often here.

Runs in your browser // nothing is uploaded

Loading converter

What survives the conversion

Derived from what each format is able to store, not from what the conversion promises.

Kept

JSON carries nothing that CSV can also hold.
Row and column values, which JSON could not store

Lost

Nested structure
Data types

Settings used

Flattened to columns from the union of top-level keys, quoted per RFC 4180.

When not to convert

Not for deeply nested data. The result will either be lossy or unreadable.

About these formats

Data

What is a JSON file?

JSON is a lightweight text format for structured data, standardised as ECMA-404. It supports objects, arrays, strings, numbers, booleans and null, and nothing else. That deliberate minimalism is why it replaced XML as the default format for web APIs and configuration.

Read the format guide

Data

What is a CSV file?

CSV is plain text where each line is a row and values are separated by commas. It is the most portable tabular format in existence and has no types, no formulas and no sheets. Its weakness is ambiguity: quoting, encodings and delimiters vary between tools.

Read the format guide

Common questions

Does converting JSON to CSV lose anything?

Yes. Nested structure, Data types cannot be carried into CSV and are dropped. CSV is flat and JSON is not. Nested objects and arrays have to be flattened into columns or dropped, which is the single thing that goes wrong most often here.

Are my files uploaded when I convert JSON to CSV?

No. The conversion runs in your browser tab, so the file is never transmitted and the page works offline once loaded.

What settings does Filoven use for JSON to CSV?

Flattened to columns from the union of top-level keys, quoted per RFC 4180.

When should I not convert JSON to CSV?

Not for deeply nested data. The result will either be lossy or unreadable.