JSON to CSV: Turning API Data Into a Readable Table
You have a JSON file full of useful data, but every time you open it you are staring at nested braces instead of rows and columns. Converting JSON to CSV solves that: it flattens structured API responses into a table you can sort, filter and chart in any spreadsheet app. This guide shows how the conversion actually works, where it breaks, and how to avoid the mistakes that turn a clean dataset into a mess of empty cells.
What JSON to CSV Conversion Actually Does
JSON stores data as nested objects and arrays. CSV stores it as flat rows separated by commas. Converting one to the other means deciding how each nested layer becomes a column.
A JSON object like {"id": 1, "name": "Ada"} maps cleanly. id becomes a column header, 1 becomes a cell value. The trouble starts when a value is itself an object or an array, because a CSV cell holds one value, not a tree.
Most converters handle this with dot notation. A nested field {"user": {"city": "Berlin"}} becomes a column called user.city. Arrays are trickier: {"tags": ["a", "b"]} might become tags with the value a;b, or it might be dropped entirely.
That is the core decision every JSON to CSV tool makes for you. Knowing which choice it made tells you whether your output is trustworthy.
Why the Structure Matters More Than the Tool
Two files can both be valid JSON and produce wildly different CSV output. A flat array of records converts perfectly. A deeply nested API response with objects inside arrays inside objects will lose detail unless you pick the right flattening depth.
Before you convert anything, open the raw JSON and ask three questions:
- Is the top level an array of records, or a single object wrapping one?
- Which fields are scalars, and which are nested?
- Do any arrays hold more than one item per record?
If the answer to the last question is yes, plan to handle it manually. No automatic converter guesses your intent.
Common JSON Shapes You Will Meet
API responses tend to fall into a few patterns. Recognising yours saves time.
The flat list. [{"id":1,"name":"Ada"},{"id":2,"name":"Grace"}]. This converts perfectly and needs no thought.
The wrapped list. {"data":[...],"meta":{...}}. The records live under a key. You need to point the converter at data, not the root.
The nested record. Each record contains sub-objects, such as an address or a set of dimensions. Flattening with dot notation usually works.
The record with arrays. Each record carries a list, such as order line items. This is where CSV struggles, because one row cannot cleanly hold a variable-length list.
How to Convert JSON to CSV in Five Steps
This workflow works with any browser-based JSON to CSV converter, including the ones in our full tool collection.
- Validate the JSON first. Paste it into a formatter and confirm it parses. A single trailing comma will break the conversion, and the error message rarely points at the real problem.
- Identify the record array. Find the path to the list of items you actually want as rows. If the data sits under
resultsordata, note that path. - Choose your flattening depth. Decide how many nested levels become columns. Two or three is usually enough. Deeper than that and your header row becomes unreadable.
- Set the delimiter and quote character. Comma is standard, but if your values contain commas, make sure the tool wraps those cells in quotes. Otherwise your columns shift and the file is quietly wrong.
- Open the result and check the row count. Compare the number of rows in the CSV against the number of records in the JSON. If they differ, something was dropped or split.
Step five is the one people skip. It is also the step that catches most silent data loss.
Can You Convert Nested JSON to CSV Without Losing Data?
Yes, but only up to a point. Flattening with dot notation preserves nested objects, and arrays of scalars can be joined into a single delimited cell. What you cannot preserve is a variable-length array of objects inside one record, because CSV has no way to represent that without either duplicating rows or cramming structured text into a cell.
For most reporting tasks, joining array values into one cell is the pragmatic answer. You keep every value and accept that the cell is no longer a single clean field. If you need true one-to-many relationships, a spreadsheet is the wrong output format.
Converting API Responses to CSV Tables
Most APIs return JSON, and most people who want a table are pulling a report. The browser-based tools on this site process everything locally, which matters when the response contains anything you would rather not upload.
A few habits make API data behave:
Request the same shape every time. Pagination often changes structure between pages. Pull one page, inspect it, then pull the rest.
Keep the raw response. Save the original JSON before converting. When a column looks wrong three days later, you will want the source.
Check the character encoding. Names and addresses with accented characters can arrive mangled if the encoding is assumed rather than declared.
Watch for null versus missing. A field that is null and a field that is absent are different things. Some converters render both as an empty cell, which hides the distinction.
Handling Large JSON Files in the Browser
Browser-based conversion has a real ceiling. A file of a few megabytes converts quickly. A file of several hundred megabytes will exhaust memory in a tab, and the page may crash before it finishes.
If you hit that wall, the honest answer is that a browser tool is not the right instrument. Split the JSON into smaller chunks first, or use a command-line utility designed for streaming. Our tools are built for the common case, not for bulk data engineering.
There is also a practical limit on nesting. Beyond roughly five levels of flattening, the generated column names become so long and so repetitive that the resulting table is harder to read than the original JSON.
JSON to CSV for Spreadsheet Analysis
Once the data is in a table, the real work starts. Sorting, filtering and pivot tables all need consistent column types, and JSON does not guarantee them.
Numbers may arrive as strings. Dates may arrive in several formats within the same file. Booleans may appear as true, "true" or 1. None of this is a conversion bug; it reflects how the source data was written.
Clean these after conversion, not before. A spreadsheet's find-and-replace and column-format tools are faster than editing JSON by hand.
Convert first, clean second. Fixing types inside JSON is slow and error-prone; fixing them in a table is a few clicks.
Frequently Asked Questions
What is the difference between JSON and CSV?
JSON is a hierarchical format that supports nested objects and arrays. CSV is a flat, row-based format where every record has the same columns. JSON suits data exchange between systems; CSV suits spreadsheets and reporting. Converting between them means flattening the hierarchy, which is why some structure is always lost.
Can I convert JSON to CSV without installing software?
Yes. Browser-based converters run entirely on your device and require no installation or account. You paste or upload the JSON, choose your options, and download the CSV. Because processing happens locally, your data is not transmitted to a server, which is useful for anything sensitive.
Why does my CSV have empty columns?
Empty columns usually mean the converter found keys that appear in only some records. JSON does not require every record to share the same fields, so the union of all keys becomes the header row. Records missing a key get an empty cell. This is expected behaviour, not a bug.
How do I handle arrays inside my JSON records?
Join the array values into a single delimited cell, or expand each array item into its own row. The first option keeps one row per record but makes the cell harder to filter. The second option is cleaner for analysis but changes your row count, so verify it against the original.
Is there a size limit for browser conversion?
It depends on your device and browser. Small and medium files convert without trouble. Very large files can exhaust available memory and crash the tab. If that happens, split the source into smaller pieces or use a dedicated command-line tool.
The Payoff: Readable Data You Can Actually Use
Converting JSON to CSV turns an API response into something you can sort, chart and share. The process is straightforward once you know which fields are nested and how your converter handles arrays. Validate the source, pick a sensible flattening depth, and always check the row count against the original. Do that, and JSON to CSV becomes a routine step rather than a debugging session.