Convert JSON to an Excel Spreadsheet
Turn JSON data into an Excel file organized in rows and columns — processed locally in your browser.
Drop your file here or click to browse
JSON files (.json)
Your data stays on your device
Nothing to delete afterwards
Safe for raw API responses
Works in every modern browser
How it works
- 1
Paste or drop your JSON
An array of objects works directly; paste the text or drop a .json file on the page.
- 2
Check the columns
Confirm the header row and the column set match what you expected.
- 3
Download the workbook
Open the .xlsx in Excel, Google Sheets, LibreOffice, or Numbers.
Why use this tool
Typed cells, not guessed ones
A number is written as a number and text as text, so Excel has nothing left to interpret when the file opens.
Leading zeros survive
A product code like `007` stays `007`, because the cell is declared as text rather than parsed from a line of characters.
No separator, no encoding
A workbook carries its own structure and its text in Unicode, so neither question ever comes up.
Opens with one double-click
No import wizard, no dialog asking about delimiters — the file opens as a sheet.
Nothing is uploaded
The workbook is built in your browser; an API response full of records never travels anywhere.
Free, no account
No signup, no watermark, no cap on how many files you convert.
Writing a workbook means Excel has nothing left to guess
This is the reason to go straight to .xlsx rather than producing a CSV and opening it. A CSV file is a line of characters, and everything Excel knows about it comes from guessing on import: whether `007` is the number seven or a product code, whether `03/04` is March or April, whether a cell beginning with an equals sign is text or a formula. A workbook does not work that way. Every cell carries a declared type, so a number is stored as a number, text is stored as text, and Excel opens the file with nothing to interpret. That single difference removes the three most common ways spreadsheet data gets quietly corrupted, and it is why this conversion is worth doing directly instead of through the CSV route.
The identifier problem disappears entirely
Anyone who has exported data to a spreadsheet has watched an identifier get destroyed. An order reference `0004512` loses its zeros. A long account number turns into scientific notation. A part code like `1-2E3` becomes a number nobody recognises. All of these happen at import time, when a CSV line is handed to a parser that has to decide what each field means and gets it wrong in a way that looks plausible. Writing the workbook directly ends the problem rather than working around it: the cell holding `0004512` is declared as a text cell, so there is no parse step and nothing to lose. If your JSON carries reference numbers, SKUs, phone numbers, or postcodes, this is the practical reason to choose a workbook over a CSV export.
A formula that arrives as text stays text
There is a security angle here that is easy to miss. When user-typed content ends up in a CSV, any value starting with `=`, `+`, `-`, or `@` is treated by the spreadsheet as a formula on import — the injection problem that makes exported free-text fields genuinely risky. Writing .xlsx removes the mechanism rather than mitigating it. A string from your JSON becomes a cell explicitly marked as a string, so a note field reading `=cmd|...` sits in the sheet as those literal characters and is never evaluated. If the data came from a form real users filled in, and it is going to a colleague who will open it without thinking twice, that difference matters more than the file size.
A workbook can hold several sheets, and that changes what nesting can become
JSON nests and a single table cannot, which is the usual constraint. A workbook loosens it. Because an .xlsx file holds many sheets, a structure with a parent and a repeating child — orders and their line items, users and their sessions — can become two sheets linked by an identifier column, rather than one sheet that either crushes the children into a cell or repeats the parent down every row. That is a modelling decision rather than something a converter can infer, so it means splitting the JSON before conversion and producing the sheets separately. But it is worth knowing the option exists, because the flat-file instinct of picking one shape and living with it comes from CSV's limits, not from Excel's.
What a workbook will not do for you
A converted file is data, not a report. It will not carry formulas, because the JSON never had any; the columns are values, and any calculation has to be added afterwards. It will not build pivot tables, conditional formatting, charts, or frozen header rows, and it will not know which columns should be currency or which dates should display as dates rather than as whatever the default is. None of this is a shortcoming of the conversion — it is the difference between the data and the presentation of the data. Expect to spend a couple of minutes formatting after opening, and do not spend twenty looking for a setting that would have done it for you.
The limits are Excel's, not the tool's
A worksheet stops at 1,048,576 rows and 16,384 columns. Those are hard limits of the file format, not of any converter, and an array longer than a million records has nowhere to go in a single sheet regardless of what produced it. In practice you meet a softer limit first: a workbook with several hundred thousand rows opens slowly, recalculates slowly, and becomes unpleasant to work with long before it becomes impossible. If your JSON is that large, the honest answer is that a spreadsheet is the wrong destination and the data belongs in a database or a tool built for it. For everything below that, and that is the overwhelming majority of real files, the format is not the constraint. Your device memory is.
Common mistakes to avoid
- Producing a CSV and renaming it .xlsx. The extension does not change the contents; Excel will either complain or fall back to guessing every field, which is exactly what a workbook exists to avoid.
- Expecting the workbook to arrive formatted. The conversion carries data, not presentation — currency formats, column widths, frozen headers, and charts are a couple of minutes of work afterwards.
- Converting a million-plus record array. A worksheet stops at 1,048,576 rows; past a few hundred thousand a workbook is painful to use even where it still opens.
- Assuming nesting must be flattened into one sheet. A workbook holds many sheets, so a parent-and-children structure can become two sheets linked by an identifier — but you have to split the JSON first.
- Pasting a raw API response into an online converter. Those payloads usually carry identifiers, emails, and sometimes tokens in fields you never scrolled to; build the workbook locally.
How it compares
| Aspect | This tool | Online converters | Exporting a CSV instead |
|---|---|---|---|
| Data sent to a server | Never | Usually yes | No |
| Cell types declared | Yes | Varies | No — guessed on import |
| Leading zeros survive | Yes | Varies | Usually not |
| Formula injection possible | No | Varies | Yes |
| Account or signup | Not needed | Often required | Not needed |
| Price | Free | Free / paid tiers | Free |
Features
Genuine .xlsx output
A real workbook, not a CSV file given a spreadsheet name and an icon.
Types preserved end to end
Numbers, text, and booleans land in cells declared as what they are.
Union header from ragged records
Every key found across the array gets a column, so optional fields are not lost.
Dotted columns for nesting
A nested `address` object becomes `address.city` and `address.postcode` rather than a stringified blob.
UTF-8 throughout
Accented, Arabic, Turkish, and other non-ASCII text is written into the workbook unchanged.
Handles large arrays
Tens of thousands of records convert without an upload queue.
Nothing to install
No Excel licence, no runtime, no dependencies — it runs on the web page.
Arabic and RTL ready
Full interface in eight languages, including right-to-left Arabic.
Secure by default
Served over HTTPS, with no file tracking and no third-party upload.
Who uses it
Developers
Handing an API response to a colleague as a file they can open and sort, with the reference numbers intact.
Operations staff
Turning a system export into a workbook for finance without an import wizard in the middle.
Data analysts
Getting typed columns straight away instead of cleaning up whatever a CSV import decided each field was.
Account managers
Producing a client-ready sheet from an export without opening a code editor.
Frequently Asked Questions
No. The conversion runs entirely in your browser — your data is never uploaded, stored, or shared.
Yes. Every row and column is converted faithfully; your data is written to a proper .xlsx sheet.
Yes — completely free, with no account, no watermark, and no limit on how many files you convert.