Download 100 MB binary file for testing
Test transfer, storage or upload-size limits with raw bytes. The preset is 100 MiB (104,857,600 bytes); choose MB for decimal megabytes.
1 MB = 1,000,000 B · 1 MiB = 1,048,576 B
Advanced: test an upload limit
Enter the byte limit above, then choose one byte below, the exact limit or one byte above. Each choice uses the same base: 104,857,600 B. Generate and download each file to test your endpoint.
Where a 100 MB BIN comes up
- Checking that a site behind Cloudflare returns 413 for an upload above the plan limit.
- Testing multipart uploads to S3 or compatible storage with a file at AWS's recommended multipart threshold.
- Measuring sustained throughput: about 8.4 seconds at 100 Mbit/s, under a second at 1 Gbit/s.
Limits it lands on
- Cloudflare Free and Pro plans refuse request bodies above 100 MB (decimal); this 100 MiB file is about 4.9% larger.
- GitHub blocks files larger than 100 MiB; this file is exactly at that threshold.
- AWS recommends multipart upload for objects over 100 MB, so this file is the usual point to switch from a single PUT.
What is inside the file
The 65,536-byte filler block repeats 1,600 times. Because the content is deterministic, any changed or missing byte changes the checksum.
SHA-256: 741452b8c6711d1533e3bb2dad099d0a02cdd90f3e0784b418f4574e40875f8e.
Questions
Why is the S3 multipart threshold relevant?
With multipart uploads, a failed part can be uploaded again without restarting the whole file. AWS recommends this method for objects larger than 100 MB.
Will Cloudflare compress it during download?
Cloudflare normally serves application/octet-stream without compression. If a proxy uses brotli, the file shrinks greatly and speed measurements become unrealistic.
Reference and checks
Noticed an issue with this test file? Report an issue →