50 MB LOG sample

A LOG file of exactly 52,428,800 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 MB sample, test or dummy LOG file.

Download

sample-log-50mb.log

50 MB52,428,800 bytes

Download 50 MB LOG

Created in your browser and, in browsers that can stream to disk, sent straight to your downloads list; this can take a minute. No sign-up.

Type
text/plain
SHA-256
5a2237ca8678ded452779dcd926e26d7bfcc8ff0a0cb4661807f982c0d6a8b2d
Delivery
Created in your browser from static generator assets (how it works).

What is in this file

307,183 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.

Lines307,184
FormatCombined Log Format (Apache and nginx access logs)
IP addressesDocumentation ranges from RFC 5737
EncodingUTF-8 (ASCII characters only)

How the file begins

The opening lines of sample-log-50mb.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

Creates the file in your browser and shows its first 64 KB.

Where 50 MB matters

A 52,428,800-byte file: exactly the size at which Git hosting on GitHub starts warning about large files, and about the limit for a zipped AWS Lambda package uploaded directly.

All 50 MB sample files

Use this file for

  • Measuring download speed from your own server or CDN
  • Benchmarking ingestion pipelines
  • Testing log parsers and grok patterns

Testing notes for LOG

  • Timestamps carry a zone offset. Parsers that drop it shift every event.
  • 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.

LOG format reference

Technical details

File namesample-log-50mb.log
FormatLOG (Log file)
Extension.log
MIME typetext/plain
Size52,428,800 bytes (50 MB)
KindText
SHA-2565a2237ca8678ded452779dcd926e26d7bfcc8ff0a0cb4661807f982c0d6a8b2d
Created2026-10-23
ValidationSee 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.
PreviewAvailable on this page
SourceGenerated in your browser by this site's generator; not copied from elsewhere
LicenceFree to use, modify and redistribute (terms)
CategoryTesting

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-50mb.log     # Linux
shasum -a 256 sample-log-50mb.log # macOS

On Windows, run Get-FileHash sample-log-50mb.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 MB?
Yes. It is 52,428,800 bytes, which is 50 MB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
What is inside the 50 MB LOG file?
307,183 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.