50 KB LOG sample
A LOG file of exactly 51,200 bytes. It is a valid Log file file, generated by this site. Compare its checksum and test it with the parser used by your application. Use it wherever you need a 50 KB sample, test or dummy LOG file.
Download
sample-log-50kb.log
50 KB51,200 bytes
Download 50 KB LOGCreated in your browser in a few seconds, then checked against the SHA-256 checksum. The file is not uploaded anywhere. No sign-up.
- Type
- text/plain
- SHA-256
7fd99f74d9dc7f25b83ef49f9fecc55b06893e9669b2d8079ccdd857b1d26a6e- Delivery
- Created in your browser from static generator assets (how it works).
What is in this file
293 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 | 294 |
|---|---|
| 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-50kb.log, exactly as they appear in the file.
00000000 31 39 38 2e 35 31 2e 31 30 30 2e 33 20 2d 20 2d |198.51.100.3 - -|
00000010 20 5b 30 31 2f 4a 61 6e 2f 32 30 32 36 3a 30 30 | [01/Jan/2026:00|
00000020 3a 30 30 3a 30 30 20 2b 30 30 30 30 5d 20 22 47 |:00:00 +0000] "G|
00000030 45 54 20 2f 61 73 73 65 74 73 2f 61 70 70 2e 6a |ET /assets/app.j|Preview
Shows the file contents.
Where 50 KB matters
A 51,200-byte file, half of the default body limit in several web frameworks. These are the default limits a file of this size is useful for testing:
| System | Limit | Note |
|---|---|---|
| Express body parsers | 100 KB by default | 50 KB is accepted; 500 KB is rejected with 413 unless the limit is raised. |
| Base64 encoding | Adds 33 percent | 50 KB becomes about 67 KB when embedded in JSON. |
Use this file for
- Checking thumbnail and icon handling
- Benchmarking ingestion pipelines
- Testing log parsers and grok patterns
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-50kb.log |
|---|---|
| Format | LOG (Log file) |
| Extension | .log |
| MIME type | text/plain |
| Size | 51,200 bytes (50 KB) |
| Kind | Text |
| SHA-256 | 7fd99f74d9dc7f25b83ef49f9fecc55b06893e9669b2d8079ccdd857b1d26a6e |
| Created | 2026-10-23 |
| Validation | See the listed size and SHA-256. Small downloads are checked in the browser; verify streamed downloads manually. A hash match does not prove parser compatibility. |
| Preview | Available on this page |
| Source | Generated in your browser by this site's generator; not copied from elsewhere |
| Licence | Free to use, modify and redistribute (terms) |
| Category | Testing |
Check the stated structure and checksum against your application requirements. As with any download, scan the file with your own security tools before opening it. How files are made and checked
Verify your copy
This file is created in your browser, so it has no direct URL for curl or wget. The generator is designed to produce reproducible bytes. After saving, compare the checksum with the SHA-256 value above.
sha256sum sample-log-50kb.log # Linux
shasum -a 256 sample-log-50kb.log # macOSOn Windows, run Get-FileHash sample-log-50kb.log -Algorithm SHA256 in PowerShell. For scripts and pipelines, save the file once and keep your own copy.
Related files
Questions about this file
- Is this file exactly 50 KB?
- Yes. It is 51,200 bytes, which is 50 KB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
- What is inside the 50 KB LOG file?
- 293 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.