About this tool
Turning an API response into CSV makes it easy to review in a spreadsheet, attach to a bug report or feed into a data-driven test. This converter takes an array of objects (or a single object), flattens nested objects into dot-notation columns such as address.city, and builds the header from the union of keys across all rows, so a field that only appears in some records still gets a column. Fields containing the delimiter, quotes or line breaks are quoted and escaped as RFC 4180 requires.
How to use it
- Paste a JSON array of objects, or click “Load sample”.
- Pick the delimiter, and choose whether arrays become indexed columns (roles.0, roles.1) or a single JSON-encoded cell.
- Keep CRLF line endings for Excel and RFC 4180, or switch to LF for Unix tools.
- Copy the CSV or download it as data.csv.
JSON to CSV Converter FAQ
How are nested objects and arrays handled?
Objects are flattened with dots: {"address":{"city":"Boston"}} becomes an address.city column. Arrays become roles.0, roles.1 and so on, or one cell containing the JSON array if you choose that option. Empty objects and arrays are written as {} and [] so you can tell them apart from missing values.
What happens to null and missing fields?
Both become empty cells. If you need to distinguish them in a test, keep the data in JSON or add an explicit marker before converting.
Will the CSV open correctly in Excel?
Use the comma (or semicolon in locales with a decimal comma) and CRLF endings. Long numeric IDs may still be displayed in scientific notation by Excel; that is a display setting in Excel, not a problem with the file.