Massive Log File Grep & Timeline Visualizer

Massive Log File Grep & Timeline Visualizer

Click or drag a .log/.txt file here, or paste text below

Finding the Moment Things Went Wrong

Scrolling through a gigabyte-scale log file looking for a spike in errors is slow and easy to miss. This tool parses timestamps out of common log formats (ISO 8601, Apache/nginx access-log brackets, and syslog's "Mon DD HH:MM:SS" style) and renders a timeline histogram showing event density over time - so a spike in activity, or a cluster of errors right before an outage, is visually obvious instead of buried in scroll.

Combine that with the text/regex filter to narrow down to just the lines you care about (a specific request ID, an error code, a hostname) and watch the timeline update to show exactly when those filtered events happened.

What This Tool Does

Timeline Histogram48 time buckets spanning your log's full time range, showing where event density spikes.
Text or Regex FilteringNarrow the log list (and the timeline) down to only lines matching a search term or a full regular expression.
Error/Warning HighlightingLines containing ERROR/FATAL or WARN/WARNING get a colored left border so they stand out while scrolling.
Drag-and-Drop File LoadingDrop a .log or .txt file directly - it's read locally, never uploaded anywhere.

Frequently Asked Questions

Does this tool upload my log file anywhere?

No - the file is read locally using the browser's FileReader API and every calculation (timestamp parsing, filtering, the timeline histogram) runs entirely in JavaScript in your browser. Nothing is uploaded to a server.

What timestamp formats does it recognize?

ISO 8601 (2026-09-17T08:12:03 or with a space instead of T), Apache/nginx access-log bracketed format ([17/Sep/2026:08:12:03), and syslog-style (Sep 17 08:12:03, which assumes the current year since syslog doesn't include one). Lines without a recognized timestamp still show in the log list, just aren't counted in the timeline.

How large a log file can I load?

There's no hard upload size limit since everything stays local, but the log list only renders the first 2,000 matching lines at a time to keep the page responsive - narrow your filter to see specific sections of a much larger file.

What counts as an "error" or "warning" line?

Any line containing the whole word ERROR, FATAL, or CRITICAL (case-sensitive on the word boundary) is treated as an error; WARN or WARNING as a warning - this is a simple keyword match, not a parser for any specific logging framework's exact format.