Skip to main content

JSON to CSV Converter

Convert JSON arrays and objects to CSV. Nested objects are automatically flattened with dot notation. Pick your delimiter, toggle the Excel-ready BOM, and download as .csv. Free, fast, and 100% browser-based — your data never leaves your machine.

0 chars | 0 lines

Ctrl + Enter to run

How to Convert JSON to CSV

  1. Paste your JSON — Any array, object, or nested structure. Upload a .json file or drag & drop one directly.
  2. Pick your delimiter — Comma (default), semicolon (for European Excel locales), tab (TSV), or pipe.
  3. Choose options — Toggle the header row, dot-notation flattening, UTF-8 BOM for Excel, CRLF line endings, always-quote mode, and array stringification.
  4. Click "Convert to CSV" — The tool flattens nested objects, escapes quotes and delimiters, and renders the result as both a styled table preview and the raw CSV source.
  5. Copy or download — Click Copy CSV to copy the raw CSV to your clipboard, or Download .csv to save the file.

About Our Free JSON to CSV Converter

JSON is the dominant data format for APIs, app config, and database exports — but for human-readable analysis, spreadsheet pivot tables, or one-off Excel reviews, CSV is still king. Converting between them sounds simple until you hit nested objects, mixed-shape arrays, or values containing commas and quotes. Our converter handles all the messy edge cases so the output Just Works:

  • Dot-notation flattening — Nested objects like {"user":{"name":"Jane","age":30}} become columns user.name and user.age. Works recursively to any depth.
  • Heterogeneous arrays — When array items have different keys, the converter takes the union of all keys as columns. Missing values become empty cells.
  • Configurable delimiter — Comma, semicolon (for European Excel), tab (TSV), pipe, or your own single character.
  • Excel-ready BOM — Optional UTF-8 byte-order-mark so Excel renders accents, currency, and CJK characters correctly.
  • Smart quoting — Cells with delimiters, quotes, or newlines are automatically wrapped in double quotes with internal quotes doubled per RFC 4180. Toggle "always quote" for downstream consumers that prefer fully-quoted CSV.
  • Configurable line endings — CRLF (Windows/Excel) or LF (Unix).
  • Array stringify mode — Array values inside cells become JSON strings (so the structure survives the round-trip) instead of being silently dropped.
  • Live table preview — See the result as a styled table AND the raw CSV source via the tab toggle.

100% browser-based — your data never leaves your machine. No file size limits beyond browser memory, no signup, no privacy concerns. Safe for API responses with tokens, internal exports, customer data, and anything else you wouldn't want passing through someone else's server.

Why Choose Our JSON to CSV Converter?

  • Privacy-first — Runs 100% in your browser. No upload, no server logs, no third-party API calls.
  • RFC 4180 compliant — Quote handling, escaping, and line endings match the standard so Excel, Google Sheets, Python pandas, R, and every other CSV consumer parses the output cleanly.
  • Real nested-object handling — Many free converters either fail on nested JSON or drop nested keys silently. Ours flattens predictably with dot notation.
  • Excel-ready out of the box — Tick the BOM and CRLF options and your file opens correctly in Excel without "this file appears to be corrupted" or mangled non-ASCII characters.
  • No ads, no signup, no tracking — Clean interface, no cookie banners.
  • Draft persistence — Your last input auto-saves in localStorage.
  • Keyboard-firstCtrl+Enter runs the conversion without lifting your hands off the keyboard.

When Should You Convert JSON to CSV?

  • API response → Excel analysis — Stakeholders want a spreadsheet, not a JSON dump. Convert and email the CSV.
  • Database export → BI tool — Many BI tools accept CSV but not JSON arrays. The flattened CSV imports cleanly.
  • MongoDB / NoSQL export → relational DB — Flatten nested documents into a CSV that a relational schema can ingest.
  • Survey/form responses — JSON from a form-builder API converted to CSV for analysis in Excel pivot tables.
  • E-commerce orders → bookkeeping — Take the order API response, convert to CSV, import to QuickBooks or a similar accounting tool.
  • Test fixtures → spreadsheets — Generate test data in JSON, export to CSV for QA spreadsheets.
  • Log analysis — Structured JSON logs converted to CSV for Excel filtering and chart building.
  • Quick data preview — JSON is hard to scan visually. The table preview here is sometimes all you need.

Frequently Asked Questions

How do I convert JSON to CSV online?
Paste your JSON (an array of objects, a single object, or nested data) into the input area, choose your delimiter and options, then click Convert to CSV. The tool flattens nested objects with dot notation, escapes quotes and delimiters, and produces a clean CSV ready to copy or download as a .csv file.
How does it handle nested JSON objects?
Nested objects are flattened using dot notation. For example {"user":{"name":"Jane","age":30}} produces columns user.name and user.age. This works recursively to any depth so you get a fully flat CSV that Excel and Google Sheets understand.
Is my JSON data sent to a server?
No. All conversion happens 100% in your browser using client-side JavaScript. Your JSON is never uploaded, never logged, and never stored anywhere except optionally in your own browser's localStorage as a draft. Safe for API responses, internal data, and proprietary content.
Can I use a custom delimiter (semicolon, tab)?
Yes. Choose comma (,), semicolon (;), tab (\t), or pipe (|). Semicolon is best for European Excel locales that use comma as the decimal separator. Tab produces TSV (tab-separated values), which pastes cleanly into spreadsheets without column-detection guesswork.
Does the CSV open correctly in Excel?
Enable the UTF-8 BOM for Excel option to prepend a byte-order-mark that signals Excel to read the file as UTF-8 — without it, Excel may mangle non-ASCII characters (accents, currency symbols, CJK). The BOM is invisible in modern editors and ignored by most CSV parsers. For maximum Excel compatibility, also enable CRLF line endings.
What's the file size limit?
No hard limit beyond your browser's available memory. The tool comfortably handles JSON files up to 10 MB (tens of thousands of rows). Larger files (50 MB+) work but may take a few seconds to flatten and render. All processing is local — no network round-trip.

Need a Custom Data Pipeline?

Our team builds reliable ETL pipelines, API integrations, and reporting dashboards that turn messy JSON into clean business insight.

Talk to an Engineer