Make a file of exactly the size you need to test upload limits, progress bars, quotas or transfer speeds. Pick zeros, incompressible random bytes or readable text, choose the extension and download it. Nothing is uploaded; the file is built in your browser.
Last updated:
Unit system
0%
File—
Exact size—
Also equals—
Generated in—
SHA-256—
Advertisement
Advertisement
How to use the Dummy File Generator
Enter the size or click a preset such as 10 MB or 1 GB.
Choose binary or decimal units to match the limit you are testing (most upload limits use binary megabytes).
Pick the content: zeros for a quick file, random bytes to defeat compression, or text for a readable file.
Set the extension and name, e.g. .pdf to test a PDF-only upload field.
Press Generate & Download. The exact byte count and SHA-256 appear below when it is done.
Common test file sizes in bytes
Size
Binary bytes (KiB/MiB/GiB)
Decimal bytes (KB/MB/GB)
Typical use
100 KB
102,400
100,000
Avatar and form attachment limits
1 MB
1,048,576
1,000,000
Default upload limits (e.g. nginx client_max_body_size is 1 MiB)
2 MB
2,097,152
2,000,000
PHP's default upload_max_filesize
10 MB
10,485,760
10,000,000
Document and image upload fields
25 MB
26,214,400
25,000,000
Common email attachment limit
100 MB
104,857,600
100,000,000
Video uploads, speed tests
1 GB
1,073,741,824
1,000,000,000
Large-file and resumable upload tests
What to test with a dummy file
Size limits on both sides. Try exactly the limit, one byte over and one byte under. Client-side checks, the web server, the proxy and the application often have different limits.
Error messages. Does a too-large file give a friendly message, or a blank page, a 413 Request Entity Too Large or a timeout?
Progress and resume. Use 100 MB or more of random data to watch progress bars, pause and resume, and chunked uploads.
Compression. A file of zeros may upload almost instantly through a compressing proxy, while random data shows the real throughput.
Integrity. Compare the SHA-256 after a round trip to catch truncated or corrupted transfers.
It depends on the convention. In binary units (used by Windows, PHP's upload_max_filesize and many servers) 10 MB is 10 × 1,048,576 = 10,485,760 bytes, properly called 10 MiB. In decimal units (used by macOS, disk makers and network speeds) 10 MB is 10,000,000 bytes. Choose the unit system that matches the limit you are testing.
Which content type should I choose?
Zeros are fastest and fine for testing size limits. Random bytes cannot be compressed, so use them when testing transfer speeds, CDN or proxy behaviour or anything that may gzip the upload. Text and numbered lines create readable files for log viewers, editors and line-count tests.
Is a dummy .pdf or .jpg file a real PDF or image?
No. Only the file name ends in .pdf or .jpg; the content is zeros, random bytes or text. Upload forms that only check the extension or MIME type will accept it, but anything that opens or validates the file will report it as damaged. To test a real file, use a genuine document of the right size.
How do I test a file that is just over an upload limit?
Use the bytes unit. For a 10 MiB limit, generate 10,485,760 bytes to test the exact limit and 10,485,761 bytes to test one byte over. The Exact size card confirms the byte count of the generated file.
Why use the SHA-256 checksum?
After uploading and downloading the file again, compute its SHA-256 (for example with sha256sum on Linux, shasum -a 256 on macOS or Get-FileHash in PowerShell) and compare it with the value shown here. If they match, the file arrived unchanged. With random content even a single flipped byte changes the hash.
What is the largest file I can create?
Up to 2 GB. The file is assembled in browser memory before it is saved, so very large files need free RAM; on phones and tablets keep it to a few hundred MB. On a desktop you can also use fsutil file createnew (Windows), mkfile (macOS) or truncate / dd (Linux) for larger files.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.