Drop in a log file — or paste one straight from a terminal. Detects the format (JSON Lines, Apache/Nginx access logs, syslog, or a generic timestamped format), checks whether it looks truncated, finds out-of-order timestamps and encoding damage, and breaks down log levels. Real evidence per line, not a guess.
If you're here because something threw one of these, this tool shows you exactly what's wrong and how much is recoverable:
Format detection covers JSON Lines (NDJSON), Apache/Nginx combined log format, syslog RFC 3164 and RFC 5424, and a generic leading-ISO-8601-timestamp format — anything else is analyzed only as plain text (line/blank counts, encoding, line endings), with no timestamp or level extraction. Syslog RFC 3164 timestamps don't carry a year, so the current year is assumed for ordering — treat the parsed dates as relative, not absolute. Log-level detection is a best-effort keyword/field match, not a parser for any particular logging library's format. Truncation is only flagged when the last line both fails to match the file's own detected format and the file doesn't end in a newline — a single malformed line in the middle of an otherwise-fine file is reported as an issue, not as truncation. The whole file is read into memory like every other tool here — very large logs (hundreds of MB+) may be slow, and detailed per-line issue lists are capped with a "+N more" note past the first 50.