A 50 MB PDF test file

About this file

A 50 MB test file in PDF format, sized to exactly 52,428,800 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

50 MB is the point where GitHub starts warning you on push (it hard-rejects above 100 MB). In practice it is the decision line for whether a binary belongs in Git directly or should move to Git LFS.

At this scale, an implementation that buffers the whole request in memory burns 50 MB or more per worker process — ten concurrent uploads means 500 MB. It is a good size for verifying that streaming or spill-to-temp-file actually works.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 41.9 seconds, and about 4.2 seconds at 100 Mbps. Base64-encoded it grows to roughly 68,267 KB.

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