JSON to Excel Converter
Turn JSON into a real .xlsx in your browser — nested objects flatten, arrays stay intact.
How to Convert JSON to Excel in Three Steps
Paste your JSON or drop in a file, let the browser flatten it into a table, then download a real .xlsx. JSON to Excel with no install, no account, no upload.
Paste JSON or Upload a File
Paste a JSON document, drop in a .json file, or click Load Example. Everything runs in your browser — there is no upload step. Pasted input has no fixed byte limit; uploaded files are capped at 100 MB.
Preview the Flattened Table
Your JSON to Excel conversion parses and flattens on the spot. Nested objects become dot-notation columns — {user:{name:'Alice'}} lands as user.name. Preview the first 100 rows to confirm the shape before downloading.
Download a Real .xlsx or Copy as CSV
Export a genuine Office Open XML .xlsx that opens in Excel, Google Sheets, Numbers, or LibreOffice. Need CSV? One click copies the flattened table. No install, no signup, no daily quota.
What Makes This JSON to Excel Converter Different
Six things this JSON to Excel converter actually does — every one runs in your browser, with no signup and no upload.
Your JSON Never Leaves the Browser
The JSON is parsed, flattened, and rebuilt as a workbook on your device. There is no upload step to opt out of — the network is never part of the conversion. The same is true the other direction: you can convert CSV files into Excel workbooks just as privately.
Real OOXML .xlsx, Not a Renamed File
A genuine Office Open XML workbook — a ZIP archive of XML, native since Excel 2007. Not a renamed .xls, not a CSV with a new extension. It opens in Excel, Google Sheets, Numbers, and LibreOffice.
Nested Objects Flatten With Dot Notation
Recursive dot-notation flattening turns {profile:{age:34}} into a column named profile.age. Keys keep their first-seen order, and columns are the union of every key across all objects — a missing field leaves an empty cell.
Arrays Follow One Clear Rule
Arrays behave the way you would predict. If every element is an object, the cell keeps the array as a JSON string so nothing is lost. Otherwise the values join with ‘; ’ into one cell — [10,20,30] becomes 10; 20; 30. You can preview the result before downloading.
Numbers, Booleans, and Null Stay Typed
This JSON to Excel converter keeps numbers numeric and booleans as TRUE/FALSE. null and undefined become empty cells, not the string “null”. Real types, not everything-as-text.
Three JSON Shapes, One Converter
Paste an array of objects (a typical API response), a single object (one row), or a primitive array like [10,20,30] (each value gets its own row in a column named value). No config, no schema — the converter detects the shape and builds the table. See the full set of free browser-based Excel tools for more.
From JSON to XLSX — What the Conversion Actually Does
JSON and Excel both carry data, but they are built on opposite assumptions. JSON is hierarchical — nested key-value pairs and arrays, defined by two aligned official standards, most notably the JSON Data Interchange Format (RFC 8259) (IETF STD 90, December 2017). It is what APIs and databases return. Excel is a grid — rows and columns built for a person to read, filter, sort, and pivot. Converting JSON to Excel moves data from nested structures machines return into a grid a person can analyze.
Two Standards Behind the Conversion
JSON’s syntax is fixed by RFC 8259 together with ECMA-404 (both published December 2017) — the two standards agree, so any valid JSON parses the same way everywhere. The .xlsx side is defined by the Office Open XML file formats (ECMA-376), 5th edition December 2021: a .xlsx is a ZIP archive of XML documents, the native Excel format since Excel 2007. A single worksheet holds up to 1,048,576 rows by 16,384 columns per Microsoft’s published limits — the practical ceiling for any large JSON export.
See It Flatten — Nested JSON to an Excel Table
[
{
"id": 1042,
"name": "Alice Chen",
"profile": { "age": 34, "city": "Austin" },
"tags": ["enterprise", "renewal"],
"orders": [
{ "sku": "A1", "qty": 2 },
{ "sku": "B2", "qty": 1 }
]
}
]| id | name | profile.age | profile.city | tags | orders |
|---|---|---|---|---|---|
| 1042 | Alice Chen | 34 | Austin | enterprise; renewal | [{"sku":"A1","qty":2},{"sku":"B2","qty":1}] |
The example shows the rule in action: nested keys flatten to columns (profile.age, profile.city), an array of objects (orders) stays as an in-cell JSON string so nothing is lost, and a simple array (tags) joins with '; ' into one cell. Arrays of objects, single objects, and primitive arrays all work; NDJSON and JSONL (one object per line) do not.
JSON vs. XLSX, Side by Side
| JSON | XLSX | |
|---|---|---|
| What it is | Nested key-value text | Workbook (ZIP + XML) |
| Standard | RFC 8259 / ECMA-404 (2017) | ECMA-376 (2021) |
| Structure | Hierarchical (objects, arrays) | Flat grid (rows × columns) |
| Data types | string, number, boolean, null | Numbers, dates, currency, formulas, styles |
| Best for | APIs, config, data exchange | Reading, analyzing, presenting |
Row and column limits per Excel’s official worksheet specifications. The legacy .xls (Excel 97–2003) caps at 65,536 rows — one reason online tools that default to .xls limit what you can export.
Who Converts JSON to Excel — and Why
Five real reasons JSON lands on someone’s desk and needs to become a workbook — and why pasting it here beats writing a script.
API Responses for Analysis
A REST endpoint returns JSON. You could write a pandas script, but analysts want a workbook they can filter and pivot now. Paste the payload, flatten it, download the .xlsx — the conversion runs while you watch.
Database Exports and Mongo-Style Documents
A Mongo export or a NoSQL dump lands as document JSON, nested fields and all. The converter flattens nested objects to dot-notation columns, so each document becomes a row you can sort and report on.
Config Files and i18n Resources
package.json, tsconfig, or an i18n locale file — turn the structure into a table to audit keys side by side. Missing translations show up as empty cells you can spot at a glance.
E-Commerce Order Payloads for Reconciliation
An order webhook payload, with nested customer, line items, and totals. Flatten it to a row per order, then reconcile two Excel spreadsheets against your payment processor’s export. Arrays of line-item objects stay intact as an in-cell JSON string.
Sharing With Non-Technical Collaborators
Your colleague does not want raw JSON — they want to double-click and see columns. Convert it here and send the .xlsx, or compare two columns in Excel against another dataset first.
Your JSON Stays On Your Device — Not “Deleted After 24 Hours”
Most online JSON to Excel converters work the same way: you upload the file, a server processes it, and the page promises it is “deleted after 24 hours.” ConversionTools, CoolUtils, Aspose, and DataConverter all process your JSON on their servers. This converter is built the other way: the JSON is parsed, flattened, and written as a .xlsx in your browser. There is no upload step — not a “secure” one, not a “deleted later” one.
Close the tab and the JSON is gone, because it was never anywhere else. No account, no email, no daily quota. That matters for API keys, customer records, or anything under an NDA — the privacy story is not a retention promise, it is the absence of the upload. Paste as much as your device’s memory allows; uploaded files are capped at 100 MB.
Converting JSON to Excel — Common Questions
{user:{name:'Alice'}} becomes user.name. Flattening is recursive, keys keep their first-seen order, and columns are the union of every key across all objects — a missing field leaves an empty cell.[10,20,30] becomes 10; 20; 30. Preview the first 100 rows before downloading.[10,20,30] (each value gets its own row in a column named value). The converter detects the shape automatically. Note: NDJSON and JSONL — one JSON object per line — are not supported; paste a single standard JSON document.