JSON to CSV Converter

Turn a JSON array of objects, or JSON Lines with one record per line, into a CSV table you can open in Excel or Google Sheets. Nested objects can become their own columns, and accents survive thanks to a UTF-8 BOM.

  • Free
  • No upload
  • No sign-up

CSV to JSON and JSON to CSV

Quoted fields, line breaks inside cells, semicolon CSV from Excel and JSON Lines are handled.

or drop a .csv / .json file here

    CSV options

    Runs entirely in your browser. Your data, files and text are never uploaded.

    From JSON records to spreadsheet rows

    Every object in the array becomes one row, and the columns are the union of all keys in the order they first appear, so records with missing fields still line up. An array of arrays is written row by row as it is, and a single object becomes a one-row table.

    Nested objects and arrays are written into a cell as JSON text by default, which keeps all the information. Switch on "Flatten nested objects" to spread them over columns such as address.city and address.zip, which is easier to filter and sort in a spreadsheet.

    Excel on Windows only reads a CSV as UTF-8 when the file starts with a byte order mark; without it, letters like č, ö and ß turn into gibberish. The BOM option is on by default for downloads. Choose semicolons as the delimiter if your Excel uses a decimal comma, and CRLF line endings for the widest compatibility.

    How to use the JSON to CSV Converter

    1. Paste JSON into the input or open a .json, .jsonl or .ndjson file.
    2. Choose the delimiter and line endings, and whether nested objects should be flattened into columns.
    3. Read any error message: invalid JSON is explained with the line and column where it breaks.
    4. Copy the CSV or download it as a .csv file that opens straight in Excel.

    Frequently asked questions

    Which JSON structures can be converted?

    An array of objects, an array of arrays, a single object, or JSON Lines (NDJSON) with one JSON value per line. Values inside cells are written as plain text, numbers or JSON.

    Why do accented letters look wrong in Excel?

    Excel needs a UTF-8 byte order mark to detect the encoding. Keep "Add a UTF-8 BOM" switched on before downloading, and the letters display correctly.

    Are long numeric IDs kept exactly?

    In browsers that support it, integers longer than 15 digits are kept exactly as written. Elsewhere such numbers are counted and you are warned that they may have been rounded.

    My JSON is invalid. Where is the mistake?

    The converter reports the line and column of the first problem, for example a missing comma or a trailing comma after the last item, so you can fix it quickly.