Skip to content
Lizely

JSON to Excel Converter

Convert a JSON array of objects into a local .xlsx workbook while preserving first-seen field order and never uploading the data.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Paste a non-empty JSON array whose items are objects.
  2. 2.Convert to Excel; first-seen object keys become the worksheet headers.
  3. 3.Download converted.xlsx and confirm the columns in the destination application.

About JSON to Excel Converter

JSON to Excel turns a non-empty JSON array of objects into a one-sheet .xlsx workbook in your browser. Paste the JSON, select Convert to Excel, and the page creates a local download named converted.xlsx. No JSON is posted to a conversion service, stored in an account, or used to train this tool. The original text stays under your control. It is useful for API samples, configuration exports, test fixtures, analytics responses, or small records that need a workbook for review or handoff.

The top-level value must be an array, and every array item must be an object. The first row of the worksheet contains field names in the order they first appear while scanning the objects. A later object can introduce a new field, and the tool adds that column after existing columns; objects missing a field receive an empty cell. Strings, numbers, booleans, and null values remain straightforward cell values. Nested objects and arrays are serialized as compact JSON text because a flat worksheet cannot honestly represent nested structure without inventing a column mapping. The converter does not infer a schema, flatten nested keys, rename fields, or guess a type from the spelling of a value.

The generated workbook is a data handoff, not a formula engine. The browser does not execute JSON text, formulas, macros, external links, scripts, or remote workbook connections. Values that look like spreadsheet formulas are written as ordinary visitor text cells. Dates remain the value supplied by the JSON rather than a locale-dependent date display. This boundary prevents a pasted payload from becoming executable page or spreadsheet logic while keeping the output auditable. If a downstream system needs typed dates, locale formatting, formulas, charts, comments, filters, validation rules, or multiple sheets, prepare those explicitly in software designed for that richer workbook model.

Limits are visible and fail closed: JSON input may contain at most 1,000,000 characters, 10,000 rows, 200 columns, and 200,000 cells. The tool rejects invalid JSON, an empty array, a primitive array item, empty objects with no fields, or a table over a stated limit. It does not silently omit keys, truncate a long string, or create a partial file. The workbook is written with the locked SheetJS core only after you request conversion, keeping the parser out of the initial page load.

For a reliable result, begin with a compact representative JSON sample and inspect the generated header order before handing it to another system. Preserve the original JSON as the source of record, especially when nesting, null semantics, leading-zero strings, or numeric precision have business meaning. Open the downloaded workbook once in the intended application and validate the fields that drive an import. This tool does not fetch a URL, merge JSON files, validate a business schema, repair malformed JSON, create formulas, or promise that all spreadsheet programs will treat the values identically. It provides a bounded, local, transparent conversion from object records to a simple Excel table.

Methodology & sources

Validate a bounded JSON array of objects; preserve first-seen keys; serialize nested values as JSON text; dynamically load the locked SheetJS core only for a local OOXML download; never evaluate visitor values as formulas.

Frequently asked questions

Does this send JSON to a server?
No. JSON parsing and the .xlsx download both happen in the browser.
How are nested objects and arrays handled?
They are serialized as compact JSON text in one cell rather than silently flattened.
How is column order chosen?
The first occurrence of each object key defines a stable first-seen column order.

Related tools

Developer Tools guides

View all