JSON to CSV

Convert JSON to spreadsheet-ready CSV, flattening nested objects into dot-notation columns.

ConvertersRuns in your browserFree, no sign-up

Options

Delimiter

Flatten nested objects

Creates contact.email columns instead of one cell of JSON.

Include header row

Quote every field

Safer for tools that guess column types from unquoted values.

Windows line endings (CRLF)

Required by strict RFC 4180 and older Excel versions.

JSON input

CSV output

Output appears here as you type.

Ctrl + Enter to run

About the JSON to CSV

Flattens an array of JSON objects into a spreadsheet-friendly table, with nested objects becoming dotted column names so `{"user":{"name":"Ada"}}` yields a `user.name` column. Values containing commas, quotes or newlines are quoted and escaped on the way out.

Arrays are the case with no clean answer, because CSV has no way to express a variable number of values in one cell. If your records have arrays of differing lengths, expect information loss and consider whether a tabular format is the right destination at all.

Frequently asked questions

How is nested JSON handled?

Nested objects are flattened to dot-notation columns, so {"contact": {"email": "…"}} becomes a contact.email column. Most converters stringify the nested object into a single cell instead, which produces a CSV that is useless in a spreadsheet. Arrays of primitives are joined with semicolons, because exploding them would change the row count.

What if my records have different keys?

Every key found anywhere in the data becomes a column, in first-seen order, and missing values are left empty. Using only the first record's keys — which is what many converters do — silently drops columns whenever the data is not uniform, and real API payloads rarely are.

Why would I need CRLF line endings?

RFC 4180 specifies CRLF, and some older Excel builds and Windows tools mis-parse a file that uses bare LF. Modern Excel, Numbers and Google Sheets all handle LF fine, so leave it off unless you hit a problem.