Review a JSON data export in Excel on Mac
A JSON export can be easier to inspect as rows and columns. Lemora converts a list of records into an XLSX workbook, using record keys as column headings. Before relying on the table, check that the export contains the records you intended and understand how nested objects and missing values appear in cells.
Inspect the export, convert it, then check the table
- Save the JSON file in Finder. Identify whether it contains a list of records, a wrapper around a list or a different structure.
- With Lemora running, select the file and press Shift-Command-E. Choose XLSX on the Convert page.
- Open the workbook and check its headings and row count against the source records.
- Inspect a record with nested values, one with missing fields and one with important identifiers or numbers. Confirm how each appears in the table.
- Keep the original JSON alongside the workbook. Use CSV instead on the original file's Convert page if the receiving application specifically requires CSV.
Results are saved beside the originals when folder access is available, or in Downloads/Lemora otherwise. Source files are never overwritten.
Where to find these actions
- Convert → XLSX (Convert to Excel): An Excel sheet from a list of records: one column per key.
- Convert → CSV (Convert to CSV): A table from a list of records: one column per key.
- Tools → Tidy: Lay it out neatly, in the same format.
What you get
A workbook with one row per record
Record keys become columns in first-seen order. Nested objects and arrays are written as JSON text inside cells, rather than expanded into related tables.
Works with: Readable JSON exports, especially arrays of record objects. Supported YAML and property list inputs can use the same table conversion.
Lists of records make the clearest tables
An array of objects is a natural fit: each object becomes a row, and its keys contribute columns. Lemora collects columns in the order they first appear, including keys found in later records. When a record lacks a column's key, its cell is empty. A list of simple values instead becomes a single column named value.
A wrapper can change which data is selected
For an object containing exactly one array with record objects, Lemora uses that list for the table. If the object contains multiple such lists, it does not ask you to choose one: the object is treated as a record instead. Check the source structure before assuming the workbook represents one particular list. Use a JSON editor to prepare a specific subset when needed.
Nested data stays nested inside a cell
A field containing an object or array is serialized as compact JSON in its cell. A list of addresses does not automatically become an address worksheet, and an object such as a customer profile does not automatically become separate profile columns. This preserves a representation of the value but may not suit a flat import template.
An empty cell can have more than one explanation
Both a missing key and a JSON null can appear as an empty cell. The workbook therefore cannot always tell you which condition was present in the source. Return to the JSON when that distinction matters. Keep the original for exact structure and types rather than treating the table as a lossless substitute.
Inspect identifiers and numeric values in the destination app
Check long IDs, leading zeroes and values that resemble dates. The table representation and the way a spreadsheet app displays it can differ from the source's types and spelling. Sample the fields that matter to your task before filtering, calculating or exporting the workbook again.
Pretty printing is a different operation
If you only need to make a compact JSON file easier to read, choose Tidy on the Tools page rather than converting it to a spreadsheet. A table is useful for scanning records, but formatting the JSON keeps its nested structure visible in the source format.
Questions
Does Lemora flatten nested keys into columns?
No. Nested arrays and objects are stored as JSON text in cells. Prepare a flatter structure separately when a destination requires one.
Can a single JSON number become a workbook?
A standalone scalar has no table structure, so the conversion reports that there is no table to make. An empty list also cannot produce a useful table.
Is the JSON uploaded for conversion?
No. Parsing and workbook creation happen on your Mac.
Try this workflow on your Mac
Download Lemora on the Mac App Store Free to try: every feature for your first 25 actions. macOS 15 or later.