MyJSON
Stream inspection

NDJSON, JSONL, JSON Lines — viewed clean.

Every log pipeline emits one JSON object per line. MyJSON detects NDJSON automatically and lets you flip between line-stream view, JSON-array view, and structured tree view.

Runs entirely in your browser

Auto-detection

Paste your log stream — MyJSON spots NDJSON and offers to wrap it as a JSON array with one click.

Tree view, per record

After wrapping, each record becomes a navigable subtree. Use Ctrl+F to search across the whole stream.

Round-trip safe

Convert NDJSON → JSON array → back to NDJSON for export. Useful for slicing log dumps.

Privacy-first

Log payloads often contain user data. Everything stays in your browser — open DevTools to verify.

FAQ

What's the difference between NDJSON, JSONL, and JSON Lines?
All three names refer to the same format: one independently-valid JSON value per line, separated by newlines. JSONL is the most-used name in 2026.
Will this handle massive log dumps?
Practical limit today is around 25 MB without going to streaming mode. For multi-gigabyte logs, slice before pasting.
Why isn't this just a Tree view?
Because the editor treats input as a single document by default. NDJSON detection adds a banner that flips a wrapper so the rest of the workstation lights up.

Related tools