JSON to CSV Converter

Real payloads are not flat

A converter that only accepts a top-level array of flat objects handles almost none of the JSON people actually have. Real responses arrive wrapped in an envelope, with the customer nested inside the order and the line items as an array. Turning that into a grid means making a decision about each of those shapes.

Finding the records

Responses usually hide the list you want under a key such as data, results or items, alongside metadata about paging. The longest array in the object is the payload, so an envelope works without you having to strip it first. A single object converts to a single row.

Nested objects become dotted columns

A customer object with a name and an email becomes customer.name and customer.email. The naming stays predictable at any depth, which matters because those column headers are what your next tool has to match on.

Arrays need a choice

A list of tags can be one cell with the values joined, one column per position, or the raw JSON kept as text. Joining reads best for a human, indexing keeps each value addressable, and JSON preserves everything when the array holds objects. There is no right default for every file, so it is a setting.