Skip to the tool
GigaJSON

JSON Lines and NDJSON Viewer

All tools
Format and check
View and query
Convert
JSON to code
Encode and decode
Sample files
Guides Open GigaJSON
Input JSON Lines
Ready Runs in your browser

Open a JSON Lines file (JSONL or NDJSON, one JSON value per line), such as a log, a database export or a machine learning dataset. Each line becomes a row of a table you can sort and filter, and the tree, the formatted text and a query panel are one click away. Files up to 1 GB open without being uploaded. To turn the lines into one JSON array, use JSON Lines to JSON.

How to use it

  1. Open a .jsonl or .ndjson file, or paste the lines.
  2. The lines appear as a table, one row per line. Switch to Tree to browse the nested fields, or use Find.
  3. Use Query for JSONPath or JMESPath across all the lines, or "Open in GigaJSON" to edit or convert the file.

Read more: Convert JSON to JSON Lines (JSONL) and back

Private, and made for big files

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.

Read JSONL logs as rows

JSON Lines, also called NDJSON, has one complete JSON value on each line. There is no surrounding array and no comma between lines:

{"level":"info","status":200,"duration_ms":42}
{"level":"error","status":503,"duration_ms":1200}
{"level":"info","status":200,"duration_ms":61}

Open these records in Table view to compare status and duration. In Query, use JSONPath $[?(@.status >= 500)] to select the error record. The viewer treats the lines as a list for browsing and querying. A newline inside a JSON string must be escaped as \n; a broken line needs correction before the document can be parsed.

Large logs still need enough device memory. To exchange a conventional JSON array, use JSONL to JSON. The API and log guide includes command-line ways to filter before opening a huge file.

GigaJSON Table view showing three JSONL log records with status and duration columnsGigaJSON Table view showing three JSONL log records with status and duration columns (dark theme)
One JSON object per line becomes one row. These example logs contain a 503 response. Screenshots follow the page theme. Click to view full size.

Questions

What is the difference between JSON Lines and NDJSON?

They're two names for the same format: one complete JSON value per line, with no commas between lines and no brackets around them. .jsonl is the usual file extension.

What happens to a bad line?

The viewer stops and tells you the line number and what's wrong with it, so you can fix the file. Blank lines are skipped.

How large a file can it handle?

JSON, XML and CSV input can be up to 1 GB, depending on memory. YAML input and JSON repair are limited to 128 MB. Parsing runs in a background worker. jq, text editing and text-based exports have separate limits, shown when you use them.

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