Microdeck.tools 100% In-Browser

NDJSON / JSON Lines Explorer & Filter

New

Inspect structured application logs, Cloudflare Workers tail traces, or LLM fine-tuning `.jsonl` datasets locally. Parses up to 10,000 JSON Lines into an auto-discovered column table, highlights corrupt/truncated lines without crashing, supports field-specific filtering (`status:500` or text), and exports filtered subsets to CSV, JSON arrays, or NDJSON.

100% In-Browser No Server Storage Instant Results
NDJSON / JSON Lines Input (4 valid, 1 malformed)
#tslevelservicelatencyMsstatusmsg
12026-11-15T08:01:02Zinfoauth14200—
22026-11-15T08:01:05Zwarnbilling420429—
32026-11-15T08:01:09Zerrorworker982500timeout
4Malformed line: {malformed json line (Expected property name or '}' in JSON at position 1 (line 1 column 2))
52026-11-15T08:01:12Zinfoedge9200—

Did this tool save you time? Help keep Microdeck free and maintained. Completely optional · From $3.

How It Works Under the Hood

Splits raw input line-by-line (skipping blanks), attempts `JSON.parse()` independently on each record so one corrupted log line never breaks parsing of surrounding events, unions all object keys into table columns, and evaluates `field:value` or substring search queries live.

Step-by-Step Instructions

1

Paste streaming `.ndjson` / `.jsonl` log lines into the top editor.

2

Check valid vs malformed counts and optionally toggle "Hide malformed lines".

3

Filter rows using plain keywords (`timeout`) or column queries (`service:billing status:429`).

4

Choose `CSV`, `JSON Array`, or `NDJSON` and copy or export your filtered subset.

Key Features & Performance

  • Fault-tolerant per-line JSON parser isolates malformed lines in red without failing the batch
  • Automatic schema column discovery builds a unified table even when log lines carry varying keys
  • Instant `key:value` and free-text filtering across parsed columns
  • Exports filtered records cleanly as RFC CSV, JSON array, or cleaned NDJSON
  • 100% browser-side: safe for production request traces, IP addresses, and auth event logs

Methodology, Formulas & Technical Standards

Supports up to `10,000` records per session in-memory with space-separated `column:substring` AND-conjunction filtering and recursive `JSON.stringify` display for nested object cells.

Common Real-World Use Cases

  • Inspecting JSON-formatted backend logs (`pino`, `winston`, `slog`) during incident triage
  • Cleaning and previewing OpenAI/Anthropic fine-tuning `.jsonl` prompt files before training
  • Extracting `status:500` error rows into a clean CSV spreadsheet for bug tracking
  • Spotting truncated JSON lines caused by unbuffered stream crashes

Worked Examples & Edge Cases

Mixed Good & Corrupt Stream

Input
4 valid log events + 1 truncated `{malformed json line`
Output
4 valid parsed into columns [ts, level, service, latencyMs, status, msg] + line 4 highlighted inline

Corrupt lines remain visible for debugging until "Hide malformed" is checked.

Targeted Log Export

Input
Filter: `service:worker` -> Format: CSV
Output
CSV table containing only matching worker event rows

Missing optional keys in sparse rows render cleanly as blank CSV cells.

Limitations, Scope & Accuracy Notes

  • • Capped at `10,000` lines in the browser textarea to guarantee snappy interactive filtering.
  • • Nested sub-objects inside log columns display serialized JSON strings in CSV/table cells rather than flattening dot-columns recursively.

Local Browser Processing & Privacy

Traditional web converters upload your documents, snippets, or media files to remote servers. NDJSON / JSON Lines Explorer & Filter runs inside your browser tab:

Processed in This Tab

Your input text and files are processed locally without uploading payloads to a processing server.

No Tool Payload Logging

Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).

Tab Memory Lifecycle

Working outputs stay in your browser tab and are released when you reset the tool or close the tab.

Frequently Asked Questions

What happens if one line in my `.jsonl` file is broken JSON?

Unlike `JSON.parse()` on an array, each line parses independently — the broken line is flagged with its exact line number and parser error while valid lines still render.

How does `key:value` filtering work?

Typing `level:error service:worker` matches only rows where both `level` contains `error` and `service` contains `worker` (case-insensitive).

Can I convert `.ndjson` to a standard JSON `[...]` array?

Yes. Select `JSON Array` in the export dropdown and click Copy or Export.

Are IP logs or access tokens sent to a server?

Never. All parsing, filtering, and CSV generation occur locally in JavaScript.

Explore Related Micro-Tools

Support Microdeck

Completely optional · From $3 · No account required

Choose an amount (USD):Selected:$5

Minimum support amount is $3 USD.

Completely optional · From $3 · Checkout opens on Gumroad.