Open a structured log file, one JSON object per line, from Kubernetes, Docker, journald, CloudWatch or your own app. The viewer opens on an overview of the fields: pick level, service or status to see how many lines have each value, then click a value to list just those lines. The table sorts and filters, Find searches every line, and Query runs JSONPath or JMESPath across the file. Files up to 1 GB open, and nothing is uploaded. For other JSON Lines data, the JSON Lines Viewer opens on the table. To cut a big log into smaller files, use the JSON Splitter.
How to read a JSON log file
- Open a .jsonl, .ndjson or .log file with one JSON object per line, or paste lines.
- The Overview lists the fields. Pick one, such as level, to count the lines per value, and click a value to filter the table to those lines.
- Search with Find, or use Query for JSONPath or JMESPath across all the lines.
Log files stay on your computer
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.
Getting logs as JSON Lines
These commands save logs in the format this page opens. The application has to log JSON itself for the first two.
- Kubernetes:
kubectl logs my-pod > app.jsonl - Docker:
docker logs my-container > app.jsonl. Docker's default json-file driver also keeps each container's log as JSON Lines under/var/lib/docker/containers/. - systemd journal:
journalctl -u my-service -o json > journal.jsonl - AWS CloudWatch Logs:
aws logs filter-log-events --log-group-name my-group --output json | jq -c '.events[]' > events.jsonl. Without jq, save the JSON as it comes and open it in the Large JSON Viewer.
JSON log viewer questions
How do I count the errors in a log file?
Open the file, then pick the level field (or status, or service) in the Overview. It lists each value with its share of the lines. Click error to see only those lines in the table.
What log formats does it read?
JSON Lines: one JSON object per line, which is what most structured loggers write (pino, bunyan, zap, logrus with the JSON formatter, Serilog's compact JSON, Python's json loggers). Plain text lines aren't JSON, so a file that mixes the two stops at the first plain line and says its number.
How large a log file can it open?
Up to 1 GB, depending on your computer's memory. The default limit is 512 MB; for bigger files, choose 1 GB in Preferences → Largest document, or confirm when the page asks.
Can I search the logs?
Yes. Find searches every key and value and shows the first 5,000 matches with the total. Query runs JSONPath or JMESPath, such as $[?(@.level == "error")].message, on the whole file, and jq on files up to about 20 MB.
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