1 KB LOG sample file
A LOG file of exactly 1,024 bytes. It is a valid Log file file, generated for this site and checked with an independent parser.
Download
- Type
- text/plain
- SHA-256
ae2dada1d3ff2898d14ddcc32e662b79d45a3538d551f8b85e1c4628c058988f- Direct URL
https://sampletestfiles.com/downloads/log/sample-log-1kb.log
What is in this file
6 web-server access log lines in Combined Log Format with increasing timestamps. One final request line carries a lengthened query string so the file reaches the exact size.
| Lines | 7 |
|---|---|
| Format | Combined Log Format (Apache and nginx access logs) |
| IP addresses | Documentation ranges from RFC 5737 |
| Encoding | UTF-8 (ASCII characters only) |
| Line endings | LF |
How the file begins
The opening lines of sample-log-1kb.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 file contents.
Where 1 KB matters
The smallest practical test file: 1,024 bytes, small enough to travel in a single network packet. These are the default limits a file of this size is useful for testing:
| System | Limit | Note |
|---|---|---|
| Ethernet | 1,500 bytes (typical MTU) | A 1 KB payload fits in one packet with its headers. |
| Browser cookies | 4,096 bytes per cookie | 1 KB is well inside the limit; the 5 KB sample is over it. |
Use this file for
- Smoke tests in CI that must run in milliseconds
- Testing log parsers and grok patterns
- Checking dashboards and alert rules
Testing notes for LOG
- Request paths and user agents come from clients and may contain quotes or escape sequences; a pattern that assumes clean input will misparse real traffic.
- Timestamps carry a zone offset. Parsers that drop it shift every event.
Technical details
| File name | sample-log-1kb.log |
|---|---|
| Format | LOG (Log file) |
| Extension | .log |
| MIME type | text/plain |
| Size | 1,024 bytes (1 KB) |
| Kind | Text |
| SHA-256 | ae2dada1d3ff2898d14ddcc32e662b79d45a3538d551f8b85e1c4628c058988f |
| 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-log-1kb.log 'https://sampletestfiles.com/downloads/log/sample-log-1kb.log'
sha256sum sample-log-1kb.log # Linux
shasum -a 256 sample-log-1kb.log # macOSOn Windows, run Get-FileHash sample-log-1kb.log -Algorithm SHA256 in PowerShell. A matching value proves that the download is complete and unaltered.
Related files
Questions about this file
- Is this file exactly 1 KB?
- Yes. It is 1,024 bytes, which is 1 KB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
- What is inside the 1 KB LOG file?
- 6 web-server access log lines in Combined Log Format with increasing timestamps. One final request line carries a lengthened query string so the file reaches the exact size.
- Are the IP addresses real?
- No. They come from the address ranges that RFC 5737 reserves for documentation, so they belong to no one.