A 10 MB WEBP test file

About this file

A 10 MB test file in WEBP format, sized to exactly 10,485,760 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 MB is one of the most common "round number" caps chosen for forms and CMS uploads. It is exactly 10,485,760 bytes (10 × 1024 × 1024), which also lets you detect whether an implementation computes MB with 1000 or with 1024.

An implementation using 1000 rejects anything past 10,000,000 bytes, so this file fails there. One using 1024 accepts it as exactly at the limit. To pin down the boundary precisely, combine it with the threshold set (9.9 MB / 10.0 MB / 10.1 MB).

Getting a feel for this size

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

Estimating a photographic WEBP at roughly 0.15 bytes per pixel, this size works out to around 69,905,067 pixels — about 9,654 × 7,241 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