JSON to CSV
Convert JSON array data to CSV (comma-separated values). Open in Excel or Google Sheets.
Why convert JSON to CSV?
JSON is the standard for APIs and web apps, but spreadsheet tools like Excel and Google Sheets work natively with CSV. Converting JSON to CSV is essential when: exporting API data to Excel for analysis, downloading user/customer data from web applications, generating reports for non-technical stakeholders, bulk-importing into databases that prefer CSV, or simply needing tabular view of JSON data. This converter handles arrays of objects (most common JSON format) and flattens them into tabular CSV with column headers from JSON keys. Supports custom delimiters and quote handling – works with all major spreadsheet tools.
How to use this tool
- Paste JSON — An array of objects (most common). Single object also works (gets wrapped in array).
- Choose delimiter — Comma (standard CSV), semicolon (European Excel), or tab (TSV).
- Choose quote handling — Always quote strings (safe for all values), or only when needed (cleaner output).
- Copy or download .csv — Result opens in Excel, Google Sheets, or any CSV-aware tool.
JSON to CSV mapping
Input JSON (array of objects):
[
{"name":"Alice","age":30,"city":"Mumbai"},
{"name":"Bob","age":25,"city":"Delhi"}
]Output CSV:
name,age,city Alice,30,Mumbai Bob,25,Delhi
Conversion rules:
- JSON keys become CSV column headers (first row)
- Each JSON object becomes one CSV row
- If different objects have different keys, all unique keys become columns (missing values = empty)
- Nested objects/arrays get stringified into single cell (consider flattening first)
- Numbers, booleans, null preserved as-is
Examples
- API response with user list: Convert to CSV for HR import or Excel analysis
- E-commerce product catalog: JSON inventory → CSV for bulk upload to Amazon, Shopify
- Analytics events log: JSON event stream → CSV for data warehouse
- Survey response data: JSON from form tool → CSV for statistical software (R, SPSS)
- Database export: NoSQL JSON dump → CSV for legacy systems
Tips & best practices
- Use semicolon delimiter for European Excel (where comma is decimal separator)
- For nested JSON, flatten first using a library (lodash flatten) or post-process – CSV is flat by nature
- Always-quote option is safer if your data contains commas, quotes, or newlines
- Add UTF-8 BOM to CSV if non-ASCII characters – Excel sometimes misinterprets without it
- Large JSON arrays may slow browser – for big datasets, server-side conversion is better
- Save CSV with explicit .csv extension for Excel/Sheets auto-recognition
Limitations & notes
Nested objects in JSON become stringified single cells – not truly tabular. For deeply nested JSON, flatten first or use specialized ETL tools. Date strings stay as strings – no Excel date conversion. Numbers preserve as text in some Excel imports – format columns as number afterward if needed.
Frequently Asked Questions
What if my objects have different keys?
The tool collects all unique keys across all objects to make a complete column set. Missing values in any row become empty cells. Common in APIs where some records have optional fields.
How are nested objects handled?
Stringified as JSON within a single cell – not ideal but preserves data. For true tabular output, flatten the JSON first using JavaScript or pandas (Python).
Can I customize column order?
Not directly – the tool uses the order keys appear in your JSON. To control order, restructure your JSON or post-process CSV manually.
Why does Excel show my numbers as text?
Excel sometimes reads CSV numbers as text if they’re not properly formatted. Workaround: open Excel first, then Data → From Text/CSV → choose column type (Number) during import.
What about Excel-compatible BOM?
For Excel to correctly read UTF-8 special characters (non-English text), the file should have a BOM (Byte Order Mark) at start. This tool currently doesn’t add BOM – manually prepend the bytes EF BB BF if needed for international data.
Can I convert CSV back to JSON?
Yes – use our CSV to JSON tool. Round-trip works for flat data but nested structures lost in CSV cannot be recovered.
What’s the max JSON size?
Browser memory dependent. Files under 50 MB work smoothly. Larger files may slow or freeze – use server-side tools or pandas for big data.
