Convert JSON to XLSX JavaScript Object Notation ↔ Excel Workbook Free Online Secure
Drop your JSON file in and take away XLSX. It is read and written here, in your browser, so the file never leaves your device — and what the crossing keeps, and what it cannot, is written out below rather than left for you to discover.
Convert your file
Drop your JSON file here, or choose one.
Your file never leaves this device. Everything runs in your browser.
Nothing uploaded
Convert from JSON
Convert to JSON
Where these formats come from
CSV is the oldest and the least standardised: a table written as lines of text, in use since the 1970s and only described in writing in 2005, by which time every program had already decided for itself what the separator was and when to put quotation marks. XML grew out of SGML in 1998 for documents that must carry strict structure and be checked against a schema. JSON was pulled out of JavaScript by Douglas Crockford around 2001, deliberately stripped down to objects, arrays, numbers and strings — and that minimalism is why it took over the web. YAML is its readable cousin, where indentation does the work that brackets do elsewhere. The one thing that matters when converting between them: CSV is flat, a grid of rows and columns, while JSON, XML and YAML are trees.
Where you meet them
CSV is what a spreadsheet exports and what an accountant, a shop platform or a bank statement will hand you. JSON is what web services speak and what configuration files are increasingly written in. XML survives in older enterprise systems, in invoicing standards and inside the office formats themselves. YAML is where humans write settings by hand. Converting between them is the daily work of moving data from where it was produced to where it is needed.
Questions people ask
My CSV opened as one column in Excel. Why?
Because your spreadsheet expected a different separator. Excel follows the list separator of the computer's regional settings, which is a semicolon anywhere the comma is already the decimal mark — that is, most of continental Europe. A file separated by commas then looks like a single column of text. Use the import dialogue and state the separator explicitly, rather than double-clicking the file. The same regional setting is why 3.5 sometimes arrives as a date.
Why can't my nested JSON become a tidy spreadsheet?
Because a spreadsheet is flat and JSON is a tree. A row can hold one value per column; a JSON object can hold a list inside a field inside another list. Converting means choosing how to flatten that: either joining nested names into one long column heading, or repeating the parent row once for each child. Both are compromises, and neither can be undone automatically — which is why going back from the spreadsheet to the original shape usually needs a human decision.
Does the file lose quality?
It depends on what the two formats can hold. Converting between formats that store the same thing — a PNG to a BMP, a WAV to a FLAC — loses nothing. Converting into a format that throws information away to save space, such as JPEG or MP3, loses a little every time, and converting back does not bring it back. Where a choice exists, this page errs towards keeping the original quality rather than making the smallest file.
Is my file uploaded anywhere?
No. The conversion happens inside your browser, on your own machine; the file never leaves it and there is no server here that could receive it. That is why a large file is limited by your own memory rather than by an upload, and why nothing you convert can appear in anybody's logs — including ours. The audio and video tools do fetch their conversion engine from this site the first time you use them, some thirty megabytes once; after that the work still happens entirely on your machine.
Why people convert JSON to XLSX
JSON is the language that programs use to talk to each other. An export from a web service, the answer of an API, a dump from a database, the log of an application: most of it arrives as JSON. It is excellent for software and awkward for people, because a screenful of brackets, quotes and commas is not something you can sort, filter or add up. An XLSX file is an Excel workbook: a real spreadsheet with rows and columns that opens in Excel, Numbers, LibreOffice and Google Sheets without any import step. That is why people convert JSON to XLSX: they have data a program produced, and they want to look at it, count it or share it with someone who lives in a spreadsheet.
The situations are familiar. An analyst who has pulled records from an API and wants a pivot table. A shop owner who has exported orders and needs them in Excel. A manager who has been sent the results of a survey as a technical file. A developer who wants to check a few hundred records at a glance. In every case the data is already structured, and what is missing is only the sheet.
This page converts JSON to XLSX in your browser. Your file is read and written here, so it never leaves your device, which matters for customer lists, orders and anything else personal. And the page tells you in advance what the crossing keeps and what it cannot, rather than leaving you to discover it. Below you will find how the conversion works, which kind of JSON can become a sheet and what a converted workbook does and does not contain.
How the conversion works
Keys become the first row
Your JSON file is read inside your browser. The keys of the records become the first row of the worksheet, and each record then becomes a row beneath it. The result is the rows and columns as a real worksheet, with the keys as the first row, so the file opens in Excel, Numbers or LibreOffice without a conversion step.
Real numbers and real text
Numbers in the JSON become numbers in the cells, and text becomes text. This is a clear advantage over CSV, which has no types: in the workbook, a column of amounts can be summed at once, without telling the spreadsheet what it is.
No import dialogue
With CSV, programs guess types and separators, and often guess wrongly. An XLSX carries its own structure, so there is nothing to guess. You double-click the file, and the table is there.
What is kept
All the rows and all the columns
Every record becomes a row and every key becomes a column. Nothing is dropped, and a field that appears only in a late record still gets its column.
The values
Each value is written into its cell. The sheet shows the data as it was in the JSON, ready to sort, filter and calculate.
A file that opens everywhere
The XLSX opens in Excel, Numbers and LibreOffice, and Google Sheets can import it. You can send it to a colleague without explaining how to open it.
What you should know before you convert JSON to XLSX
Only one JSON shape is already a table
The same shape rule applies as for CSV: an array of flat objects. A single object, or a tree with objects inside objects, has no rows to write and is refused rather than flattened into something you did not ask for. If your file is a tree, extract the list of records you need and convert that.
What comes out is data, not a document
What comes out is data, not a document: one sheet, no formulas, no column widths, no colours and no frozen header, because none of those were in the JSON to begin with. A JSON file knows nothing about how a spreadsheet should look. You will want to widen the columns and format the header yourself, which takes a few moments.
Nested values are written as JSON text
A nested value, where a field holds a list or an object, is written into the cell as JSON text, because a cell cannot hold a branch. The information is there, and you can split it with the tools of your spreadsheet.
How to convert JSON to XLSX here
Add your file
Drop the JSON file onto the page or pick it from your device. It is read inside your browser and is not uploaded.
Convert
Press the button. A file of ordinary size takes a moment. Leave the page open until it is done.
Download and open
Download the XLSX and open it in your spreadsheet program. Check the header, a few rows in the middle and the last row, then widen the columns and format as you wish.
A closer look at JSON and XLSX
Trees and grids
JSON describes a tree: objects containing values, which may be objects or lists in turn. A worksheet is a grid: rows and columns, nothing more. A tree can hold things that a grid cannot, such as a branch with different branches under it. A list of uniform records, on the other hand, fits a grid perfectly. To convert JSON to XLSX is to go from the general form to the special one, and it works smoothly when the data was really a table all along.
XLSX or CSV?
If you only need a plain table that any program can read, JSON to CSV is lighter and more universal. XLSX is better when the people opening it use Excel, when you want numbers typed correctly and when you wish to avoid the guesswork of an import. For most office work, the workbook is the more comfortable choice.
Why the strictness helps
Tools that accept any JSON and flatten it automatically often invent column names such as address.street or items.0.price. This is convenient until you need to know what happened. By accepting only the shape that is already a table, this page spares you from silent decisions.
Common situations in detail
Exports from web services and APIs
Most services return lists of records as JSON. If you need them in Excel, convert JSON to XLSX and open the result. It is the quickest route from an API answer to a pivot table.
Orders, customers and products
Shop platforms often let you export data as JSON. A workbook of orders or products can be sorted by date, filtered by customer or totalled by product in a few clicks.
Survey results and logs
Tools that store survey answers or event logs as JSON produce one record per answer or event. In a worksheet, they can be counted, charted and compared.
Sharing data with non-technical colleagues
A colleague who has never seen a curly brace will understand a worksheet at once. Converting before you send saves explanations and mistakes.
Practical advice before you convert JSON to XLSX
Check the shape of your file
Open the JSON in a text editor. If it starts with a square bracket and holds a list of curly-braced records with simple values, it is the right shape. If it starts with a curly brace and has records nested inside, look for the list you need and extract it first.
Know which values are nested
If some fields contain lists or objects, they will appear as JSON text in their cells. Decide whether you need them split, and plan to do it in the spreadsheet.
Think about the size
Everything runs on your device, so a very large file needs memory. For files of many megabytes, use a computer, and split the data if the page struggles.
Plan the formatting
Since the workbook has no widths, colours or frozen header, plan a minute for formatting after the conversion. Select all the columns and use auto-fit, make the header bold and freeze the first row.
Questions people ask before converting
Why was my file refused?
Because it is not an array of flat objects. A single object, or a tree with objects inside objects, has no rows to write. Pick out the list you need and convert that.
Why is there only one sheet?
Because a JSON list of records is a single table. One sheet is the honest result.
Where are my formulas and colours?
They were never in the JSON. The workbook holds data, and the formatting is yours to add.
What happens to lists inside a record?
They are written into the cell as JSON text, because a cell cannot hold a branch.
Is my file uploaded?
No. The conversion runs in your browser and the file never leaves your device.
Can I go back to JSON?
Yes. XLSX to JSON turns a workbook back into a list of records.
Choosing wisely when you convert JSON to XLSX
Workbook or plain table?
For Excel users, the workbook. For anything that must be readable by any tool, a CSV. Both are available here.
Other targets
If the destination is a markup file or a configuration, JSON to XML and JSON to YAML serve those needs.
Keep the JSON
The JSON is the master. It holds the structure and the types. Keep it, and treat the workbook as a view of the data.
Getting a good result after the conversion
Auto-fit the columns
Select all and use auto-fit so that every column is wide enough for its content. It turns a cramped sheet into a readable one.
Format the header and freeze it
Make the first row bold and freeze it, so that the names stay visible as you scroll through the records.
Set number and date formats
Numbers arrive as numbers. If you want currency symbols or a fixed number of decimals, apply the format. Dates that were text in the JSON can be converted with the date functions of your program.
Check a few rows against the source
Compare a couple of records in the sheet with the JSON. It takes a minute and tells you the table is faithful.
Preparing your JSON so that it converts well
Shape the data before you convert JSON to XLSX
If your file is a tree, you can usually reshape it into a list of flat records first. Pick the list that holds what you want to count: the orders, the customers, the events. Copy it into a file of its own, with the square brackets around it, and the page will accept it.
Keep the field names meaningful
The keys become the header, so the clearer the names, the more readable the sheet. If you control the source, use names such as order_date and customer_name in place of abbreviations that only a programmer would understand.
Be consistent about types
A field that holds numbers in most records and text in a few will confuse sorting and sums. If you can, clean the odd ones before the conversion, so that each column means one thing.
Working with the workbook after you convert JSON to XLSX
Turn the range into a table
Spreadsheet programs have a command that turns a block of cells into a named table, with filter buttons on the header and banded rows. After you convert JSON to XLSX, apply it. Sorting and filtering then become one click, and formulas that refer to the table keep working when you add rows.
Build a pivot table
A pivot table is the quickest way to answer questions such as which product sold most, which customer ordered most often or how many events happened each day. Because the workbook has proper headers and typed values, the pivot builder recognises the fields straight away.
Add charts
Select the columns you want to compare and insert a chart. The data that arrived as a list of records from a program becomes a picture that a meeting can understand in seconds.
Combine with other sheets
If you have several JSON exports, convert JSON to XLSX for each and copy the sheets into one workbook, or use lookup functions to join them on a common field such as a customer number. The typed values make such lookups reliable.
Save a copy for the future
Once you have formatted the workbook to your liking, save it as a template. The next export will be a matter of pasting the new data under the same header.
Privacy and handling
Why local conversion matters for data
Data files often hold what is private: customers, orders, addresses, messages. Many online converters upload your file to a server, process it and send back the result, and for a while a copy lives on a machine you do not control. Here your own browser does the work, so the data stays on your device.
What happens when you leave
When you close the page, the converted file disappears from the browser, so download it first. Nothing about your data is kept.
If something goes wrong
The page says the file is not valid JSON
There may be a stray comma, a missing quote or a bracket that does not close. Open the file in an editor that highlights JSON errors and fix the line it points to.
The workbook looks cramped
That is normal, since a JSON file carries no widths. Use auto-fit on the columns.
The page freezes with a large file
Everything runs on your device, and a large file needs memory. Try again on a computer, or split the data.
Related tools
The same family of tools covers the neighbouring jobs. To go back, use XLSX to JSON. For a plain table, JSON to CSV and CSV to JSON work with text files. For other formats of structured data, there are JSON to XML, XML to JSON, JSON to YAML and YAML to JSON. When the figures are in a PDF, PDF to XLS rebuilds a table from the page.
A worked example
Say you have exported 500 orders from an online shop as a JSON file, and your accountant wants them in Excel. You drop the file here and press the button. A moment later you download a workbook with the field names in the first row and 500 rows beneath it. You auto-fit the columns, freeze the header and send it. The accountant opens it with a double-click, and the amounts add up at once, because they are numbers. The JSON stays in your folder as the source.
A short checklist
Before converting
Check that the file is a list of records. Note which fields are nested. Keep the JSON.
While converting
Stay on the page until the file is ready.
After converting
Open the workbook, auto-fit the columns, format the header, check a few rows against the source and save.
Common mistakes
Feeding it a tree
Do not expect to convert JSON to XLSX for a deeply nested file. Extract the list of records first.
Expecting a formatted report
The workbook holds data, not a document. Add the formatting yourself.
Deleting the JSON
Keep it. It holds the structure the table cannot.
Your data stays on your device
The conversion happens locally. Your file is read by your own browser, rewritten there and handed back as an XLSX. Nothing is uploaded, so no copy ends up on a server and nobody else can read it. For data with private content, that is the safe way to convert JSON to XLSX.
Summary
To convert JSON to XLSX here, drop the file and press the button. It is read and written in your browser, so the file never leaves your device. The rows and columns arrive as a real worksheet, with the keys as the first row, so the file opens in Excel, Numbers or LibreOffice without a conversion step. The same shape rule applies as for CSV: an array of flat objects. What comes out is data, not a document: one sheet, no formulas, no column widths, no colours and no frozen header, because none of those were in the JSON to begin with. A nested value is written into the cell as JSON text.