Log Format Parser (Apache, Nginx, JSON, syslog)
You have log lines on the clipboard and want them as a table — to filter, sort, or paste into a spreadsheet. This parser handles the most common formats: Apache Common / Combined Log Format, Nginx default, JSON Lines (one JSON object per line, e.g. from jq or structured logging), and RFC 5424 syslog. Auto-detects format or pick manually.
How to use the Log Format Parser (Apache, Nginx, JSON, syslog)
Paste log lines (one per line). Pick a format or leave on auto-detect. The output table shows parsed columns for each line — IP, user, timestamp, method, path, status, size, referrer, user-agent for HTTP logs; structured JSON keys for JSON logs.
About Log Format Parser (Apache, Nginx, JSON, syslog)
Common log formats:
- Apache Common —
%h %l %u %t "%r" %>s %b. The default for Apache 1.x. Example:192.168.1.42 - alice [28/May/2026:14:32:01 +0000] "GET /api/users HTTP/1.1" 200 1543 - Apache Combined — Apache Common +
"%{Referer}i" "%{User-agent}i". Modern default. - Nginx default — virtually identical to Apache Combined.
- JSON Lines (ndjson) — one JSON object per line. Modern structured logging (logrus, zap, pino, slog, Pythoner's logging-as-json).
- syslog (RFC 5424) —
<PRI>VERSION TIMESTAMP HOSTNAME APP-NAME PROCID MSGID STRUCTURED-DATA MSG.
For unparseable lines (mixed formats, custom formats), the tool falls back to showing the raw line in a "raw" column so you can spot which lines didn't match.
Common use cases
- Quick log analysis — paste a few hundred lines and sort / filter visually.
- Spreadsheet export — copy the parsed table into Google Sheets / Excel.
- Format discovery — figure out which format an unfamiliar log uses.
- Incident triage — quickly extract the failing requests from a window of access logs.