A 10 KB JPG test file

About this file

A 10 KB test file in JPG format, sized to exactly 10,240 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 KB sits below virtually every upload limit, which makes it the baseline "happy path" case. Confirm this file goes through first, then move up in size to probe where your limits actually bite.

It also fits inside the AWS Lambda asynchronous invocation payload cap (256 KB) and typical API JSON body limits. The size is convenient for CI fixtures and unit-test data you commit to a repository.

Getting a feel for this size

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

Estimating a photographic JPG at roughly 0.2 bytes per pixel, this size works out to around 51,200 pixels — about 261 × 196 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