JSON to CSV in Excel: Fix “Excel Won’t Open My JSON File”

If you have ever double‑clicked a .json file and watched Excel shrug—or open a wall of raw text—you are not doing anything wrong. Spreadsheets and JSON both hold “data,” but they speak different languages. This guide explains why Excel feels awkward with JSON files, what is actually going wrong under the hood, and a reliable path to get the same information into Excel as CSV or XLSX so you can sort, filter, and pivot without fighting the file format.

What Excel expects vs. what JSON delivers

Excel’s grid is built around rectangular tables: rows and columns where each cell is mostly flat text or a number. You can think of a clean CSV as Excel’s native “simple” cousin—predictable, row‑by‑row, easy to import.

JSON (JavaScript Object Notation) is different. It is a flexible way to describe structured data for programs: objects with named fields, lists inside lists, nested records, and optional values. That flexibility is why APIs and web apps love JSON—but the same structure is not automatically a single table.

So when people say “Excel won’t open my JSON file,” the failure is usually one of these realities:

• Excel is not a generic JSON editor. Depending on your version and path (double‑click vs. import), Excel may try to treat the file as text, refuse the format, or import only part of the structure.
• Your JSON may not be “one table.” Nested objects and arrays map poorly to one rectangle without flattening rules.
• Large or “pretty‑printed” JSON can be painful in a spreadsheet UI even when it opens, because you still do not have a clean column layout.

In other words: JSON is not “broken,” and Excel is not “wrong”—they are optimized for different jobs.

What about Excel’s built‑in JSON import?

Modern Excel can import JSON through features like Get Data (Power Query), and for some files that works well—especially when JSON is already close to a table (for example, a top‑level array of objects with mostly flat fields). Many teams successfully use this path.

Where teams still struggle is the messy middle: exports where nested objects repeat, where arrays should become multiple rows, or where field names change between API versions. Power Query can handle a lot, but you are still doing data modeling inside Excel—often repeat work, often brittle when the export changes next month.

That is why a dedicated preview → column edit → export step still wins for repeatable business exports: you decide what “flat” means before Excel ever sees the file, and you get a CSV/XLSX that opens predictably for everyone on the team—not only people comfortable with query editors.

Common ways this shows up in real work

Here are the patterns we hear most often from analysts, ecommerce operators, and developers:

• Double‑clicking a .json export opens in Notepad, VS Code, or a browser—not in Excel as a tidy sheet.
• “Get Data” import feels confusing because the preview shows nested fields, and you are not sure which level should become rows.
• API responses saved as JSON contain an array of objects (great!) but also nested objects (shipping address, line items, metadata) that do not fit one row without decisions.
• Teams share a JSON file expecting a spreadsheet, and non‑technical teammates get stuck before they even analyze anything.

The underlying issue is almost always structure, not the characters in the file. Once you translate JSON into a stable table model—rows and columns you agree on—Excel becomes the friendly tool you expect.

The reliable fix: convert JSON to CSV or XLSX first

For most workflows, the fastest win is to stop asking Excel to “be” your JSON parser. Instead, convert JSON into:

• CSV when you want maximum compatibility, smaller files, and easy sharing.
• XLSX when you want a workbook file with formatting, multiple sheets later, or a more “finished” deliverable.

Both formats match how Excel thinks: columns for fields, rows for records. The conversion step is where you decide how nested JSON should flatten—whether keys become column headers, whether arrays become multiple rows, and how to handle missing values.

This is also where a purpose‑built converter saves time. Spreadsheets shine after the data is tabular; the bottleneck is turning messy real‑world JSON into that table cleanly and repeatably.

A practical flow using TableFromJSON

Below is a straightforward flow that mirrors how TableFromJSON is designed to work: preview first, adjust columns, then export—so you are not surprised by a bad import on step one.

1. Bring your JSON into the converter. Upload a file or paste a payload you copied from an API, an export tool, or email.
2. Preview the table. You should see rows and columns, not just raw text. If your data is an array of objects, you will usually get one row per item and one column per field.
3. Rename and reorder columns. This matters more than people expect: clear headers make Excel filters and pivot tables pleasant instead of painful.
4. Handle nested data consciously. If your JSON contains nested objects or arrays, decide what you need in the sheet. Sometimes you want a flattened column like customer.email; sometimes you want to split nested collections into separate exports. Previewing helps you catch “exploding arrays” before you commit.
5. Export to CSV or XLSX. Download the file, then open it in Excel normally. This is the moment where Excel feels “easy” again—because the file is already shaped like a spreadsheet.

If you repeat exports weekly (orders, payouts, campaign results), the win is consistency: same columns, same order, same downstream formulas—without manual cleanup marathons.

When you are ready to go deeper on output formats, the export formats guide walks through when CSV, Excel, Markdown, or HTML tables make sense—useful if your JSON feeds both spreadsheets and documentation.

Excel tips after you have a CSV or XLSX

Once you are in Excel with a clean import:

• Check encoding and delimiters if anything looks garbled. CSV relies on commas (or other delimiters) and consistent text quoting; converters should produce a file Excel can swallow without surprises.
• Format numbers as numbers. Sometimes IDs or postal codes look numeric but should remain text—decide early to avoid corrupted leading zeros.
• Use tables and pivot tables only after headers are stable. Changing column names every week breaks saved pivots; a stable export beats a “perfect” one‑off.

Privacy note (why “preview first” matters)

JSON exports often contain sensitive business data. A workflow that lets you preview and verify what will land in columns—before you share a workbook—reduces mistakes like accidentally leaking an email column or shipping internal IDs. TableFromJSON is built around fast conversion with a privacy‑conscious mindset; still treat exports like any confidential dataset: share minimally, store responsibly, and rotate access when teammates change roles.

FAQ

Why won’t Excel just open JSON like CSV?
CSV maps naturally to a grid. JSON maps naturally to trees. Excel can import JSON in some scenarios, but you still need rules to flatten nested structures—otherwise you get partial imports, confusing previews, or a result that is not the table you pictured.

Should I use CSV or XLSX?
Choose CSV for simplicity and interoperability; choose XLSX when you need a workbook format or plan to add charts, multiple sheets, or formatting. If your goal is “get analyzable rows into Excel,” CSV is often enough.

What if my JSON is huge?
Huge files are a workflow problem: previewing, filtering columns early, and exporting only what you need beats importing everything into Excel and hoping it survives. Start with a small sample JSON to validate column layout, then scale.

What if my JSON is deeply nested?
That is normal for APIs. Decide what “one row” means for your analysis (order‑level vs line‑item‑level vs customer‑level). The right answer depends on the question you are trying to answer—not on the JSON’s default nesting.

Can I just rename .json to .csv?
Please do not. The file contents will still be JSON; changing the extension only hides the problem and can confuse tools. Convert properly, then export a real CSV.

Will this work on Mac Excel vs Windows Excel?
Once you have a real CSV or XLSX, both platforms open it the same way. The pain is usually upstream—getting JSON into a stable table—not the operating system.

Bottom line

If Excel “won’t open” your JSON file, you are bumping into a format mismatch, not a personal failure. JSON is great for systems; spreadsheets are great for humans—once the data is tabular. Convert JSON to CSV or XLSX with a preview‑driven flow, open the result in Excel, and you are back to the part that actually matters: analyzing the data instead of wrestling the file.

Next step: open the TableFromJSON converter, paste a sample export, preview your columns, and download CSV or XLSX—then import into Excel the easy way.