Convert JSON to CSV – JSON to CSV Converter

Paste the JSON above or open the .json file with “Open file”, then select “JSON to CSV”. The tool expects a list of objects, such as [{"id": 1, "name": "Anna"}, {"id": 2, "name": "Ben"}]. This produces a header row, “id,name”, and one row per object. The columns include every key; if an object lacks a key, its cell stays empty. The tool also reads a single object, JSON Lines and a list inside an object such as {"data": [...]}. Copy the result or download it as a .csv file.

Select “CSV to JSON” and paste CSV with a header row, or open a file. “id;name” followed by the row “1;Anna” becomes [{"id": 1, "name": "Anna"}]. The tool detects the delimiter (comma, semicolon, tab or pipe) automatically, but you can set it yourself. Without a header row, you get a list of arrays; with JSON Lines, you get one line per record. First save an Excel spreadsheet as “CSV UTF-8” in Excel. If it contains numbers with decimal commas, such as “19,90”, set the decimal separator to comma so the value becomes the number 19.90.

Select “JSON to CSV,” open your .json file with “Open file,” and choose the “Excel (Germany)” preset. Download the result as a .csv and double-click to open it in Excel: semicolons separate columns, umlauts are preserved, and numbers use decimal commas. The tool creates CSV, not an .xlsx file, but Excel opens CSV directly and you can then save it as .xlsx. Alternatively, use Excel’s “Data” > “Get Data” > “From File” > “From JSON” import (Power Query).

If your Excel uses a comma as its decimal separator, as with German regional settings, it expects a semicolon as the field delimiter. Excel also reads a CSV file as UTF-8 only if it has a BOM (Byte Order Mark); otherwise, accented characters may appear corrupted. Choose the “Excel (Germany)” preset: semicolons, decimal commas, Windows line endings and a BOM in the download. “19.9” then becomes “19,9”, while “Müller” stays “Müller”. For Excel using a period as the decimal separator, as with English regional settings, the “Standard” preset is enough.

Click “Open file” or drag the file onto the input field. Below the result, the preview shows the data as a table: one row per object for JSON, or CSV as a spreadsheet program would read it. The preview shows the first 100 rows and 50 columns; copying and downloading include everything. Files are read up to 5 MB and are not uploaded. To make JSON easier to read with indentation, use the JSON Formatter.

CSV is flat, so nested objects are flattened using dot notation: {"address": {"city": "Köln"}} becomes the column “address.city”. You can write arrays in two ways. “As JSON text” puts the whole array in one cell, such as ["admin","dev"]. “Expanded” makes each element a column (“tags.0”, “tags.1”). To reverse the process when converting CSV to JSON, enable “Nest dot-notation columns”. Information CSV cannot represent, such as the difference between null and an empty string, is lost.

CSV is a flat table: a header row followed by one record per row, with fields separated by a delimiter. JSON stores objects and lists that can be nested, and has distinct types for numbers, booleans and null. CSV opens in any spreadsheet program and is compact; JSON is better suited to APIs and nested data. Converting JSON to CSV therefore flattens nested structures.

No. Reading, conversion, table preview and downloading all happen entirely in your browser. Your data is neither uploaded nor stored, including files you open or drag onto the field. The limit therefore depends on your device: the tool opens files up to 5 MB and rejects inputs with more than 5 million cells (or more than 5,000 columns when converting JSON to CSV) before the browser freezes. This matters for customer lists, database exports and API responses containing tokens.