JSON to CSV Converter – Convert JSON to CSV Online

What is a JSON to CSV converter?

A JSON to CSV converter turns structured JSON data into comma-separated values: a header row naming the columns, then one row per record. JSON describes objects and arrays; a CSV describes a table. The converter is the mapping between the two - the keys of your objects become the column names, and each object in the array becomes one row of the spreadsheet.

That is the conversion you need whenever data arrives as JSON but has to be worked with in a table. Typical uses are exporting API responses to a spreadsheet, loading a dataset into a reporting tool, checking a JSON payload by eye in Excel, and feeding data into a script or a database import that expects rows and columns.

Nothing is uploaded and no account is needed. The conversion runs locally in your browser, so your data stays on your machine - which matters when the JSON is a customer record, a log export or an internal API response.

How to convert JSON to CSV

The workflow is three steps: paste, convert, copy.

1. 1Paste valid JSON into the JSON Input panel. An array of objects gives the cleanest table, and Load Example or Upload .json will fill the panel for you.
2. 2Click Convert to CSV. The JSON is parsed, checked and then mapped onto a table: each object becomes a row and each field becomes a column.
3. 3Review the generated CSV in the CSV Output panel. Values containing a comma, a quote or a line break are quoted so the columns stay aligned.
4. 4Copy the CSV or press Download to save it as a .csv file you can open in Excel, Google Sheets or any data-processing tool.

The conversion happens entirely in your browser. There is no upload step, no account and no usage limit, so it is equally usable for a three-line snippet and for a multi-megabyte API response.

JSON to CSV example

The object below is converted to the CSV beside it. Each JSON key becomes a CSV column of the same name, and the single object becomes a single row under those headers.

When the JSON is an array of objects, every object becomes its own row and the columns are shared. That is the shape almost every API returns, and it is what makes the result open directly in a spreadsheet.

{
  "name": "John",
  "age": 30,
  "city": "Lahore"
}

name,age,city
John,30,Lahore

Nested JSON and escaped values

CSV is a flat format, so nested JSON has to be reshaped rather than copied. A nested object becomes one column per leaf, named with the path that leads to it - address.city, stats.views - so nothing is hidden inside a cell and every value can be sorted and filtered in a spreadsheet.

A JSON array inside a record has no column of its own, so its items are joined into a single cell with a semicolon between them: ["JavaScript", "Python"] becomes JavaScript; Python. A semicolon rather than a comma is used on purpose, because a comma would look like a new column to the spreadsheet.

Values are written exactly as they are in the JSON, and a value that contains a comma, a double quote or a line break is wrapped in double quotes so it stays in one cell. In the example below, "New York, NY" and a value containing quotes both survive the round trip into Excel.

[
  {
    "name": "John Doe",
    "city": "New York, NY",
    "note": "He said \"hello\"",
    "address": {
      "city": "Lahore",
      "country": "Pakistan"
    },
    "skills": ["JavaScript", "Python"],
    "active": true,
    "score": null
  }
]

name,city,note,address.city,address.country,skills,active,score
John Doe,"New York, NY","He said ""hello""",Lahore,Pakistan,JavaScript; Python,true,

JSON vs CSV: when to use which

Neither format is universally better - they are built for different jobs, and choosing the right one is usually about who reads the data next.

A practical rule: if a program on the other end parses the data, or if it travels over a network or gets stored in a database column, keep it as JSON. If a person has to read, sort, filter or chart the data, convert it to CSV - every spreadsheet and most BI and reporting tools expect exactly that shape.

When JSON to CSV conversion works best

CSV is inherently tabular: every row has the same columns and every value is text in one cell. JSON that already looks like a table therefore converts cleanly - an array of objects with the same fields in each one, which is what a database export, a list endpoint or a fixture file usually contains.

Nested JSON converts too, but it has to be flattened, because a cell cannot hold a sub-table. This converter flattens nested objects into dot-notation columns and joins an array inside a record into one cell, so the data is never dropped. Two limits are worth knowing: a JSON null becomes an empty cell, so it is indistinguishable from an empty string once it is in the spreadsheet; and nesting deeper than eight levels is written as JSON text in a single cell instead of being split into columns.

If you need the exact types, the exact nesting or multiple records per field, JSON is the better format and CSV is the wrong tool. Converting is still the right call when the next step is a spreadsheet, a pivot table, a CSV import or a quick look at the data.

Related JSON tools

Converting JSON to CSV is only one of the jobs a JSON workflow involves. These are the other Calzyra tools you are most likely to reach for next.

• Need to make minified JSON readable before you convert it?JSON Formatter
• Need to know whether a payload is valid JSON and where it breaks?JSON Validator
• Need to shrink JSON back to a single line for a URL or a payload?JSON Minifier
• Need to explore a deeply nested document as collapsible nodes?JSON Tree Viewer
• Need a flattened key-value view of the same nesting?JSON Flattener
• Need YAML output instead of CSV?JSON to YAML Converter
• Need an XML document instead of CSV?JSON to XML Converter

Frequently Asked Questions