JSON to CSV Converter
Clean Tables From Messy Data

Jobs This JSON to CSV Converter Handles for You

This JSON to CSV converter turns the data an app or an API gives you into rows and columns a spreadsheet can open. Paste the JSON, and the table appears beside it. There is no upload, because your browser does all the work.

JSON is great for programs. It nests things inside other things, and it lets each record carry different fields. A spreadsheet, however, wants one flat grid. So the real job is not the format change itself. The real job is deciding what to do with nested objects, lists and missing fields, and then telling you what was decided.

That is why every conversion ends with a checks table. It names the records it found, the objects it flattened, the cells it left empty and anything that looked risky. As a result, you know the file is right before you send it to anyone.

How Denwix Turns Nested JSON Into Dotted Column Names

Each spreadsheet cell can store only a single value. So when a record has an address object inside it, the converter gives each part its own column: address.city, address.country and so on. The dotted names show exactly where each value came from.

Lists work differently. A list of tags or item names goes into one cell, joined with a semicolon. If you would rather keep the list as JSON text, switch the option off. Either way, nothing is dropped.

Turn JSON Into CSV and Keep Every Field

Many converters read JSON with the browser’s built-in parser, and that parser rounds long numbers. An order ID such as 12345678901234567890 comes back as 12345678901234567000, which is a different order. This tool reads every number as the exact text you pasted, so IDs and account numbers stay whole.

Records rarely match perfectly, either. One customer has a phone number, and the next one does not. The converter collects every field it meets, in the order it meets them, and leaves a cell empty where a record has no value. The checks table then counts those empty cells for you.

How the Converter Finds Your Records

API responses often wrap the list you want inside another object, for example { "data": [ ... ] } or { "results": [ ... ] }. When there is exactly one list of objects inside, the converter uses it and says so. One object gives you one row, while an array of arrays maps straight onto rows.

The rules for JSON itself live in RFC 8259. If the reader finds a mistake, such as a trailing comma or a missing quote, it names the line and column. Then a button takes you straight to the spot.

JSON to Excel Without Broken Characters

Excel is picky about text files. Unless a CSV starts with a small marker called a byte order mark, Excel may guess the wrong encoding. Then names such as Zoë or Karachi in Urdu script turn into gibberish. Tick Excel-ready download, and the file carries that marker, so it opens correctly with a double click.

Semicolons or tabs are available as separators too. Some regions use a comma as the decimal point, so their Excel versions expect semicolons between columns. Pick semicolon, tab or pipe, and the preview updates at once.

Protection Against Spreadsheet Formulas

A cell that starts with =, +, - or @ can run as a formula when the file opens. Attackers hide commands this way, and OWASP calls it CSV injection. With the formula guard on, such cells get a leading apostrophe, so they open as plain text. Negative numbers are left alone, and the checks table lists every cell it changed.

Quotes, Commas and Line Breaks Handled

CSV has one rule that trips up hand-made files: a value containing the delimiter, a quote or a line break must sit inside double quotes. Furthermore, any quote inside it must be doubled. The converter follows RFC 4180 exactly, so a name such as Sara "Sam" Malik or an address with a comma survives the trip.

Before you import the file somewhere important, you can compare it with an older export. Our diff checker shows every changed line side by side.

Who Needs JSON Data in a Spreadsheet

Plenty of people who never write code still receive JSON. A shop owner exports orders from a store plugin. A marketer downloads leads from a form service. A support lead pulls tickets from a help desk. In each case the data arrives as messy JSON, but the report has to live in a clean sheet.

Developers use it too. For example, a quick CSV makes it easy to check an API response by eye, sort it or hand it to a colleague. Meanwhile, analysts load the file into Google Sheets or a database import screen. The steps stay the same for everyone: paste, read the checks, then download.