Runs entirely in your browser

JSONL to Excel. A real .xlsx.

Turn a JSON Lines or NDJSON export into a real Excel workbook, built in your browser with no upload.

JSONL to Excel
Processed locally in your browser
JSONL / NDJSON
Workbook preview

Your table preview will appear here

How to use JSONL to Excel

  1. Paste or drop the export

    One JSON object per line. Files from mongoexport, BigQuery and log pipelines all use this shape.

  2. Preview the sheet

    Nested fields become dot-notation columns and the layout is shown as a table, so you can check it before the workbook is built.

  3. Download the workbook

    A genuine Office Open XML file with a bold, frozen header row — no import wizard and no format-mismatch warning when Excel opens it.

Why use Parsefy JSONL to Excel?

Your data never leaves your device

Everything runs in your browser tab — there is no upload step and no server to store anything. That makes it safe for API responses, database dumps and production data you could not paste into a hosted converter.

Real .xlsx: typed cells, frozen header, any spreadsheet app

The Office Open XML package is assembled properly in your browser, so Excel, LibreOffice, Numbers and Sheets all open it natively. Numeric fields arrive as numbers, the header row is bold and frozen, and accented characters and emoji come through intact.

Checked against Excel's own limits first

Row, column and cell-length limits are checked before the file is built, so you get a warning rather than a workbook Excel refuses to open.

No sign-up, no file-size tier

There is no account, no email wall and no paid plan gating bigger files. The only real limit is how much memory your own browser can spare.

JSONL to Excel — frequently asked questions

Can Excel open a JSONL file directly?

Not usefully. Excel has no importer for one-object-per-line JSON, so the file opens as raw text in a single column. Converting first produces a real worksheet with one row per record and one column per field.

Is my data uploaded to build the file?

No. The whole workbook is assembled locally in your browser, which is unusual for a converter of this kind and means production exports never leave your device.

What happens to very long ID numbers?

They are kept as text rather than converted to numbers, because Excel displays long numeric values in scientific notation and drops trailing digits beyond fifteen. Keeping them as text preserves the exact value.

How many records can it handle?

An Excel worksheet holds 1,048,576 rows and 16,384 columns, and your data is checked against both before the file is built. Very large exports may hit your browser's memory limits before they hit Excel's own limits.