DevPik Logo

JSON to CSV Converter Online

Convert JSON arrays to CSV with nested-object flattening (dot-notation columns), configurable delimiters (comma, semicolon, tab, pipe), and one-click download — safe for Excel, Google Sheets, and bulk imports.

Built and maintained by Muhammad Tayyab — Founder, DevPik.

Why Use JSON to CSV Converter Online?

Marketing, ops, and finance teams live in spreadsheets — and the data they need often lives in JSON-returning APIs. Piping JSON through a converter that preserves structure (flattening nested objects with dot-notation columns) is faster than writing a one-off Python script every time a stakeholder wants to open a report in Excel. The tool also handles the awkward edges: arrays within values become semicolon-joined strings, nulls become empty cells, and regional delimiters (semicolon for EU, tab for Excel imports) are one click away. Useful when exporting Stripe customer lists, Google Analytics reports, or a JSON dump from a MongoDB collection.

How to Use JSON to CSV Converter Online

  1. Paste your JSON array into the input area or upload a .json file using the Upload button.
  2. The tool automatically converts your JSON to CSV in real-time as you type or paste.
  3. Adjust options: choose a delimiter (comma, semicolon, tab, pipe), toggle headers, or enable nested object flattening.
  4. Copy the CSV output to your clipboard or download it as a .csv file.
  5. Use the Swap button to switch to CSV to JSON conversion mode.

Worked Examples

Basic flat array of records

Input
[{"name":"Jane","email":"j@x.com"},{"name":"Bob","email":"b@x.com"}]
Output
name,email
Jane,j@x.com
Bob,b@x.com

Headers auto-derived from the first object's keys.

Flatten nested address objects

Input
[{"name":"Jane","address":{"city":"NYC","zip":"10001"}}]
Output
name,address.city,address.zip
Jane,NYC,10001

Dot-notation preserves hierarchy in a flat CSV format Excel can read.

European delimiter for spreadsheets

Input
Same JSON, delimiter set to `;`
Output
name;email
Jane;j@x.com

Excel on non-English systems treats comma as a decimal separator — semicolon avoids ambiguous imports.

About JSON to CSV Converter Online

Spreadsheets are where analysts, marketers, and finance teams live, but the data they need increasingly comes from JSON-returning APIs, Stripe exports, or MongoDB dumps. The JSON to CSV converter bridges that gap without a one-off Python script: paste a JSON array or upload a .json file, and it converts to CSV in real time. Nested objects are flattened into dot-notation columns (address.city becomes its own column), so no structure is silently dropped. You can choose the delimiter, comma, semicolon, tab, or pipe, which matters more than people expect: European locales use semicolons because commas are decimal separators, and tab-separated output imports cleanly into Excel. Toggle the header row, then copy the result or download it as a .csv file ready for Excel or Google Sheets. This tool is built for data analysts, operations teams, marketers pulling API reports, and developers who need to hand structured data to non-engineers. A few practical notes. Arrays inside values are joined into a single cell with semicolons so rows stay aligned, and null values become empty cells. Records do not need identical keys: the converter unions all keys across the array and leaves blanks where a record lacks a field, which is exactly what you want with ragged API responses. Values containing commas, quotes, or newlines are quoted per RFC 4180 so they survive the round trip through Excel and Sheets. If Excel garbles accented characters on open, that is an encoding issue rather than a data issue: open the file with UTF-8 encoding or import it through Excel's Text Import wizard instead of double-clicking. For JSON Lines files (one object per line, common in logs and ML datasets), make sure the input is a proper JSON array; many tools emit JSONL, and wrapping it in brackets is not enough, each line must be comma-joined into an array.

Troubleshooting & Common Issues

Excel shows all data in one column

Excel's import treats comma as the delimiter only on English locales. On German/Spanish Excel, switch the converter's delimiter to semicolon, or use Excel's Data → Import wizard and specify the separator manually.

Commas inside a string value break the CSV layout

The converter automatically quotes any cell that contains the delimiter, a newline, or a double quote — per RFC 4180. If you see broken layout, check that your importing application also respects RFC 4180 quoting.

Arrays flattened to `1,2,3` conflict with CSV commas

Inner arrays are joined with semicolons by default to avoid colliding with the outer delimiter. Change the join character in settings if your downstream tool expects a different separator (pipes work well for data that might already contain semicolons).

Some rows have missing keys — empty cells appear

The converter collects the union of all keys across every row, so rows missing a field get empty cells for that column. This is correct CSV behavior. If you need a "default value" instead of empty, pre-process your JSON to fill in the blanks.

Frequently Asked Questions

What happens to nested objects in my JSON?

They are flattened into dot-notation columns, so {"address": {"city": "Paris"}} becomes a column named address.city. Nothing is dropped silently. Nested arrays inside values are joined into one cell with semicolons to keep rows aligned.

My records have different fields. Does that break the conversion?

No. The converter unions all keys across every record into the header row and leaves empty cells where a record lacks a field. This handles ragged API responses cleanly without you pre-normalizing anything.

Which delimiter should I choose for Excel?

Use comma for US/UK locales and Google Sheets. Use semicolon for most European locales, where the comma is the decimal separator and Excel expects semicolons. Tab-separated values also import reliably into Excel via the Text Import wizard.

Why does Excel show garbled characters for accents?

Excel sometimes opens UTF-8 CSVs as a legacy encoding when you double-click them. Fix it by importing through Data > From Text/CSV and choosing UTF-8, or open the file in Google Sheets, which detects UTF-8 automatically.

Can I convert a JSON object, not an array?

CSV is inherently tabular, so the input should be an array of objects. A single object is treated as one row. If you have nested arrays you want as rows, point the converter at the array path or reshape the data so the array is the top level.

Is my data uploaded anywhere?

No. Conversion runs entirely in your browser, which makes it safe for customer lists, internal IDs, and other data you would not paste into a server-side tool.

Guides & Further Reading

Related Tools

Was this tool helpful?