A 100 MB WEBP test file

About this file

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

Estimating a photographic WEBP at roughly 0.15 bytes per pixel, this size works out to around 699,050,667 pixels — about 30,530 × 22,898 px at a 4:3 aspect ratio. Compression varies enormously with image content, so treat this purely as an order-of-magnitude figure.

What to check for this format

WebP uses a RIFF container: the file starts with RIFF and has WEBP at byte 9. It supports lossy, lossless, alpha, and animation — but detecting it from the extension or only the first four bytes risks confusing it with other RIFF-based formats.

• Whether your server-side image library actually supports WebP — older GD or ImageMagick builds may not
• Whether it is served as image/webp — a wrong Content-Type makes browsers download instead of render it
• Whether the JPEG / PNG fallback in your <picture> element works for unsupported clients