A 10 KB PNG test file

About this file

A 10 KB test file in PNG 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 PNG at roughly 2 bytes per pixel, this size works out to around 5,120 pixels — about 83 × 62 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

PNG is lossless and carries an alpha channel. Every file starts with the fixed 8-byte signature 89 50 4E 47 0D 0A 1A 0A, followed by IHDR / IDAT / IEND chunks. The key question for upload validation is whether your code identifies the file by those leading bytes rather than by its extension.

• Whether the alpha channel survives resize and conversion — converting to JPEG destroys it
• Whether image libraries such as GD, ImageMagick, or sharp hit their memory ceiling — PNG memory use scales with decoded pixel count, not file size
• Whether metadata such as tEXt chunks is stripped — PNG has no EXIF, but text chunks can retain information