JSON Lines Viewer

Inspect JSON Lines as numbered, typed records with an expandable record preview.

Processing stays in this browser. Inputs are not uploaded.

At most 200,000 input characters, 10,000 records, 20,000 JSON values and 64 nesting levels per record. Duplicate keys and unsupported numeric magnitudes are rejected; decimal precision may change.

Each input line must contain one JSON value. LF or CRLF is supported; one final newline is allowed. Blank records, a leading BOM and standalone CR are rejected.

Inspect a stream of JSON records

Paste JSON Lines and choose View records. The table shows a record number, JSON type and a shortened preview. Select a record number to inspect its complete formatted value. Previous and Next move through 20 records at a time; changing page does not change the selected record automatically.

Example: three different types

Load example (replaces inputs) inserts an object with id 1, the boolean true, and null on separate lines. Processing reports three records. The type column distinguishes object, boolean and null; null is not mislabeled as an object. Select record 1 to inspect the object's id property.

Validation and interpretation

The viewer checks every record before showing a result. An invalid record stops processing and reports its one-based line number; it does not skip bad lines or claim the remaining data is complete. This checks JSON syntax and the reader's stated limits, not a domain schema. A syntactically valid record can still lack fields your application requires.

The preview abbreviates each compact value after 120 characters. The selected-record area retains the entire value, and the normalized download contains all records, not only the current page. Downloading reserializes parsed values rather than preserving the source bytes.

Use JSON Pointer Resolver to inspect a branch of one copied record, or JSON Lines Splitter to divide a validated stream into smaller files.

Input and numeric limits

Processing is local and edits clear stale results. JSON Lines inputs accept LF and CRLF, with one optional final newline. Blank records, a leading BOM and standalone CR are rejected. Browser textareas may normalize pasted line endings before the parser receives them. Pretty-printed multiline objects must first be put on one line per record.

The reader rejects duplicate object keys, nonfinite numbers, unsafe integers, and nonzero numbers such as 1e-400 that become zero at JavaScript precision. Other decimals still use floating-point arithmetic; negative zero and numeric spelling can normalize. Store exact identifiers or precision-sensitive decimal text as strings. Each record is limited to 64 nesting levels; input is limited to 200,000 characters (combined when merging), 10,000 records and 20,000 values. Output is capped at two million characters. Input stays in memory and is lost on reload.