Developer Tool

JSON Log Viewer: Read NDJSON Logs Easily

Transform messy newline-delimited JSON or Docker container outputs into clean, queryable tables in seconds.

Runs in your browser. Nothing is uploaded.
Invalid syntax
Log Stream 0 rows loaded
Time Level Message

Drop NDJSON or Container Logs Here

Paste from your clipboard, drop log files (up to 300MB), or try our realistic microservice logs.

Log Details No row selected

Select any row on the left to inspect its complete JSON tree, stack trace, and nested properties.

Use ↑ and ↓ keys to navigate records.

Copied!

How to Read and Query NDJSON Logs with Zero Setup

Modern backend systems, Kubernetes pods, and distributed services generate high-volume telemetry as structured JSON logs. However, reading thousands of raw lines via terminal buffers or rudimentary text editors makes incident triage slow and error-prone. This browser-based JSON Log Viewer provides an instantaneous, private workspace to analyze, filter, and inspect structured logs directly on your local machine.

How to Use in 4 Simple Steps

  1. Import Your Logs: Drag and drop any .log, .jsonl, or .ndjson file into the drop zone, or click Paste to insert directly from your clipboard.
  2. Filter by Severity: Click any of the color-coded level chips (ERROR, WARN, INFO, DEBUG) to isolate faulty requests or unexpected exceptions.
  3. Query Custom Fields: Use the query bar to filter with expressions such as status >= 500, user.id = 42, or free-text keywords with full regex support.
  4. Inspect Deep JSON Trees: Click any row in the virtualized table to inspect formatted stack traces, drill down into nested objects, and copy payloads for local debugging.

Example: Raw NDJSON vs Structured Table

Observe how raw newline-delimited logs are parsed into an organized, readable structure with automated timestamp normalization and severity tagging:

Raw Docker / Container Log (NDJSON)
2024-05-18T10:14:22Z stdout F {"level":"error","ts":1716027262000,"msg":"Database pool connection timeout","service":"billing-worker","error":{"code":"ETIMEDOUT","retries":3},"user":{"id":8491,"plan":"enterprise"}}
2024-05-18T10:14:23Z stdout F {"level":"info","ts":1716027263000,"msg":"Payment webhook received","service":"payments","event_id":"evt_98319"}
Parsed Table & Tree Inspector
[10:14:22]  [ERROR]  Database pool connection timeout
  ├─ service: "billing-worker"
  ├─ user.id: 8491
  └─ error.code: "ETIMEDOUT" (retries: 3)

[10:14:23]  [INFO]   Payment webhook received
  └─ event_id: "evt_98319"

Why Structured Logging Matters in Production

Traditional flat-text logs like [ERROR] user 42 failed to purchase item 99 force engineers to craft brittle regex strings to parse parameters. In contrast, structured logging outputs logs as newline-delimited JSON objects with typed keys (such as duration_ms, trace_id, http.status). This guarantees high auditability across microservice architectures.

Popular logging libraries across ecosystems—including Pino, Winston, and Bunyan in Node.js, Zap and Zerolog in Go, and Serilog in .NET—adopt NDJSON as their default output standard. This tool automatically recognizes standard field names across all major conventions.

Common Log Formatting Problems Handled Automatically

Log viewing tools often choke on real-world log discrepancies. This viewer is built to handle edge cases with resilient fallbacks:

Frequently Asked Questions

What is NDJSON?
NDJSON stands for Newline Delimited JSON, also known as JSON Lines (JSONL). In this format, each individual line is a standalone, valid JSON object without commas or wrapping array brackets. It allows continuous log streaming without needing to parse the entire file at once.
How do I read JSON logs?
Simply paste your log text or drop a file into this tool. The parser extracts timestamps, severity levels, and messages into responsive columns, allowing you to search, sort, and isolate errors immediately.
Does it support Docker and Kubernetes logs?
Yes! Container engines write raw stdout/stderr headers at the start of each line. This viewer strips container stream metadata automatically so you can inspect the clean JSON payload without manual cleanup.
Is my log data uploaded anywhere?
Never. The tool runs completely client-side in your browser. All parsing, filtering, and chart calculations occur inside your browser's JavaScript sandbox and Web Worker threads. No telemetry or log contents ever leave your device.
What file size limit does the viewer handle?
Thanks to streaming chunk parsing in a background Web Worker and DOM table virtualization, you can comfortably open log files up to 300 MB (over 500,000 log entries) without freezing your browser tab.

Related Developer Tools

Discover more free, privacy-first developer utilities built by MafLabs:

Export Filtered Logs

Choose your preferred export format for the current filtered log rows.

Keyboard Shortcuts

↑ / ↓Navigate log rows FToggle Fullscreen Focus Mode Ctrl + Shift + CCopy selected row JSON EscClose modal / Exit Focus Double click splitReset layout to 50/50