JSON log viewer for NDJSON files

NDJSON (JSON lines) logs put one JSON object on each line. This viewer reads the file in your browser, shows each line as a row and lets you filter by level or any field.

[LOCAL] Runs in your browser. Your files stay on your device and nothing is uploaded.

or drop one here. Now showing: Example log

9 lines, 8 valid JSON objects, 1 not JSON

Level

Field filters are separated by spaces: key:value matches exactly, key~text contains, !key:value or !key~text excludes, key alone means the field exists and !key that it is missing. Nested fields use dots; put values with spaces in quotes, like msg:"request completed".

Fields (check to hide the noisy ones)
9 of 9 lines match

Level numbers by logger

How numeric log levels map to names
Shown asPino / Bunyan numberNames recognized
[FATAL]60fatal, panic, emerg, alert
[ERROR]50error, err, severe, critical
[WARN]40warn, warning
[INFO]30info, notice, log
[DEBUG]20debug, dbg
[TRACE]10trace, verbose, silly

How to use it

  1. Choose a .log, .ndjson or .jsonl file, drop it on the box, or paste lines into the text area. The example log loads first so you can see the layout.
  2. Untick levels you do not need. Pino and Bunyan numbers (30, 50, 60) and names like warn, ERROR and severity fields are all read as levels.
  3. Type field filters such as res.status:500 or !service:worker to keep or drop lines by a nested field, and use Search text to match anywhere in the line.
  4. Tick fields in the Fields list to hide them from every row, which collapses noise like request ids and hostnames.
  5. Click a row to see the full object, then copy or download the matching lines as a new NDJSON file.

Questions

What is NDJSON?
NDJSON, also called JSON lines or JSONL, is a text format with one complete JSON object per line and no commas between lines. Loggers like pino, Bunyan, structlog and Winston write it because each line can be read and appended on its own.
Which level and message fields does the viewer recognize?
Levels are read from level, severity, lvl, levelname, log.level or Serilog's @l, as names or pino and Bunyan numbers. Messages come from msg, message, event, log or text, and times from time, timestamp, ts, @timestamp or datetime. Epoch times in seconds or milliseconds, like pino's default, are shown as UTC dates. Every other field stays available for filtering.
What happens to lines that are not JSON?
They are counted and shown as [RAW] rows so stack traces and stray print statements are not lost. Untick the non-JSON lines box to hide them, or search them like any other line.
How big a file can it open?
The viewer opens files up to 256 MB, shows the first 50,000 lines and tells you how many more the file had. Everything is parsed in your browser tab, so speed depends on your device. For bigger logs, cut the file down with grep or tail first and load the result.
Is my log uploaded anywhere?
No. The file is read with your browser and filtering happens in the page. Nothing is sent to a server, so logs with customer data stay on your device.

More free tools