A 100 MB TXT test file

About this file

A 100 MB test file in TXT format, sized to exactly 104,857,600 bytes. Free to download with no signup, for verifying upload limits and file-handling behaviour.

The MD5, SHA-1 and SHA-256 values listed above are the real digests of this file. Recomputing them after download confirms the transfer was not corrupted, and they double as known-good expected values when testing a hashing library.

What this size means in practice

100 MB is GitHub's hard per-file push limit and also the upload cap through Cloudflare's free plan. It is likewise the point where AWS S3 recommends multipart upload instead of a single PUT.

It also exercises your timeout configuration. On a 10 Mbps link the transfer alone takes about 80 seconds, so leaving PHP's max_execution_time (default 30s) or nginx's fastcgi_read_timeout (default 60s) untouched makes the upload fail on a timeout rather than on a size check.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 83.9 seconds, and about 8.4 seconds at 100 Mbps. Base64-encoded it grows to roughly 136,533 KB.

At roughly 120 bytes per log line, this size holds about 873,813 lines — a reasonable basis for estimating how long log aggregation or a full-text scan will take. Line length varies, so treat it as an approximation.

What to check for this format

Plain text is the simplest format, yet two variables alone — character encoding and newline convention — account for a large share of real defects. It carries no signature, so its format cannot be confirmed from the bytes.

• Whether you read line by line — slurping a log-sized text file whole puts heavy pressure on memory
• Whether the presence or absence of a BOM changes your processing
• Whether the final line is still captured when the file does not end with a newline