JSONL Free Online JSONL Viewer

Read the valid records in a JSONL export and see which lines need attention.

Stays on your computerNo accountSQL includedJoin across files

Find what is usable in a broken JSONL export

A few bad lines should not make the useful records unreadable. Here it takes three steps:

  1. 1Drop the .jsonl or .ndjson export in.
  2. 2See the valid records as a table and the bad lines by number.
  3. 3Use SQL to isolate the records you need, then export CSV or JSON.

What it can do, and where it stops

Why JSON Lines needs its own viewer

One JSON value per line is what makes the format streamable — and what makes a single bad line break a whole-file parse. So it is read line by line:

  • How many lines are valid data, and which ones are not
  • Column types inferred across the whole file, not guessed from the first record
  • Nested objects kept as objects
  • Keys a JSON viewer usually mangles: dots, spaces, empty names

Nothing leaves the tab

The file is opened from your disk and read where it sits, so there is no upload and no copy on a server. Queries are read-only, which means the file you opened is the file you still have, and closing the tab leaves nothing behind.

Prefer to keep a .jsonl or .ndjson file in your editor?

The browser is for a quick answer. Install the local viewer in your editor to keep working with the file beside your code.

From one file to a complete data workflow

Open JSON Lines locally, then move on to compressed files, S3, databases, and repeatable conversion workflows with DBConvert Streams.