A 100 KB TXT test file

About this file

A 100 KB test file in TXT format, sized to exactly 102,400 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 KB sits at the boundary between "trivially small" and "realistic payload". It is close to the total transfer weight of a single lean web page and is a common target size for performance-conscious images.

It clears the sub-1 MB caps many applications impose, but it is still small enough that a naive load-everything-into-memory implementation works fine — so it is not the right size for proving that streaming is necessary. Pair it with 10 MB or larger to see the difference.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 82 ms, and about 8 ms at 100 Mbps. Base64-encoded it grows to roughly 133 KB.

At roughly 120 bytes per log line, this size holds about 853 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