Sample log files
Two made-up log files: 2,000 lines in the combined access-log format used by nginx and Apache, and 600 application log lines with levels and worker ids. Free, no sign-up. Updated 19 November 2026.
What these files are
Two made-up log files: 2,000 lines in the combined access-log format used by nginx and Apache, and 600 application log lines with levels and worker ids. The IP addresses are from the ranges reserved for documentation, so they belong to no one.
Status codes in the access log: 200: 1,527, 302: 94, 304: 74, 404: 213, 500: 92. Log levels in the application log: DEBUG: 147, ERROR: 36, INFO: 358, WARNING: 59.
Every file was generated by our own code, so nothing in them is copied from anyone, and we release them under CC0: use them for anything. The facts in the table were read back from each file after it was written, not typed in by hand.
About the format
The combined log format writes, in order: client IP, identity, user, the time in brackets, the request line in quotes, the status code, the response size in bytes, the referrer and the user agent. nginx uses it by default for access logs. The address blocks 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24 are reserved for documentation by RFC 5737.
These files open in text editors, less and grep. A web server should send them with the header Content-Type: text/plain.
2 files to download
| File | Size | What it is |
|---|---|---|
| sample-access.log | 340 KB | 2,000 lines in the nginx/Apache combined log format; IPs from the documentation ranges (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24) lines: 2000; status counts: 200: 1527, 302: 94, 304: 74, 404: 213, 500: 92 |
| sample-app.log | 42 KB | 600 application log lines with timestamps, levels (INFO, DEBUG, WARNING, ERROR) and worker ids lines: 600; level counts: DEBUG: 147, ERROR: 36, INFO: 358, WARNING: 59 |
MIME type: text/plain. Total 382 KB.
Good for testing
- Log parsers, grok patterns and regex practice
- Loading logs into a SIEM or log tool
- Counting status codes and errors
Check a file
awk '{print $9}' sample-access.log | sort | uniq -cCompare the SHA-256 checksum to make sure the download is complete and unchanged (sha256sum file on Linux, shasum -a 256 file on macOS, certutil -hashfile file SHA256 on Windows):
| File | SHA-256 |
|---|---|
| sample-access.log | 1e51d43291d8feb2330324d663f2ef8d1e71575ef0230a31479e60bda915c9a8 |
| sample-app.log | 1f7f1fb1224fab849826576896226263d0cebddae62e0a5ff2d45c9492b58290 |