JSONL to CSV. One line per record.
Convert JSON Lines and NDJSON exports into a single CSV table, entirely in your browser.
Your table preview will appear here
How to use JSONL to CSV
Paste or drop the export
One JSON object per line, as produced by mongoexport, BigQuery, Elasticsearch or a structured log file.
Every record is read
Nested fields are flattened into dot-notation columns, and the header is built from the union of keys across all lines, so a field that appears only in later records still gets a column.
Download the CSV
Fields containing commas, quotes or line breaks are quoted to the CSV specification, so the file opens correctly in Excel, Sheets and database importers.
Why use Parsefy JSONL to CSV?
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.
Records with different keys still line up
Log and export files rarely have a fixed shape. Every line is scanned and the header is the union of all keys, so a field present in only some records gets its own column and the rest are left empty rather than shifting the data.
A truncated export is salvaged, not rejected
If the file was cut off partway through a record — a common outcome of a piped command or a copied terminal buffer — the complete records are recovered and you are told how many, instead of the whole conversion failing.
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 CSV — frequently asked questions
What is the difference between JSONL, NDJSON and JSON?
JSONL and NDJSON are the same format under two names: one complete JSON object per line, with no wrapping array and no commas between records. Ordinary JSON is a single document. Both are handled here — the format is detected automatically.
Is my export uploaded to a server?
No. Parsing and CSV generation both run in your browser tab, so the data never crosses the network. That is the difference from most converters of this kind, and it is what makes production exports safe to paste in.
How are nested objects handled?
They are flattened into dot-notation columns, so a record containing user.address.city produces a column of that name. Arrays are indexed the same way, which keeps every value visible rather than collapsing it into one cell.
What if one line is malformed?
That line is skipped and reported, and the rest of the file is still converted. Trailing commas, single quotes and unquoted keys are repaired automatically rather than treated as errors, since exports frequently contain them.