Images · JPG
A 5 MB JPG file, on demand.
A 5,242,880-byte JPEG that fits ordinary image limits but breaks base64-encoded serverless uploads.
5,242,880 bytes · built in your browser, nothing uploaded
Where a 5 MB JPG comes up
- Testing an image upload route built on API Gateway and Lambda.
- Checking bots that send photos through Telegram.
- Simulating a typical smartphone photo size for gallery and feed uploads.
Limits it lands on
- Telegram's Bot API accepts photos up to 10 MB with sendPhoto, so this one goes through.
- Base64-encoded for a Lambda proxy integration it becomes about 6.99 million bytes, over the 6 MB synchronous limit.
- It is also above Vercel's 4.5 MB serverless request body maximum.
What is inside the file
About 80 padding segments sit between the start-of-image marker and the encoded picture; the image data itself is unchanged.
The canvas is drawn with a gradient and texture blocks so the encoder produces a realistic, non-trivial JPEG.
Questions
Why use a 5 MB photo for serverless tests?
It is a normal phone-photo size, yet it is the point where encoding overhead pushes many serverless upload paths over their limit.
Does the image look different at each size?
No — the visible picture is the same 800 × 600 image; only the comment padding changes.
Noticed an issue with this test file? Report an issue →