JSON Formatter
Paste JSON and format it, shrink it, or check it for errors, with the exact line of the problem.
Open tool →Paste a JSON array of objects and get a clean CSV file in seconds. Copy the result or download it, ready to open in Excel or Google Sheets.
Last updated: 17 November 2026.
Everything runs in your browser. Your JSON is never uploaded, sent, or stored.
JSON, short for JavaScript Object Notation, is the format most apps and APIs use to send data around. It stores records as objects with named fields, which is great for software but hard to read in a spreadsheet. CSV, short for comma separated values, stores the same records as rows in a plain text table, with one record per line and one field per column. Converting JSON to CSV means taking each object and turning it into a row, with the field names becoming the column headings at the top. The data stays the same, only the shape changes.
This matters because spreadsheets are where most people actually look at data. A developer can read JSON in a text editor, but a shop owner, a teacher, or a researcher usually wants columns they can sort, filter, and total. A CSV file opens in almost every spreadsheet app without extra steps, and it is easy to share by email or upload to another system.
One common case is an API response. Many web services send data as JSON, and when you need to hand that data to a colleague or a client, a spreadsheet is far easier to explain than a block of code. Survey or form results are another case: turned into a CSV, each answer becomes a row you can sort by date, filter by score, or chart in a few clicks. Product lists, customer records, and analytics exports follow the same pattern.
CSV is also the bridge between tools that do not talk to each other. A shop system might export orders as JSON while the accounting software only accepts CSV. Instead of retyping hundreds of rows, you convert the file once and import it. The same trick works for moving a mailing list into an email tool, or for giving a data set to someone who only works with spreadsheets.
Start by pasting your JSON into the top box. It should be an array of objects, which means it starts with a square bracket and each record sits inside curly braces. A single object is also accepted and treated as one row. Then pick a delimiter, which is the character that separates the columns. A comma is the standard choice and works with Excel and Google Sheets. Pick a semicolon if your data uses commas inside numbers, or if your spreadsheet app expects it, and pick a tab for tools that prefer tab separated values.
Press Convert to CSV and the result appears in the output box, with the field names as the first row. The counters above show how many rows and columns were found, so you can check at a glance that nothing went missing. Press Copy CSV to copy the result, or Download .csv to save it as a file you can open straight away. The Load sample button fills in a small example, and Clear empties both boxes. Nothing you paste leaves your browser at any point.
Real JSON is rarely perfectly flat. A record might contain a nested object, such as an address or a list of tags. This converter keeps those values safe by writing them as compact JSON text inside a single cell, so the information is kept and the row stays intact. Numbers stay as numbers, true and false stay as they are, and empty fields become empty cells. If one record has a field that others do not, that field still gets its own column, and the records without it leave that cell blank.
Special characters are handled the same careful way. If a value contains a comma, a quote, or a line break, the whole value is wrapped in double quotes, and any quote inside it is doubled. This follows the usual CSV rules, so spreadsheet apps read the value as one cell instead of splitting it in the wrong place. That is why a name like "Large, Red Shirt" stays in a single column, and a multi line address does not break your rows apart.
The most common error is invalid JSON. A trailing comma after the last item, single quotes instead of double quotes, or a missing bracket will all stop the conversion, and the tool will show the exact error message from the parser so you can find the problem. If your data came from an API, check that you copied the whole response and not just part of it. If you wrote it by hand, a quick check with the JSON formatter can point to the faulty line.
Another common surprise is a top level value that is not an array. A single object works, because the tool wraps it as one row, but a bare string or number has no fields to turn into columns, so the tool will ask for an array of objects instead. An empty array also has nothing to convert, so it shows a clear message rather than a blank file. If the CSV opens oddly in Excel, try the import wizard and pick UTF-8 encoding, which keeps special characters and non English text intact. For data in a different structured format, the XML formatter can tidy it first.
It accepts a JSON array of objects, such as [{"name":"Ali","age":30}]. Each object becomes one row in the CSV, and the field names become the column headings. A single object on its own is also accepted and becomes one row.
Every unique key across all records gets its own column, in the order the keys first appear. If a record does not have a value for a column, that cell is left blank, so no rows shift out of place.
Values that contain a comma, a quote, or a line break are wrapped in double quotes, and any quote inside the value is doubled. This follows the standard CSV rules, so Excel and Google Sheets read the value as a single cell.
Yes. Paste the object on its own and the converter treats it as one row. A bare string, number, or empty array cannot be converted, because there are no fields to turn into columns.
No. The conversion runs fully in your browser with plain JavaScript. Your JSON is never uploaded, never sent to a server, and never stored. You can close the page and nothing remains.