NGINX Access Log Parser
Parse NGINX combined-format access log lines into structured fields: client IP, timestamp, request, status code, response size, referrer and user agent.
About this tool
Parse NGINX combined-format access log lines into structured fields: client IP, timestamp, request, status code, response size, referrer and user agent.
Example
Input: 127.0.0.1 ... "GET /x" 200 2326
Output: IP: 127.0.0.1 | Request: GET /x | Status: 200
Privacy
This tool runs entirely in your browser. Your data is processed locally and never uploaded to a server.
How to use this tool
- Paste one or more NGINX combined access log lines into the input area.
- Make sure each line follows the standard combined format with IP, timestamp, request, status, size, referrer, and user agent.
- Run the parser to convert the raw text into structured fields.
- Copy or inspect the parsed output and use the fields you need in your app, script, or analysis.
Step by step, what happens
- The tool reads each log line as plain text and looks for the combined access log pattern.
- It splits the line into separate fields such as client IP, timestamp, request, status code, response size, referrer, and user agent.
- It keeps the original values intact, including spaces inside the request, referrer, and user agent strings.
- If a line does not match the expected format, the parser can only extract what is present and may leave some fields empty or unparsed.
Worked example
Here is a typical NGINX combined log line for a page request from a browser.
Input: 203.0.113.10 - - [18/Jun/2026:14:22:31 +0000] "GET /index.html HTTP/1.1" 200 512 "https://example.com/" "Mozilla/5.0"
- The parser detects the client IP at the start of the line.
- It extracts the timestamp, request text, status code, response size, referrer, and user agent from the combined format.
- Each value is returned as a separate structured field so you do not need to split the line yourself.
Output: {"client_ip":"203.0.113.10","timestamp":"18/Jun/2026:14:22:31 +0000","request":"GET /index.html HTTP/1.1","status_code":200,"response_size":512,"referrer":"https://example.com/","user_agent":"Mozilla/5.0"}
Tips and common mistakes
- Use full combined-format lines, not shortened custom log formats, if you want every field parsed correctly.
- Keep the request, referrer, and user agent wrapped in quotes exactly as NGINX writes them.
- If your logs use a dash for missing values, leave it as-is so the parser can preserve that missing field.
- Check the timestamp format before parsing, because mixed log formats in the same input can make results harder to trust.
Frequently asked questions
Which log format?
The Apache/NGINX Common and Combined log formats.
What fields are extracted?
IP, time, request line, status, size, and (if present) referrer and user agent.
Is data uploaded?
No, parsing is local.
More Developer Tools Tools
Explore related calculators in this category
Apache Log Parser, Free Online Developer Tool
Parse Apache/NGINX combined access log lines into IP, time, request, status and size fields. Get instant results, the formula, and a clear example.
Cron Parser
Parse a cron expression into a plain-English description of when it runs.
Data URI Parser
Parse a data: URI to reveal its MIME type, encoding and decoded content. Free online data URI inspector.
HTTP Header Parser
Parse raw HTTP headers into clean key-value pairs. Free online HTTP header parser.
You Might Also Like
Popular tools from other categories
Natural Log Calculator
Calculate the natural logarithm (base e) of a number.
User Agent Parser
Parse a user-agent string into browser, OS and device.
1031 Exchange Calculator - Free Online
Free Calculate tax deferral in a 1031 exchange. Step-by-step solutions and formulas included. Fast, accurate, and free, with formula and example.
4% Rule Calculator
Find the retirement nest egg you need using the 4% safe-withdrawal rule.
Can't Find the Right Calculator?
Try our AI Math Solver, type any problem in plain English and get instant step-by-step solutions.