Why convert JSON
JSON is the data language of apps and websites: API responses, app exports, product catalogues, form submissions and settings are often JSON. It is easy for programs but hard for people to read. Excel lets anyone sort, filter, chart and check the data.
What happens when you convert
If the JSON is a list of records, each record becomes a row and each field becomes a column. Nested objects are flattened into columns with dotted names, such as address.city. If the top level is an object, every list of records inside it gets its own sheet, and the remaining single values are listed on an Info sheet. Simple lists of values are joined with commas in one cell.
Numbers, text and accuracy
JSON numbers become real Excel numbers you can calculate with, while text values — including IDs written as text — stay text, so leading zeros are kept. Very complex nested lists inside records are kept as JSON text in a cell so no data is lost.
Common problems and how to fix them
“Not valid JSON”: the message shows where the problem is — usually a missing comma, an extra comma or wrong quotes. Too many columns: deeply nested data creates many columns; hide those you do not need. Very large numbers lose digits in Excel: Excel stores only 15 significant digits — keep such IDs as text in the source.
Good habits
Format the JSON first with Format JSON if you want to inspect it, keep the original file, and document which sheet holds which data.