JSON ⇄ CSV Converter

Bidirectional, in-browser conversion. Handles nested objects via dot-notation, custom delimiters, and RFC 4180 quote escaping. Nothing leaves your machine.

Input · JSON
Output · CSV

Options

316 input chars132 output charssample data

JSON and CSV are the two most common interchange formats for tabular data. APIs return JSON; spreadsheets and analytics pipelines speak CSV. The ToolEdge JSON ⇄ CSV Converter goes both directions in your browser: paste a JSON array of objects to get a CSV with auto-detected headers, or paste a CSV to get a JSON array back. The conversion is reversible — the result of `json → csv → json` round-trips cleanly for typical flat records.

Common pitfalls when converting between the two: CSV has no native types (everything is a string), no native nested structures (you have to flatten), and ambiguous quoting rules across tools. This converter handles all of that — it parses CSV with proper RFC 4180 quote handling via the Papaparse library, and flattens nested JSON via dot-notation (e.g., `user.email` becomes a column). Inputs and outputs stay in your browser; no upload, no server.

Common use cases

  • Exporting a JSON API response to a spreadsheet to share with non-technical teammates.
  • Loading CSV from a customer's data dump into a JSON-based pipeline (Postgres jsonb, MongoDB, ElasticSearch).
  • Quickly previewing what a CSV looks like as structured data — easier than opening in Excel.
  • Bulk-creating test fixtures: write rows in CSV, convert to JSON, paste into your test file.
  • Sanity-checking data shape before importing — does every row have the same fields? The JSON view makes inconsistencies obvious.

Frequently asked questions

It takes the union of keys across every object in your JSON array, sorted by first-occurrence order. Rows missing a key get an empty cell in that column. For nested objects, keys are flattened using dot notation: {"user":{"name":"Ada"}} becomes a column called user.name. Arrays are JSON-stringified into a single cell.