JSON to CSV Converter

JSON to CSV Converter turns a JSON array of objects into a properly formatted CSV file that opens cleanly in Excel, Google Sheets, or any spreadsheet tool. It automatically detects every unique key across your objects to build the column headers, aligns rows even when some objects are missing certain keys, and applies correct CSV quoting for values containing commas, quotes, or line breaks.

This is the format developers reach for when exporting an API response, a database query result, or any list of records into something a non-technical teammate can open directly in a spreadsheet.

• Automatic column detection: Every unique key across your JSON objects becomes a column, in the order first encountered.
• Handles sparse and nested data: Missing keys become empty cells; nested objects and arrays are safely stringified rather than dropped.
• RFC 4180 quoting: Commas, quotes, and line breaks inside values are escaped correctly so the file opens cleanly in any spreadsheet app.
• Instant, in-browser conversion: No upload, no server round trip, no account.
• Copy or download: Grab the CSV text directly or download it as a .csv file.

1. Paste a JSON array of objects into the input box, or click "Load Sample" to see an example.
2. Click Convert to generate the CSV output.
3. Review the columns — every unique key across your objects becomes a header.
4. Copy the CSV or download it as a .csv file to open in Excel or Google Sheets.

Example 1: A JSON array of three user records with name, email, and role fields converts to a four-line CSV — one header row and three data rows — ready to open directly in Excel.

Example 2: A product export where some items have a "discount" field and others do not still produces a clean, aligned CSV, with an empty cell in the discount column for products that lack that field.

• Spreadsheet-ready exports: Turn an API response or database export into something non-technical teammates can open directly.
• No column mismatches: Automatic key detection keeps every row aligned even with inconsistent objects.
• Safe for messy data: Proper quoting prevents commas or quotes in your data from breaking the file structure.
• 100% private: Nothing is uploaded — conversion runs locally in your browser.