Images · JPG
A 100 MB JPG file, on demand.
A 104,857,600-byte JPEG — 100 MiB exactly — aimed at the hard per-file limits of Git hosting and CDN plans.
104,857,600 bytes · built in your browser, nothing uploaded
Where a 100 MB JPG comes up
- Testing what happens when a large image is committed to a repository.
- Checking upload limits on sites behind Cloudflare's Free or Pro plans.
- Setting a Google Form upload question to its 100 MB option and testing the boundary.
Limits it lands on
- GitHub blocks files larger than 100 MiB; this file sits exactly at that line, the classic edge case for push hooks.
- Cloudflare's Free and Pro plans cap request bodies at 100 MB, so the upload (decimal 100 MB is smaller than 100 MiB) is refused.
- Google Forms offers 100 MB as a per-file maximum for upload questions.
What is inside the file
About 1,600 comment segments, each up to 65,533 bytes, precede the image data.
Building it takes a few hundred milliseconds; the file is assembled in memory and handed to the browser as a download.
Questions
Why does Cloudflare reject a "100 MB" file?
Cloudflare's limit is 100 MB in decimal terms. 104,857,600 bytes is larger than 100,000,000.
Should large images go in Git?
Use Git LFS or object storage; files this size make clones slow even when they are accepted.
Noticed an issue with this test file? Report an issue →