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
Frequently Asked Questions
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.
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.
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.
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.