10 MB BIN sample file
A BIN file of exactly 10,485,760 bytes. It is a valid Binary test file file, generated for this site and checked with an independent parser.
Download
sample-bin-10mb.bin
10 MB10,485,760 bytes
Download 10 MB BINDirect download. No sign-up and no waiting.
- Type
- application/octet-stream
- SHA-256
17a8377a8b86a416ce30457cc9a08624d194cfcef9d1cf185a15d5c2838b5897- Direct URL
https://sampletestfiles.com/downloads/bin/sample-bin-10mb.bin
What is in this file
10,485,760 pseudo-random bytes from a seeded generator, so every build of the file is identical and compression cannot shrink it.
| Content | Pseudo-random bytes |
|---|---|
| Compressible | No |
| Structure | None |
First bytes of the file
The first 64 bytes of sample-bin-10mb.bin as a hex dump: offset, bytes, then the same bytes as text.
00000000 69 d7 01 57 38 17 40 db 61 5f 0e 4f 75 40 49 5e |i..W8.@.a_.Ou@I^|
00000010 d3 fc 95 3b 45 b8 87 18 49 96 a6 71 a8 43 c8 18 |...;E...I..q.C..|
00000020 89 f8 7e 39 ec 9a 9e ce 34 2f 69 b7 da d9 eb d3 |..~9....4/i.....|
00000030 94 f6 9c 62 d6 00 0a 85 47 be 21 64 11 e9 87 5c |...b....G.!d...\|Preview
BIN files cannot be shown in a browser. Download the file and open it with curl, wget and browser download managers.
Where 10 MB matters
A 10,485,760-byte file: over the default limits of PHP, API Gateway and Spring Boot requests. These are the default limits a file of this size is useful for testing:
| System | Limit | Note |
|---|---|---|
| Amazon API Gateway | 10 MB payload | A 10 MB file in a multipart or base64 body is over the limit. |
| Spring Boot multipart | 10 MB per request by default (max-request-size) | Exceeded once form overhead is added. |
| PHP | 8 MB POST body by default (post_max_size) | Rejected before the script runs. |
| Amazon S3 multipart upload | 5 MiB minimum part size | This file splits into exactly two minimum-sized parts. |
| Email attachments | Commonly 20 to 25 MB per message | 10 MB fits, at about 13.3 MB once encoded. |
Use this file for
- Exercising chunked and resumable uploads
- Testing size limits precisely
- Checking resumable and chunked uploads
Testing notes for BIN
- Because application/octet-stream says nothing about content, strict upload filters reject these files. That is itself a useful test.
- A file of zeros, as produced by many quick commands, compresses to almost nothing, which makes transfers look far faster than they are.
Technical details
| File name | sample-bin-10mb.bin |
|---|---|
| Format | BIN (Binary test file) |
| Extension | .bin |
| MIME type | application/octet-stream |
| Size | 10,485,760 bytes (10 MB) |
| Kind | Binary |
| SHA-256 | 17a8377a8b86a416ce30457cc9a08624d194cfcef9d1cf185a15d5c2838b5897 |
| Created | 2026-10-10 |
| Validation | Exact size, signature bytes and structure checked when the file was generated |
| Preview | Not available for this format; details only |
| Source | Generated for this site; not copied from elsewhere |
| Licence | Free to use, modify and redistribute (terms) |
| Category | Testing |
Validated for expected format and integrity. As with any download, scan the file with your own security tools before opening it. How files are made and checked
Download from the command line and verify
Fetch the file with curl, then compare its checksum with the SHA-256 value above.
curl -o sample-bin-10mb.bin 'https://sampletestfiles.com/downloads/bin/sample-bin-10mb.bin'
sha256sum sample-bin-10mb.bin # Linux
shasum -a 256 sample-bin-10mb.bin # macOSOn Windows, run Get-FileHash sample-bin-10mb.bin -Algorithm SHA256 in PowerShell. A matching value proves that the download is complete and unaltered.
Related files
Questions about this file
- Is this file exactly 10 MB?
- Yes. It is 10,485,760 bytes, which is 10 MB in the binary units that operating systems and server limits use (1 KB = 1,024 bytes).
- What is inside the 10 MB BIN file?
- 10,485,760 pseudo-random bytes from a seeded generator, so every build of the file is identical and compression cannot shrink it.
- Why not use a file full of zeros?
- Zeros compress to nearly nothing, so any compression between server and client hides the true transfer size. Random bytes do not.