JSON to CSV Converter

The converter reads every object in your array and collects their keys in the order it first meets them. Those keys become the header row. An object that lacks a key gets an empty cell in that column, so rows with different fields still line up:

Alan's row has no name, so the cell is blank, and Ada's row has no email. Nothing is dropped and no column is invented. If you paste a single object instead of an array, you get a header row and one data row.

Each cell holds one value, and the converter does not split nested data into extra columns. This is the part most likely to surprise you:

• A nested object such as address comes out as the literal text [object Object]. Its contents are lost.
• An array of plain values such as tags is joined with commas into one quoted cell: "math,code".
• true stays as the word true, and null becomes an empty cell.

If your records contain objects, flatten them before converting. Rename address.city to a top-level key like address_city, or move each nested field up one level. Then every value lands in its own column.

A value that contains a comma, a double quote or a line break is wrapped in double quotes, and any quote inside it is doubled. Everything else is written as is, without quotes:

The line break inside lines is kept inside the quoted cell, so the record spans two physical lines. Spreadsheets read this correctly; a script that splits the file on newlines will not.

Your JSON is parsed before it is written out, so numbers come out in their shortest form: 1.50 becomes 1.5. Integers longer than about 16 digits can't be held exactly, and 12345678901234567890 comes out as 12345678901234567000. Store long IDs as strings in the JSON if you need them intact.

Text values keep their leading zeros, so a ZIP code stored as "02134" is written as 02134. A spreadsheet may still read that column as a number when you open the file and drop the zero. Import the column as text to keep it.