Sample web server access log (500 lines)
Five hundred request lines in Combined Log Format, as written by nginx and Apache, with a realistic mix of methods, paths and status codes.
Download
sample-access.log
80.2 KB82,141 bytes
Download LOG sampleDirect download. No sign-up and no waiting.
- Type
- text/plain
- SHA-256
c671ae4e10d829bd0db8cf25fa6df29b7ec50c41e408b35ee5e9705d0c62fe99- Direct URL
https://sampletestfiles.com/downloads/samples/sample-access.log
Why test with this file
For testing log parsers, dashboards, alert rules and regular expressions.
| Lines | 500 |
|---|---|
| Format | Combined Log Format |
| IP addresses | Documentation ranges from RFC 5737 |
| Line endings | LF |
| Encoding | ASCII |
What to check
After your application has processed sample-access.log, confirm that:
- All 500 lines match your parsing pattern.
- Status codes are aggregated correctly, including the 404 and 500 responses.
- Timestamps keep their +0000 offset.
How the file begins
The opening lines of sample-access.log, exactly as they appear in the file.
192.0.2.239 - - [01/Jan/2026:00:00:00 +0000] "GET /assets/app.js HTTP/1.1" 200 4759 "https://example.com/" "ExampleMonitor/1.0"
198.51.100.123 - - [01/Jan/2026:00:00:01 +0000] "GET /favicon.ico HTTP/1.1" 500 33395 "https://example.com/" "curl/8.5.0"
192.0.2.55 - - [01/Jan/2026:00:00:03 +0000] "GET /favicon.ico HTTP/1.1" 404 10647 "https://example.com/" "ExampleMonitor/1.0"
198.51.100.184 - - [01/Jan/2026:00:00:05 +0000] "GET /assets/app.css HTTP/1.1" 200 36767 "https://example.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:12…
203.0.113.34 - - [01/Jan/2026:00:00:06 +0000] "GET /index.html HTTP/1.1" 204 19807 "https://example.com/" "ExampleMonitor/1.0"
203.0.113.75 - - [01/Jan/2026:00:00:08 +0000] "GET /downloads/report.pdf HTTP/1.1" 304 8816 "https://example.com/" "ExampleMonitor/1.0"Preview
Shows the first 64 KB of the file.
Technical details
| File name | sample-access.log |
|---|---|
| Format | LOG (Log file) |
| Extension | .log |
| MIME type | text/plain |
| Size | 82,141 bytes (80.2 KB) |
| Kind | Text |
| SHA-256 | c671ae4e10d829bd0db8cf25fa6df29b7ec50c41e408b35ee5e9705d0c62fe99 |
| Created | 2026-10-10 |
| Validation | Exact size, signature bytes and structure checked when the file was generated |
| Preview | Available on this page |
| Source | Generated for this site; not copied from elsewhere |
| Licence | Free to use, modify and redistribute (terms) |
| Category | Testing |
Validated for expected format and integrity. As with any download, scan the file with your own security tools before opening it. How files are made and checked
Download from the command line and verify
Fetch the file with curl, then compare its checksum with the SHA-256 value above.
curl -o sample-access.log 'https://sampletestfiles.com/downloads/samples/sample-access.log'
sha256sum sample-access.log # Linux
shasum -a 256 sample-access.log # macOSOn Windows, run Get-FileHash sample-access.log -Algorithm SHA256 in PowerShell. A matching value proves that the download is complete and unaltered.
About LOG
Line-oriented text records of events. The samples use the web-server Combined Log Format.
Where it fits
- File parser testing
Well-formed files and deliberate edge cases for testing code that reads CSV, JSON, XML, PDF and more.
- CI/CD pipelines
Fixtures for build, test and deployment pipelines, with checksums for verification.