A 10 KB PDF test file

About this file

A 10 KB test file in PDF 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.

Assuming a text-oriented PDF with embedded fonts runs about 80 KB per page, this size is on the order of 0 pages. Image-heavy PDFs will hold far fewer pages at the same size.

What to check for this format

PDF starts with the %PDF- signature and keeps a cross-reference table (xref) at the end that points to every object. Because of that layout, losing the tail of the file makes the whole document unreadable — which makes PDF a good subject for truncation-detection tests.

• Whether page-count extraction and text extraction finish without timing out on large files
• The time and memory cost of thumbnail generation, i.e. rasterising the first page
• Because PDF can embed JavaScript and external references, whether your sanitisation path runs when accepting user uploads