JSON to CSV Converter for developers and analysts. Paste JSON, flatten nested objects, pick which array to convert, and export Excel-ready CSV. Includes CSV to JSON reverse conversion with delimiter auto-detection. Handles arrays, nested keys, custom delimiters, Unicode, and Excel BOM. Free, private, no signup.
[{"id":1,"name":"Alice"},{"id":2,"name":"Bob"}]Each object becomes a row. The union of all keys becomes the header row. Missing values become empty cells.
[{"id":1,"address":{"city":"Berlin","zip":"10115"}}]When Flatten nested objects is enabled, nested keys are joined with dots:
address.city, address.zip. Disable flattening to store the entire nested object as a JSON string in one cell.{"data":[{...}], "meta":{...}, "errors":[{...}]}When the JSON contains more than one array of objects, the Convert this array dropdown appears above the options. Pick the path you want to turn into a table. The tool auto-selects the largest one by default.
[{"id":1,"tags":["a","b","c"]}]Arrays of primitive values are joined with semicolons in a single cell:
a; b; c.[{"id":1,"items":[{"sku":"A1"},{"sku":"B2"}]}]The inner array is stored as a JSON string in one cell, since it cannot be flattened into a single column. Use a separate nested-array handling approach if you need one row per inner item.
He said "hi" becomes "He said ""hi""".Tip: press ⌘/Ctrl + Enter inside any textarea to run the active panel's conversion.
An API response is not a spreadsheet.
You paste it into Excel. The nested objects become a single messy cell. The arrays break across columns. Nothing lines up.
That is the moment most developers reach for a JSON to CSV converter. Then they find one that flattens everything into incomprehensible dot-notation or leaves nested data as raw JSON strings.
This tool flattens cleanly. It picks the right array. It shows you a live preview before you download.
Nested objects get flattened with dot notation
A JSON field like {"address": {"city": "Berlin"}} has no direct CSV equivalent. A CSV is flat. Every row has the same columns.
The standard solution is flattening. The nested key becomes a column named address.city. The value goes in that column.
Flattening handles multiple levels of nesting. {"user": {"profile": {"email": "..."}}} becomes user.profile.email.
If you would rather keep nested objects as raw JSON strings, turn off the flatten option. Each object goes in one cell.
Multiple arrays? Pick the one you want
Real API responses rarely return a single array. A typical response looks like {"data": [...], "meta": {...}, "errors": [...]}.
Most converters guess. They take the first array or the top-level one. That is often wrong.
This tool scans the entire JSON tree. It finds every array of objects and shows them in a dropdown.
You see the exact path for each. $.data. $.items. $.response.results. Pick the one you want.
The largest array is auto-selected by default. Your choice is remembered across reloads.
Invalid JSON? See the exact line.
A missing comma in a 500-line config file is nearly impossible to find by hand.
The tool parses the error message. It extracts the position. It converts that to a line and column number.
Then it shows you a code frame. Three lines of context. The error line highlighted. A caret pointing at the exact character.
You fix the error in seconds instead of minutes.
Excel BOM and regional delimiters
Excel on Windows has two quirks. First, it expects a UTF-8 CSV file to begin with a byte order mark. Without it, accented letters display as garbage.
Enable Excel BOM to prepend it. Your umlauts, accents, and emoji will display correctly.
Second, Excel uses the system's list separator. In most European locales, that is a semicolon, not a comma. Switch the delimiter before downloading.
The tool follows RFC 4180, the official CSV spec. Fields are quoted only when they contain the delimiter, a quote, or a line break. Internal quotes are doubled.
CSV to JSON in reverse
The second tab does the opposite conversion. Paste a CSV. Get a JSON array.
The first row becomes the header. Each subsequent row becomes a JSON object.
With type inference enabled, "42" becomes the number 42 and "true" becomes the boolean true. Turn it off if you want everything as strings.
The delimiter can be set manually or auto-detected. Auto-detect sniffs the header row and picks the right character. It handles comma, semicolon, tab, and pipe.
What this tool does not do
It does not stream very large files. Files above a few megabytes may slow down the browser tab.
It does not explode nested arrays into multiple rows. If an object contains an array of objects, that array is stored as a JSON string in one cell.
It does not infer deeply nested JSON schemas. It converts what is there. If your JSON is inconsistent, the columns will reflect that.
It also does not validate against a schema. It parses and converts.
Privacy and speed
Everything runs in your browser. Your JSON, your CSV, and your uploaded files never leave your device.
No uploads. No accounts. No ads inside the tool.
Your recent conversions and last-used settings are saved in localStorage on your device. Up to 5 items. Clear your browser data and they are gone.
Frequently Asked Questions
How do I convert JSON to CSV?
Can this tool handle nested JSON and multiple arrays?
{"address": {"city": "Berlin"}} becomes a column named address.city. If the JSON contains several arrays of objects, the Convert this array dropdown lists every path and lets you pick which one to turn into a table. The largest array is auto-selected by default.