Convert JSON to Excel
online, free & instant

JSON to spreadsheet in three steps

No account. No upload. No nonsense.

Related JSON tools

Common questions answered

Converting JSON to Excel format

Excel spreadsheets (XLSX) are the universal format for business data. Finance teams, project managers, and analysts rely on Excel for formulas, pivot tables, and charts. Converting JSON to CSV (which Excel opens natively) bridges developer JSON APIs and business Excel workflows, enabling analysis without coding.

This tool converts JSON to CSV format that Excel opens natively. Each object becomes a row, each key a column header. The converter handles proper escaping so commas, quotes, and newlines in values do not break the spreadsheet structure. Download the output as .csv and open in any spreadsheet application.

[
  {"name":"Alice","dept":"Engineering","salary":95000},
  {"name":"Bob","dept":"Sales","salary":75000},
  {"name":"Charlie","dept":"Engineering","salary":105000}
]

name,dept,salary
Alice,Engineering,95000
Bob,Sales,75000
Charlie,Engineering,105000

→ Save as .csv → Open in Excel

Get the most out of this tool

• Save converter output as .csv — Excel, Google Sheets, and LibreOffice all open CSV files natively.
• Use Excel Text to Columns if CSV parsing does not auto-detect columns on your system.
• For dates and numbers, Excel may misinterpret formats — prefix with single quote (') to force text mode.

How JSON-to-Excel conversion works

Converting JSON to Excel involves two conceptual steps: first, flattening the JSON's hierarchical structure into a tabular representation, and second, writing that tabular data to a spreadsheet file format. Excel's native format (XLSX) is a ZIP archive containing XML files defined by the Open Packaging Conventions (OPC) and Open XML standards. The JavaScript ecosystem provides libraries like SheetJS (xlsx) and ExcelJS that abstract away this complexity, exposing APIs to create workbooks, sheets, and cells programmatically.

JSON arrays of objects map naturally to spreadsheet rows — each object becomes one row, and the union of all object keys becomes the column headers. The algorithm scans all objects to discover all possible keys (since heterogeneous arrays may have different keys per object), then emits a header row followed by one data row per object. Empty cells appear where a given object lacks a particular key, preserving alignment across all rows.

Nested JSON objects within array elements present a flattening decision. Option one: convert nested objects to JSON strings in a single cell — preserving the full data but making nested fields inaccessible to Excel formulas. Option two: flatten with dot-notation — address.city and address.zip become separate columns. Option two is more useful for Excel analysis but increases the column count for deeply nested structures.

Cell type mapping from JSON to Excel affects how Excel handles the data downstream. JSON numbers should become Excel numeric cells so that SUM, AVERAGE, and sort functions work correctly — not text cells that Excel displays as left-aligned strings. JSON booleans should become Excel boolean cells (TRUE/FALSE). JSON null should become empty cells. Correct type mapping prevents "number stored as text" warnings and ensures Excel formulas work as expected.

Excel date handling requires special attention. JSON has no native date type — dates are typically represented as ISO 8601 strings ("2024-01-15T10:30:00Z"). When converting to Excel, ISO date strings should be parsed and written as Excel serial date numbers with a date format applied, allowing Excel's date-aware filtering, sorting, and calculation features to work correctly. A text cell containing "2024-01-15" cannot be used in Excel's date functions.

For browser-based JSON-to-Excel conversion without a server, the SheetJS community edition (Apache License 2.0) is the most widely used solution. It generates XLSX files entirely in the browser, creating a Blob URL that triggers a file download when clicked. No data is sent to any server — the conversion happens locally. This approach works offline and protects sensitive JSON data from being uploaded to third-party services.

Large JSON-to-Excel conversions involving hundreds of thousands of rows may create XLSX files that are slow to open or manipulate in Excel itself. Excel has a row limit of 1,048,576 rows (2^20) per worksheet. For datasets approaching this limit, consider splitting data across multiple worksheets, filtering to relevant rows before converting, or using a proper database export tool rather than a browser-based converter.

When developers convert JSON to Excel

JSON-to-Excel conversion pitfalls

• Numbers imported as text: If JSON numbers are written as Excel text cells instead of numeric cells, Excel formulas like SUM and AVERAGE will not work. Look for cells left-aligned in Excel (numbers should be right-aligned by default) and the "number stored as text" warning triangle as indicators of this problem.
• Dates not recognized by Excel: ISO 8601 date strings that are not converted to Excel serial date format appear as plain text. Excel date functions like DATEDIF, YEAR, and date filtering by month or quarter will not work on text dates. Ensure your converter parses date strings and writes them as proper Excel date values.
• Nested objects losing structure: JSON with deeply nested objects flattened to a single level produces many columns with long dot-notation names that may exceed Excel's 32,767 character column header limit (practically, very long headers are hard to read). Consider restructuring deeply nested JSON before converting rather than relying on automatic flattening.
• Special characters in keys causing issues: JSON keys containing characters that are invalid in Excel column headers — like forward slashes, brackets, or very long names — may be truncated or cause unexpected behavior. Sanitize key names before converting to ensure they work as Excel column headers.

Additional frequently asked questions