A 5 MB JPG test file

About this file

A 5 MB test file in JPG format, sized to exactly 5,242,880 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

5 MB lands in a useful spot for probing PHP defaults. upload_max_filesize ships as 2M and post_max_size as 8M, so on an untouched PHP install this file is rejected by upload_max_filesize while still fitting inside the POST body cap.

Serverless platforms cut in even earlier: AWS Lambda caps synchronous invocation payloads at 6 MB and Vercel Serverless Functions cap request bodies at 4.5 MB. Use this file to verify what happens when the request dies before your handler ever runs.

Getting a feel for this size

On a 10 Mbps link the transfer takes roughly 4.2 seconds, and about 419 ms at 100 Mbps. Base64-encoded it grows to roughly 6,827 KB.

Estimating a photographic JPG at roughly 0.2 bytes per pixel, this size works out to around 26,214,400 pixels — about 5,912 × 4,434 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

JPEG is lossy and has no transparency. Its signature begins with FF D8 FF. The single most common defect in real implementations is ignoring the EXIF Orientation tag, which makes rotated photos appear sideways in the browser.

• Whether you read EXIF Orientation and auto-rotate, or deliberately strip it
• Whether privacy-sensitive data such as GPS coordinates remains — stripping is mandatory for user-submitted images
• Whether both progressive and baseline JPEG decode correctly — older decoders sometimes fail on progressive