A 500 KB WEBP test file

About this file

A 500 KB test file in WEBP format, sized to exactly 512,000 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

500 KB is a realistic size for a single high-resolution photo. It puts a load close to real-world data on front-end image optimisation and preview-generation paths.

Base64-encoded it grows to roughly 667 KB, because Base64 inflates data by about 33%. If you embed files in data URIs, email attachments, or JSON payloads, your limits must account for that expansion.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 410 ms, and about 41 ms at 100 Mbps. Base64-encoded it grows to roughly 667 KB.

Estimating a photographic WEBP at roughly 0.15 bytes per pixel, this size works out to around 3,413,333 pixels — about 2,133 × 1,600 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