JSON to CSV Converter
Turn JSON into a spreadsheet. Nested objects are flattened into readable columns, the right array is found for you, and the whole conversion happens inside your browser.
JSON
Your table will appear here.
What you can do
- Get an API export into Excel. Paste the response, pick the array, download a file that opens cleanly.
- Flatten nested data. Objects inside objects become readable dot-path columns instead of unreadable JSON blobs.
- Handle ragged records. Objects with different keys still line up, with empty cells where a value is missing.
- Avoid the encoding trap. The UTF-8 BOM means names with accents survive the trip into Excel.
- Catch dangerous cells. Formula-triggering values are counted and can be neutralised before anyone opens the file.
Why CSV is still worth the trouble
JSON is the right shape for machines and the wrong shape for a finance team. CSV is the one format every spreadsheet, database loader and accounting package will accept without an integration, which is why “can you send it as a spreadsheet?” outlives every API. The awkward part is the mismatch: JSON nests, CSV is flat. That translation is what this tool is for.
Frequently asked questions
Is my JSON uploaded to a server?
No. The conversion runs entirely in your browser, so the data never leaves your machine. That matters here more than for most converters, because the JSON people need to turn into a spreadsheet is usually an API export full of customer names, emails and order values.
How are nested objects handled?
They are flattened into dot-path columns, so a contact object with an email inside it becomes a contact.email column. Lists of simple values are joined into a single cell, and lists of objects are indexed. Switch flattening off and each nested value is written as raw JSON in one cell instead.
My array is buried inside a wrapper object. Does that work?
Yes. Most API responses look like {"page": 1, "results": [...]}, and converting the outer object would give you one useless row. The tool finds every array in the document, picks the largest one whose entries are objects, and lets you switch to a different one from the "Rows from" menu.
Why do my accented characters look wrong in Excel?
Excel assumes a CSV is in your system’s legacy encoding unless the file starts with a UTF-8 byte order mark. The "Excel BOM" option adds one, which is why it is on by default. Turn it off if you are feeding the file to a script or database loader, where the extra bytes can confuse the first column name.
What is the formula warning about?
A spreadsheet treats any cell beginning with =, +, - or @ as a formula. If the JSON came from somewhere you do not control, that is a way to make Excel run something the moment your colleague opens the file — a real attack known as CSV injection. The tool counts those cells and offers to prefix them with an apostrophe so they stay as text. Most converters do not check at all.
Which separator should I choose?
Comma is the default and what nearly every tool expects. Choose semicolon if you are opening the file in Excel on a machine set to a European locale, where a comma is the decimal separator and a comma-separated file lands entirely in one column. Tab is the safest choice when the data itself is full of punctuation.
What if my objects do not all have the same keys?
The column list is the union of every key seen, in the order they first appear, and any row missing a key gets an empty cell. Nothing is dropped, so a partial record stays visible rather than silently shrinking the table.
Still moving data by hand?
If someone on your team exports, converts and re-uploads the same file every week, that is an integration waiting to be built. AgileTechForge builds them.
Talk to our team