A 100 MB PDF test file

About this file

A 100 MB test file in PDF 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.

Assuming a text-oriented PDF with embedded fonts runs about 80 KB per page, this size is on the order of 1,280 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