# Sample log files for testing parsers and shippers, free and CC0 2 log test files from 110.1 KB to 167.7 KB. Direct URLs, a SHA-256 for each and CC0, so curl and CI can fetch them with no signup and no keys. The page: . Log files are text, but tooling meets them in two distinct shapes, and both are here. `log/nginx-access-1000-lines.log` is 1,000 lines in the nginx combined access-log format: client address, timestamp, request line, status, bytes, referrer and user agent. The timestamps are fixed and every client address is an RFC 5737 documentation address, so the file contains no real IP addresses and parses the same way every time. `log/json-lines-app-1000.log` is 1,000 application log records with one JSON object per line, the structured shape that log shippers and observability pipelines prefer. Use them to test log parsers and shippers, dashboards that must handle both shapes, grok and regex patterns, and upload forms for diagnostic files. Both are UTF-8 with LF line endings. Related formats: [NDJSON](https://loremfile.dev/ndjson), which has the same one-object-per-line structure, and [text files](https://loremfile.dev/txt). ## Files | Path | Size | MIME | Properties | |---|---|---|---| | [`log/json-lines-app-1000.log`](https://loremfile.dev/log/json-lines-app-1000.log) | 167.7 KB (167,666 bytes) | `text/plain; charset=utf-8` | utf-8, LF, 1,000 lines | | [`log/nginx-access-1000-lines.log`](https://loremfile.dev/log/nginx-access-1000-lines.log) | 110.1 KB (110,093 bytes) | `text/plain; charset=utf-8` | utf-8, LF, 1,000 lines | The same list as JSON: .