JSON to CSV
Convert JSON data to CSV format.
Converting JSON to CSV: Complete guide
JSON (JavaScript Object Notation) and CSV (Comma-Separated Values) are two of the most widely used formats for storing and transporting data. While JSON is ideal for nested data and web APIs, CSV is the preferred format for spreadsheets, data analysis, and tools like Excel, Google Sheets, Pandas, and R. Converting between both formats is a common task in data science and backend development.
JSON to CSV conversion transforms each object in the JSON array into a row, and each object key into a column. Nested values are automatically flattened, and missing fields in some objects are filled with empty values to maintain a consistent tabular structure.
Practical use cases
Exporting API data: REST APIs return JSON, but data analysts prefer CSV for working in Excel or Google Sheets. This tool bridges that gap instantly.
Database migration: When exporting data from MongoDB (native JSON) to import into PostgreSQL or MySQL, CSV is the standard intermediate format.
Reports and dashboards: Generate CSVs from JSON API responses to feed dashboards in BI tools like Tableau, Power BI, or Google Data Studio.
Frequently asked questions
What happens with nested data?
Nested objects are flattened using dot notation. For example, {"user": {"name": "Anna"}} becomes a "user.name" column. Nested arrays are serialized as JSON strings within the corresponding cell.
Does the CSV use commas or semicolons?
The CSV standard uses commas as separators. However, in countries where the comma is the decimal separator, Excel expects semicolons. This tool generates standard comma-separated CSV.
How are quotes and commas within values handled?
Values containing commas, line breaks, or quotes are automatically enclosed in double quotes. Quotes within the value are escaped by doubling them, following the RFC 4180 standard.
Can I convert JSON with arrays of different structures?
Yes. The tool detects all unique keys across all objects and creates columns for each one. Objects that don't have a specific key will have that cell empty in the resulting CSV.
JSON vs CSV: When to use each
| Feature | JSON | CSV |
|---|---|---|
| Nested data | Native | Requires flattening |
| Size | Larger (more verbose) | Smaller (compact) |
| Spreadsheets | Not compatible | Native |
| Web APIs | Standard | Not used |