Convert JSON to CSV
To convert JSON to CSV, paste or drop your JSON into the converter on this page and click Convert to CSV. A spreadsheet engine running as JavaScript in your browser does the parsing and writing, so the data is turned into rows and columns on your own machine, never on a server.
Runs in your browser. Your file never leaves your device.Drop your JSON hereChoose a JSON to convert
It becomes a CSV right in your browser, up to 100 MB
Your file never leaves your device
Works in airplane mode. See the proof
Limits, published exactly
| Where it runs | In your browser. The file never leaves your device. |
|---|---|
| Free conversions | Unlimited. No account, no ads, no queue, no watermark. |
| Max file size, free | 100 MB |
Why convert JSON to CSV?
The everyday case is getting API output or an export dump into a spreadsheet. JSON is great for code and lousy for eyeballing in bulk, so the moment you need to sort, filter, pivot or hand a colleague something to open in Excel or Google Sheets, CSV is the bridge. Converting takes structured records and lays them out as a flat grid, one row per object, that any spreadsheet tool reads instantly. It is the quickest way to make machine-shaped data human-readable and editable without writing a script for it.
What is JSON?
JSON is the lingua franca of APIs and config: nested objects and arrays in a compact, human-readable text form that almost every language can parse. It handles structured and hierarchical data that a flat table cannot. For tabular data it is often paired with CSV, and for configuration with YAML.
What is CSV?
CSV is the plainest way to store a table: one row per line, fields separated by commas, readable by every spreadsheet and database tool. It carries no formatting, formulas, or multiple sheets, which is exactly why it travels so well between programs. The tradeoff is that anything richer than a flat grid has to be flattened to fit.
Quality and what to expect
For this to work cleanly the JSON has to be tabular: an array of row objects, a single object, or a {data:[...]} envelope wrapping the rows. The honest limit is depth. CSV is a flat grid, so when a value is itself a nested object or array, it gets flattened or stringified into a single cell rather than spread across proper columns. Deeply nested JSON therefore does not map neatly onto a table; you get readable rows for the top-level fields and JSON-ish blobs for the nested parts. Column order follows the keys found, and missing keys leave empty cells.
JSON to CSV FAQ
What JSON shape does this expect?
An array of row objects works best, but a single object or a {data:[...]} envelope is also accepted. Each object becomes a row and its keys become the column headers, which is what spreadsheet tools want to see.
What happens to nested objects and arrays?
CSV has no concept of nesting, so a nested value is flattened or stringified into one cell rather than expanded into columns. Flat records convert cleanly; deeply nested JSON will leave JSON-like text inside some cells.
Will the CSV open correctly in Excel and Google Sheets?
Yes. The output is standard comma-separated values written by a real spreadsheet engine, so Excel, Google Sheets, Numbers and database import tools all read it directly without any extra cleanup.
Is my JSON sent anywhere to be converted?
No. The SheetJS engine runs as JavaScript inside this browser tab, so your data is parsed and written to CSV locally. Nothing about the JSON, however sensitive, is transmitted to us or anyone else.