Access Log Formatter
Parse Apache/Nginx access log lines (Common Log Format or Combined Log Format) into a structured, filterable table — extract the IP, timestamp, method, path, status, bytes, referrer and user-agent from raw log text.
Input
Options
Auto-detect tries Combined Log Format first, then falls back to Common Log Format.
Output
| IP | Date/Time | Method | Path | Protocol | Status | Bytes | Referrer | User-Agent |
|---|---|---|---|---|---|---|---|---|
| No data yet | ||||||||
Guides
What does this tool do?
Paste raw web server access log lines and this tool turns them into a readable, structured table — one row per request, with separate columns for IP address, timestamp, HTTP method, path, protocol, status code, response size, referrer and user-agent. It supports both Common Log Format (CLF) — ip - - [date] "request" status bytes — and Combined (Extended) Log Format — CLF plus quoted referrer and user-agent fields — the default access log format written by Apache and Nginx.
Lines that don't match either format aren't discarded silently: they're counted as "could not be parsed" in the summary line above the table, so you always know how much of your paste was actually understood.
Who is it for?
- Developers and sysadmins eyeballing an access log without grepping through raw text.
- Security and support teams quickly filtering a log dump down to a status class (e.g. all
4xxor5xxrequests) to spot failed logins, broken links or server errors. - Anyone who wants a quick CSV export of parsed log rows for a spreadsheet.
How to use it
- Paste log lines into the text box, or drop a
.log/.txtfile onto the uploader — its contents sync straight into the box. - Choose a Log Format: leave it on Auto-detect (tries Combined first, then falls back to Common Log Format per line), or pin it to CLF/Combined if you know your format and want stricter matching.
- Use Status Filter to narrow the table to a status class — for example
4xxto isolate client errors. - The summary line reports how many lines parsed successfully and how many were skipped. Copy or download the table as CSV with the buttons on the output card.
FAQ
What's the difference between Common Log Format and Combined Log Format?
Common Log Format (CLF) has seven fields: IP, identity, user, timestamp, request line, status code and response size. Combined (Extended) Log Format is CLF plus two more quoted fields — the referrer and user-agent — and is what most Apache and Nginx installs write by default.
Why did some lines get skipped?
A line is skipped when it doesn't match the selected format's structure — for example, a line missing the [timestamp] brackets, missing quoted fields, or truncated mid-line. Try switching Log Format to match your log's actual format, or check for line-wrapping/copy-paste artifacts.
Does it handle multi-line log entries or JSON-formatted logs?
No — this tool expects one CLF/Combined-format request per line, the plain-text format written by default Apache/Nginx configurations. JSON-structured logs (e.g. from a custom log format) aren't parsed.
Can I export just the filtered rows?
Yes. Set Status Filter to the status class you want, then use the table's download button — only the currently visible (filtered) rows are exported.
Privacy
Parsing happens entirely in your browser. Your log lines are never uploaded or sent to a server.