JSON ↔ CSV Converter
Convert between JSON arrays and CSV format
Frequently Asked Questions
What are the typical use cases for JSON → CSV?
Exporting an API's JSON array to Excel/Google Sheets for analysis, handing data to a PM or marketing teammate, migrating to BI tools that do not speak JSON, and storing data as a portable backup. The reverse (CSV → JSON) is perfect for seeding test fixtures or feeding scripts.
What input shape does the tool expect?
Ideally an array of objects: `[{"name":"Alice","age":30}, {...}]`. Each object becomes a row and each key a column. Nested objects flatten to `parent.child`; nested arrays can be JSON-stringified or expanded into multiple rows.
Can I customize delimiters, quoting, and line endings?
Yes. Switch delimiter (comma / semicolon / tab), quoting policy (always / only when required), and line endings (LF / CRLF) to match Excel, PostgreSQL `COPY`, MySQL `LOAD DATA`, and other consumers.
Why does Excel show garbled characters for CJK content?
Excel opens CSV as Windows ANSI by default, so UTF-8 looks wrong. Toggle the "Include BOM" option on download, or rename the file to `.csv` and use Excel's "Import from Text" with UTF-8 selected.
Is my data uploaded?
No. The JSON source and generated CSV stay in your browser, so customer or business data is safe.
How is this different from Excel's own export?
Excel's CSV export varies with locale (delimiters, date formats), which can break cross-team workflows. DevToolkit's behavior is predictable and configurable — ideal for automation and reproducible handoffs.