System · EXE
A 2 GB EXE file, on demand.
Exactly 2,147,483,648 bytes of a genuine MS-DOS + PE header — the same bytes file-type scanners and antivirus engines check to identify a Windows executable, built on your machine the moment you press the button.
2,147,483,648 bytes, exactly.
Every byte above the 512 bytes structural minimum goes into trailing bytes after a header that declares zero sections, so a real Windows loader refuses to run it, which is why this file still behaves like one a real user would send.
Unit convention
2 GB on this page means exactly 2,147,483,648 bytes, using the binary (MiB) convention some systems label "MB" for short. 1 MB in the strict decimal sense is 1,000,000 bytes; 1 MiB is 1,048,576 bytes — the readout above always shows the exact count either way.
Approximate size equivalents
Roughly 1,193,046 pages of typed text, 2237 minutes of 128 kbps audio, 203 minutes of CD-quality audio, 859 photos from a 12 MP camera. These figures compare file size only — the generated file does not contain this text, audio or image content.
Rejected by
Slack free workspace file, Cloudflare Free proxy body, GitHub repository file — this exceeds their commonly cited limit, which makes it a useful negative test. Published limits can vary by plan and change over time.
Other EXE sizes
At this scale you are testing infrastructure rather than validation: timeouts, proxy buffers, disk headroom and progress reporting.
2 GB in other system formats
Questions.
Is this 2 GB EXE file valid?
Yes. It is a genuine MS-DOS + PE header — the same bytes file-type scanners and antivirus engines check to identify a Windows executable. The extra bytes sit in trailing bytes after a header that declares zero sections, so a real Windows loader refuses to run it, so it opens in file managers and antivirus scanners — deliberately never executes.
Does 2 GB mean 2,147,483,648 bytes?
On this page, yes — 2 GB uses the binary (MiB) convention, so the file is exactly 2,147,483,648 bytes. 1 MB in the strict decimal sense would be a different, smaller byte count. Upload validators may use either convention, so the exact byte count is always shown to remove any ambiguity.
What is a 2 GB file used for?
At this scale you are testing infrastructure rather than validation: timeouts, proxy buffers, disk headroom and progress reporting. For EXE specifically, the usual job is testing upload size limits, download managers and file-type filters without ever shipping runnable code.
Where is the file downloaded from?
Nowhere. It is assembled in a Web Worker on your own device and handed to the browser as a Blob, so nothing is uploaded, fetched or stored.