Sample Log files
Free Log test files from 5 KB to 1 GB. Pick a size and download, or type any size you need.
5 KB Log
60 lines
10 KB Log
122 lines
100 KB Log
1,225 lines
500 KB Log
6,127 lines
1 MB Log
12,256 lines
5 MB Log
Made on your device
10 MB Log
Made on your device
25 MB Log
Made on your device
50 MB Log
Made on your device · saved in pieces
100 MB Log
Made on your device · saved in pieces
500 MB Log
Made on your device · saved in pieces
1 GB Log
Made on your device · saved in pieces
Free for any use, including commercial. Made by this site, with no third-party content and no signup.
What is inside
- One line per request: timestamp, level, server name, trace ID, method, path, status and time taken
- 122 lines in the 10 KB file, 12,256 in the 1 MB file, 306,658 in the 25 MB file
- ISO 8601 UTC timestamps, starting at 2026-01-01T00:00:01.370Z and 1.37 seconds apart
- Mostly INFO, with DEBUG, WARN and ERROR mixed in
- ERROR lines carry status 500 and WARN lines carry 429, so you can filter on either
- Each file ends on its last whole line, so it is a few bytes under the target size
Try it with these tools
They run in your browser. The file you downloaded stays on your device.
- Log File Viewer Open and read a log file in your browser, with errors and warnings easy to spot.
- Compare Log Files Find what differs between two log files.
- Regex Tester Test a pattern live, with matches highlighted.
- Unix Timestamp Converter Convert between timestamps and readable dates.
- GZIP Compressor Compress a single file with gzip.
- Compress Text File Compress a .txt, .log, .csv or .json to GZIP, ZIP or raw deflate.
- File Hash Generator Work out the MD5, SHA-1 and SHA-256 of a file without uploading it.
About Log files
A .log file is plain text that a program appends to as it runs. There is no single standard layout, but most lines carry the same few parts: a timestamp, a level such as INFO or ERROR, where the line came from, and a message.
Developers, support staff and ops teams read logs to find out what happened and when. Logs grow quickly, so real ones are often tens or hundreds of megabytes, and a tool that is fine with a short log can freeze on a long one.
The thing that most often goes wrong is time. A log written in local time without an offset can be hours out when read in another country. These files use UTC with a Z on the end, so the time means the same thing everywhere.
Sources: RFC 3339, date and time on the internet (IETF)
Questions
Why is the 10 KB log 9,984 bytes?
Each file stops at the last full line that fits under the size. Cutting a line in half, or adding filler, would make the file look like a broken log, and that is not what you want to test.
Are these real server logs?
No. A seeded script writes them, so the trace IDs, paths and timings are made up and there are no IP addresses or user details in them. The same script always writes the same lines.
How do I find only the errors?
Search for the word ERROR, or for a status of 500. Every ERROR line has status 500, so both searches return the same lines, which is a handy check that a filter is working.
Also searched as: sample log file download, dummy log file, test log file, example log file, 1 MB log file, 10 MB log file, 100 MB log file, 1 GB log file, free log for testing.
For developers: exact bytes and SHA-256
Sizes are decimal (1 MB = 1,000,000 bytes). The hosted files never change between builds, so these checksums stay valid.
| File | Bytes | SHA-256 |
|---|---|---|
| sample-5kb.log | 4,922 bytes | 7b5d3e85cac346c5298f7a82ea11cb1dd90785c5c54a00817d06151356b7ba42 |
| sample-10kb.log | 9,984 bytes | 6f70aad8adb47b8406c9b00c76afaf9520cc684a051ce5b40215fe8fe7ae9528 |
| sample-100kb.log | 99,964 bytes | 8d3161ea8ab5159b867188ee1ae82ec25b92774041d91c16865c840ed852e76d |
| sample-500kb.log | 499,977 bytes | 098e7473de27e1b274694e9572b3d04bde87af87272e6365ac5f713a650668ad |
| sample-1mb.log | 999,912 bytes | a4492134cfab61aba9a35c916bc1e3b650008bf8ffaedaec83da51b34c70f181 |