Open line-delimited JSON

  1. Choose a .jsonl or .ndjson file.
  2. Search the table for a record, then sort by a column.
  3. Click nested values to inspect them, or flatten nested objects into columns.
  4. Export the filtered records as CSV when you need a simpler table.
{"id":101,"owner":{"name":"Alex"},"status":"ready"}
{"id":102,"owner":{"name":"Sam"},"status":"waiting"}

Each nonblank physical line must contain one complete JSON value. Blank lines do not become records. Original source line numbers remain available in inspection, so a record can be traced back to the file.

Why does pretty-printed JSON fail?

A JSON object split over several lines is valid in a .json document, but it is not a complete JSONL record on each line. Select JSON when pasting a multiline document, or obtain a correctly named .json export. Malformed JSONL stops loading and reports the exact line; records are not silently dropped.

Different records can have different fields

An event export may mix record shapes. Missing fields can produce empty table cells, while nested arrays remain inspectable. Table limits are 100,000 records and 200 columns. This is local inspection, not streaming ingestion or a database query engine.

Your browser does the parsing and searching. Larger files can take longer, but their content is not uploaded. See how to inspect nested JSON for a worked example.

Credit to the format’s makers

The JSON Lines community builds on JSON’s simple value model with a useful convention: one complete value per line. That makes individual records easier to identify in exports and event data.

Format reference: JSON Lines documentation. Reference checked 7 October 2026. These links acknowledge the format; they do not imply endorsement or a partnership.