¿Odias los anuncios? Ir Sin publicidad Hoy 

Access Log Formatter (Apache / Nginx)

DatosDesarrolladorRedes

APORTE

Proceso automático

PROD.

Lado cliente

Paste log lines on the left to see them parsed here.

IP	Date/Time	Método	Camino	Estado	No — rompe el shebang	Referrer	User-Agent
El resultado aparecerá aquí

ANUNCIO · ¿ELIMINAR?

Guía

Access Log Formatter (Apache / Nginx)

Paste raw Apache or Nginx access log lines and instantly turn them into a structured, sortable table. The Access Log Formatter detects whether each line is in the Common Log Format (CLF) or Combined Log Format (Apache’s default), then breaks every entry into clean columns: IP, date/time, method, path, status code, bytes, referrer, and user agent. Filter the result by status code group, sort any column with one click, and export only the rows you care about as CSV.

Cómo Usar

Paste your raw access log lines into the input box, or upload a log file.
Leave Log Format on Auto-detect, or pin it to CLF or Combined if your server uses a fixed format.
Utiliza el Status Filter dropdown to narrow results to a specific status group (for example, 4xx Client Error when hunting broken links).
Click any column header to sort by IP, date/time, status, bytes, or any other field.
Haz clic en Descargar CSV to save the currently visible rows for further analysis in a spreadsheet.

Características

Auto-detects CLF and Combined – No need to know your log format up front; both Apache and Nginx defaults are recognised automatically.
Sortable columns – Click any header to order rows by IP, date, status, response size, and more.
Status code filters – Quickly isolate 2xx success, 3xx redirects, 4xx client errors, or 5xx server errors.
Visual status colouring – Status codes are colour-coded so anomalies stand out at a glance.
CSV export of filtered rows – Download exactly what you see, ready to drop into Excel, Sheets, or Pandas.
Soporte para carga de archivos – Drag and drop a log file instead of pasting lines.
Funciona completamente en tu navegador – Logs never leave the page, so sensitive IPs and request paths stay local.

 Preguntas frecuentes

What is the difference between Common Log Format (CLF) and Combined Log Format?

Common Log Format records the client IP, RFC 1413 ident, authenticated user, request timestamp, the request line, the HTTP status code, and response size in bytes. Combined Log Format adds two extra quoted fields at the end: the Referer header and the User-Agent header. Apache's default access log uses Combined; Nginx ships with a similar default it calls 'main', which is also Combined-compatible.
Why does an access log entry sometimes show a dash instead of a value?

A single hyphen ('-') in an access log means the field was not available. RFC 1413 ident is almost always a dash because the protocol is virtually unused, and the authenticated user is a dash for any unauthenticated request. The Referer and User-Agent are dashes when the client did not send those headers. The response size is a dash on requests that returned no body, such as a 304 Not Modified.
What do HTTP status code groups (1xx, 2xx, 3xx, 4xx, 5xx) mean?

Each digit class signals a category of response. 1xx is informational (rare in access logs), 2xx is success, 3xx is redirection, 4xx indicates a client-side error such as a missing resource or unauthorised request, and 5xx indicates a server-side error such as an internal exception or upstream failure. Filtering by group is a fast way to surface broken links (4xx) or backend incidents (5xx).
Why are access log timestamps wrapped in square brackets with an offset like -0700?

The Common Log Format timestamp uses the strftime pattern '[day/month/year:hour:minute:second zone]' where the zone is the server's offset from UTC. The square brackets and the trailing offset are part of the format itself, which is why parsers must treat the whole bracketed expression as one field. Storing the offset means the timestamp can be interpreted unambiguously even if the server later moves time zones.