A 10 KB TXT test file

About this file

A 10 KB test file in TXT format, sized to exactly 10,240 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

10 KB sits below virtually every upload limit, which makes it the baseline "happy path" case. Confirm this file goes through first, then move up in size to probe where your limits actually bite.

It also fits inside the AWS Lambda asynchronous invocation payload cap (256 KB) and typical API JSON body limits. The size is convenient for CI fixtures and unit-test data you commit to a repository.

Getting a feel for this size

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

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