Download a sample log file of any size
Get a plain-text application log with timestamps, levels and worker names, at the exact size you need.
1 MB = 1,000,000 B · 1 MiB = 1,048,576 B
Advanced: test an upload limit
Enter the byte limit above, then choose one byte below, the exact limit or one byte above. Each choice uses the same base: 10,485,760 B. Generate and download each file to test your endpoint.
How is the sample LOG file built?
Each line has an RFC 3339 timestamp in UTC, a level (INFO, DEBUG, WARN or ERROR), a worker name and a message such as an HTTP request, a cache hit or a 413 upload rejection. Timestamps advance one second per line from 1 January 2026. The final line is a run of # characters that sets the exact size.
The smallest valid LOG file is 2 bytes; any byte count from there up to 2 GiB can be selected. MIME type: text/plain.
Which LOG size do you need?
What is inside a 1 MiB LOG file?
The 1 MiB sample has 15,264 log lines covering a little over four hours, from 00:00:01 to 04:14:24 UTC, followed by a 45-byte filler line. One line in eight is an ERROR and one in eight a WARN, so a filter for errors returns a predictable count.
When is a sample LOG file useful?
- Testing log viewers, tail tools and search in support dashboards.
- Checking upload limits for diagnostic bundles that customers attach to tickets.
- Benchmarking log parsers and grep-style filters on a known line format.
Questions about LOG test files
Can a log parser read it?
Yes. The format is space-separated: timestamp, level, [worker-N], message. A regular expression or a grok pattern can parse each line.
How many ERROR lines are there?
One in every eight lines. In the 1 MiB sample that is about 1,900 lines.
Format reference and related tools
Format reference: RFC 3339 timestamps.
Other formats in this family (Data): CSV · JSON · XLSX · XML · SQL · ODS · YAML · TSV · JSONL.
Related: CSV to JSON · JSON to YAML · Bytes to MB converter
Noticed an issue with this test file? Report an issue →