Skip to the tool
GigaJSON JSON Log Viewer
All tools
Format and check
View and query
Convert
JSON to code
Encode and decode
Sample files
Guides Open GigaJSON

JSON Log Viewer

Open JSON Lines logs up to 1 GB. Count errors by level, service or status, then filter and query the lines. Nothing is uploaded.

Drop a JSON Lines file here
.jsonl, .ndjson or .log with one JSON object per line, up to 1 GB · read on this device
or · CloudWatch, Kubernetes, Docker and app logs
Lines: up to 1 GB (512 MB by default)JSONPath, JMESPath: any size that opensjq: 20 MB

Open a structured log file, one JSON object per line, from Kubernetes, Docker, journald, CloudWatch or your own app. The viewer opens on an overview of the fields: pick level, service or status to see how many lines have each value, then click a value to list just those lines. The table sorts and filters, Find searches every line, and Query runs JSONPath or JMESPath across the file. Files up to 1 GB open, and nothing is uploaded. For other JSON Lines data, the JSON Lines Viewer opens on the table. To cut a big log into smaller files, use the JSON Splitter.

How to read a JSON log file

  1. Open a .jsonl, .ndjson or .log file with one JSON object per line, or paste lines.
  2. The Overview lists the fields. Pick one, such as level, to count the lines per value, and click a value to filter the table to those lines.
  3. Search with Find, or use Query for JSONPath or JMESPath across all the lines.

Log files stay on your computer

This tool runs in your browser, in a background worker: nothing you paste or open is uploaded, and nothing is kept after you leave. JSON and XML input can be up to 1 GB, depending on available memory. Processing runs in a background worker; large analyses can take a minute or more. Already loaded features keep working if your connection drops. Loading another tool or jq for the first time needs a connection. When one tool isn't enough, GigaJSON opens your data with a tree, a table, JSONPath/JMESPath/jq queries, transforms, diff and history.

Getting logs as JSON Lines

These commands save logs in the format this page opens. The application has to log JSON itself for the first two.

JSON log viewer questions

How do I count the errors in a log file?

Open the file, then pick the level field (or status, or service) in the Overview. It lists each value with its share of the lines. Click error to see only those lines in the table.

What log formats does it read?

JSON Lines: one JSON object per line, which is what most structured loggers write (pino, bunyan, zap, logrus with the JSON formatter, Serilog's compact JSON, Python's json loggers). Plain text lines aren't JSON, so a file that mixes the two stops at the first plain line and says its number.

How large a log file can it open?

Up to 1 GB, depending on your computer's memory. The default limit is 512 MB; for bigger files, choose 1 GB in Preferences → Largest document, or confirm when the page asks.

Can I search the logs?

Yes. Find searches every key and value and shows the first 5,000 matches with the total. Query runs JSONPath or JMESPath, such as $[?(@.level == "error")].message, on the whole file, and jq on files up to about 20 MB.

Is my data uploaded?

No. The tool runs in your browser, in a background worker. Nothing you paste or open goes to a server, and nothing is kept after you leave the page.

All tools