CSV to JSON
Turns a CSV table into an array of JSON objects.
Paste a JSON array or drop a .json file to get a CSV table that opens in Excel or Google Sheets. Nested objects are flattened into their own columns.
Excel-safe adds a UTF-8 byte order mark so Excel reads accents correctly, and puts an apostrophe before cells that start with =, +, -, or @ to block formula injection.
.json file up to 5 MB.value.{"address":{"city":"Lisbon"}} becomes a column named address.city.null values and missing keys give an empty cell.=, +, -, @, a tab, or a carriage return, so a spreadsheet can't run them as formulas.Input:
[{"id":1,"name":"Ana","address":{"city":"Lisbon"}},{"id":2,"name":"Ben","email":"[email protected]"}]Output:
id,name,address.city,email 1,Ana,Lisbon, 2,Ben,,[email protected]
A value with a comma is quoted: [{"note":"Hello, world"}] gives a note column whose cell is "Hello, world".
JSON is how most APIs deliver data, but spreadsheets and many business tools expect CSV. Converting lets you:
In countries where the comma is the decimal separator, such as Germany, France, and Brazil, Excel expects fields separated by semicolons. If your CSV opens with everything in one column, convert again with the semicolon delimiter.
An array of objects works best, with each object becoming one row. A single object becomes a one-row CSV.
They are flattened into columns with dot notation, so {"address":{"city":"Lisbon"}} becomes a column named address.city.
Yes. For non-English characters, turn on "Excel-safe" so Excel detects UTF-8. In regions where Excel expects semicolons, pick the semicolon delimiter.
No. The conversion runs in your browser.
Often used together with the JSON to CSV.
Turns a CSV table into an array of JSON objects.
Beautifies or minifies JSON.
Converts JSON into well-formed, indented XML.