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
- Open a .jsonl or .ndjson file, or paste the lines.
- The lines appear as a table, one row per line. Switch to Tree to browse the nested fields, or use Find.
- 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.


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
- JSON FormatterIndent with 2 or 4 spaces, sort keys
- JSON ValidatorLine and column of the first error
- JSON MinifierRemove whitespace, see the bytes saved
- JSON RepairFixes quotes, commas, comments, AI output
- JSON Schema GeneratorA JSON Schema from examples
- JSON Schema ValidatorCheck JSON against a schema
- JSON Token CounterCount tokens, select data, compare JSON and TOON
- JSON EditorTree and code editing, undo and history
- Large JSON ViewerTree, table and search for huge files
- JSON Lines ViewerJSONL and NDJSON logs as a table
- JSON Log ViewerCount and filter JSON Lines logs
- Large CSV ViewerCSV files too big for Excel, up to 1 GB
- JSON VisualizerThe data as a graph, PNG and SVG export
- JSON DiffChanges between two documents
- JSON Path FinderClick a value, copy its path
- JSONPath TesterJSONPath, JMESPath and jq, live
- JMESPath PlaygroundJMESPath, for AWS CLI queries too
- jq PlaygroundReal jq in your browser
- JSON to CSVNested objects become dotted columns
- JSON to ExcelAn .xlsx sheet, numbers kept as numbers
- CSV to JSONDelimiters detected, 007 stays 007
- JSON to XML@keys become attributes
- XML to JSONRSS feeds, sitemaps, SOAP responses
- JSON to YAMLReadable YAML, ambiguous strings quoted
- YAML to JSONAnchors and multiple documents
- JSON Lines to JSONNDJSON or JSONL into one array
- JSON to JSON LinesA JSON array as one record per line
- JSON to TOONConvert JSON to TOON, with token counts
- JSON to MermaidA flowchart or class diagram, drawn
- JSON SplitterCut a big file into parts, or sample it
- JSON to TypeScriptInterfaces inferred from your data
- JSON to GoGo structs with json tags
- JSON to RustRust structs that derive serde's Serialize and Deserialize
- JSON to PythonPython dataclasses with type hints
- JSON to JavaJava classes with getters and setters
- JSON to C#C# classes with System.Text.Json attributes
- JSON to KotlinKotlin data classes
- JSON to SwiftSwift structs that conform to Codable, with CodingKeys
- JSON to DartDart classes with fromJson and toJson
- JSON to ZodZod schemas with TypeScript types inferred from them
- JWT DecoderHeader, payload and expiry, locally
- JSON EscapeText to a JSON string and back
- Sample JSON FilesDownload test JSON, 100 KB to 1 GB
- Sample JSON Lines FilesDownload test NDJSON, one record per line
- Sample CSV FilesDownload test CSV, 100 KB to 1 GB
- Sample XML FilesDownload test XML, 100 KB to 1 GB
- Sample GeoJSON FilesPoints, lines and polygons, up to 1 GB
- Sample Nested JSONRecords 8 levels deep, up to 1 GB
- Sample Unicode JSON13 scripts, emoji and escapes
- Sample API ResponsesJSON:API, HAL, GraphQL, pages, errors
- Large JSON File GeneratorTest data from 100 KB to 1 GB