JSON to CSV Converter

JSON to CSV Converter: Turn API Data Into a Real Spreadsheet

JSON is how modern applications and APIs talk to each other, but it's not how most people read data. A response pulled from an API, an export from a database, or a config file full of nested objects and arrays is genuinely hard to scan by eye and impossible to sort, filter, or hand to a non-technical colleague as-is. CSV solves that: rows and columns that Excel, Google Sheets, and every reporting tool already know how to open. Converting once turns a wall of braces and brackets into something anyone on a team can actually work with.

Every converter on SmallStudyTools is tested with real files before it ships. This tool parses your JSON with the browser's own strict parser, so a file with a syntax error is rejected with a clear message rather than silently producing a broken CSV, and it correctly quotes any CSV field whose value contains a comma, quote, or line break.

1How This JSON to CSV Converter Works

The tool reads your file, parses it as JSON, and normalizes it into a list of records: an array of objects is used as-is, and a single JSON object is treated as one record. It then collects every key that appears across all of those records to build the full column set, so objects with slightly different shapes don't break the output, before writing each record out as a properly quoted CSV row.

2Simple vs Pro Mode

Simple Mode covers the everyday case: upload one JSON file and get back a clean, comma-separated CSV with a header row and nested objects already flattened, ready to open immediately. Pro Mode, currently free to use, hands over the delimiter, the flattening behavior, and the header row, plus bulk conversion for anyone processing a whole folder of exports at once.

3Flattening Nested Objects, Explained

JSON supports nesting objects inside other objects, which CSV has no native way to represent, since a spreadsheet cell can only hold one flat value. Flatten Nested Objects, on by default, solves this by turning a nested object like {"address":{"city":"Lahore","zip":"54000"}} into two separate columns, address.city and address.zip, so the data stays fully usable in a spreadsheet instead of collapsing into an unreadable blob of text. Turning flattening off keeps each nested object as a single JSON-text cell instead, which is occasionally useful if a downstream tool expects to re-parse that value as JSON later. A nested array is always written out as JSON text within its cell, in either mode, since a variable-length list doesn't have a clean columnar shape to flatten into.

4Common Reasons People Convert JSON to CSV

Most JSON to CSV conversions happen at the point where machine-readable data needs to become human-readable data. A response pulled from a REST API during testing, a config or settings export that needs a quick audit, or a batch of records coming out of a MongoDB-style database on their way into a reporting tool are all common starting points. Since almost every spreadsheet, BI tool, and reporting pipeline can open a CSV without any setup, converting once removes an entire category of "how do I even look at this" friction.

5Handling Inconsistent Keys Across Records

Real-world JSON is rarely perfectly uniform: one record might include a field another one omits entirely. This tool handles that by scanning every object in the file first and building the column set from the full union of keys it finds, rather than just the first record's shape. Any record missing a particular key simply gets an empty cell in that column, so the sheet stays properly aligned, no columns shift out of place, and no data silently disappears because one record happened to be missing a field.

6JSONL and NDJSON Files

A genuinely common point of confusion is JSONL, also called NDJSON, where each line of the file is its own separate JSON object rather than the whole file being one JSON array. Technically that's not valid JSON as a single document, so a file in that shape needs a small fix first: wrap the lines in square brackets and put commas between them to turn it into one proper array, then upload that. If you're generating JSONL output yourself and want it built correctly the first time, this site's CSV to JSON Converter can produce genuine newline-delimited JSON directly from a CSV, in the opposite direction from this tool.

7Choosing a Delimiter

Comma is the standard CSV delimiter and the safe default for opening a file in Excel or Google Sheets almost anywhere. Semicolon is worth switching to if the file is headed for a European locale where Excel treats the comma as a decimal separator instead of a field separator, which otherwise misreads a plain comma-delimited file. Tab-delimited output behaves like a TSV file and is a good choice when a value in the data is likely to contain commas itself, since a tab is far less likely to show up inside ordinary text.

8Frequently Asked Questions