A 5 MB PNG test file
File info
| File Format | PNG |
|---|---|
| File Size | 5 MB（5,242,880 bytes） |
| MIME Type | image/png |
| MD5 | 8cf0927fe2a935606e23dd7b431c5650 |
| SHA-1 | 01d4d083ce1a65f71c48572a9f8355dd52590e4d |
| SHA-256 | 8562ccb77f405df7a0b7c3b2fe1399eea291afcfe12a879ea59cad5d96740e47 |
Download via command line
curl -O https://devlab.itlibra.com/files/images/png/png-5mb.png
wget https://devlab.itlibra.com/files/images/png/png-5mb.png
Invoke-WebRequest -Uri "https://devlab.itlibra.com/files/images/png/png-5mb.png" -OutFile "png-5mb.png"
About this file
A 5 MB test file in PNG 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 PNG at roughly 2 bytes per pixel, this size works out to around 2,621,440 pixels — about 1,870 × 1,403 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
FAQ
- Is this file free to use?
- Yes — fully free and no signup required. Use it for any commercial or non-commercial test/verification purpose.
- What is inside the file?
- Dummy data generated for testing — sized to match the listed size exactly.
- What are the hash values for?
- Verify integrity after download or use them as test data for hashing libraries.