Convert JSON to CSV!

Input JSON to convert it into CSV! Paste straight into Excel or Google Sheets.
JSON
Result

Convert JSON to CSV!

Paste a JSON array and each object becomes a row, with its keys as column headers. The copy button at the top right of the result puts comma-separated CSV text on your clipboard, ready to paste into Excel or Google Sheets.

Reach for it when JSON pulled from an API or a database has to go to an ops or product team as a table, or when you want to sort and filter a few hundred log entries in a spreadsheet.

How to use

  1. Paste an array of objects ([{...}, {...}]) into the JSON box. A single object gives a one-row table.
  2. Check the column order and values in the table shown under Result.
  3. Press the copy button (or Ctrl/⌘+Enter) to copy CSV text, then paste it into cell A1 of your sheet.

Example

Input (JSON)
[
  { "orderNo": 5001, "customer": "Kim, Minji", "total": 42000, "tags": ["gift", "express"] },
  { "orderNo": 5002, "customer": "Lee", "total": 15500, "memo": "leave at door" }
]
Output (CSV)
orderNo,customer,total,tags,memo
5001,"Kim, Minji",42000,"[""gift"",""express""]",
5002,Lee,15500,,leave at door

The customer value contains a comma, so it is wrapped in double quotes; the tags array lands in a single cell as JSON text, with inner quotes doubled as "". memo, missing from the first row, still gets its own column, and that row's cell is left empty.

Supported features

  • Columns are the union of every object's keys, in the order they first appear, so a key present in only one object is not dropped.
  • Values containing commas, double quotes or line breaks are quoted per RFC 4180, with " escaped as "".
  • Nested objects and arrays are not expanded; they go into one cell as JSON strings such as {"a":1}.
  • The result is previewed as an HTML table; CSV text is produced when you copy.

Use cases

Sharing an API response with non-developers

A raw order-list response pasted into chat is hard to read. Converted to CSV and dropped into a sheet, the operations team can filter and total it right away.

Reviewing MongoDB or Firestore exports

Documents exported from a document database rarely share the exact same fields. Because every key becomes a column, the table shows at a glance which documents are missing which fields.

Notes and limitations

  • The delimiter is always a comma. Excel set to a European locale that expects semicolons may need Text to Columns after pasting.
  • A JSON null and a key that is absent from a row both become an empty cell, in the table preview and in the copied CSV alike. If you need to tell them apart, replace null with a marker value before converting.
  • To get columns like user.name from nested data, run the JSON flatten tool first and convert its output.
  • An array of plain numbers or strings ([1, 2, 3]) cannot form rows and returns an error.
  • There is no file download; output goes to the clipboard only.

FAQ

Everything lands in one column after pasting into Excel. Why?

Excel did not treat the comma as a separator. Use Data → Text to Columns and choose comma. If you save the text as a .csv file and non-ASCII characters break when reopening, save it as UTF-8 with BOM.

Zip codes like 00123 or long numeric IDs change in the spreadsheet.

The CSV keeps the value exactly, but Excel reinterprets it as a number on paste, dropping leading zeros or switching to scientific notation. Format those columns as Text before pasting.

How is the column order decided?

Keys of the first object come first; keys that first appear in later objects are appended to the right in order. Reorder the first object's keys if you want a specific layout.