Convert JSON to CSV

Your data lives in JSON — an API response, an export, a config — but your spreadsheet, database import or reporting tool wants CSV. Convert JSON to CSV bridges the gap: feed it a JSON array of objects and get a clean, header-prefixed table ready for Excel, Google Sheets or a data pipeline.

Object keys become the columns, each object becomes a row, and nested objects are flattened with dot notation so nothing is lost. Choose a comma, tab or semicolon delimiter, toggle the header row, and copy the result or download it as a .csv file. All conversion happens locally in your browser.

• Array of objects in, table out: each object becomes a row, keys become columns.
• Nested flattening: nested objects become dotted columns such as address.city.
• Delimiter choice: comma, tab or semicolon for maximum compatibility.
• Header row control: emit or omit the header as your import tool requires.
• Safe quoting: values containing the delimiter, quotes or newlines are quoted and escaped correctly.
• Copy or download: grab the CSV or save it as a .csv file.
• Private by design: all processing happens locally in your browser.

1. Paste a JSON array of objects or open a .json file.
2. Choose the delimiter — comma, tab or semicolon.
3. Decide on the header row — on by default.
4. Copy or download the resulting table.

Example 1 — Spreadsheet import. Convert an API response to CSV and import it into Excel or Google Sheets without retyping a single field.

Example 2 — Data pipeline handoff. Your ETL stage emits JSON; the next stage expects CSV. Convert inline and keep the pipeline moving.

Example 3 — Reporting. Flatten a nested product or customer export into tabular rows your analytics tool can ingest.

• Instant tabulation — JSON records become spreadsheet rows in one click.
• Nothing lost — nested data is flattened, not dropped.
• Format-compatible — comma, tab or semicolon output.
• Import-ready — quoting follows CSV rules for any consumer.
• Free and private — runs locally, no uploads.