Corrupt an EXE File Online
Corrupt a Windows .exe file online for free. Destroys the MZ stub and PE header so Windows refuses to load the executable.
- No upload
- No size limit
- No sign-up
Corrupt your EXE file
Tuned for .exe, .msi, .scr, and works with every other format too.
Why EXE files are hard to corrupt properly
A Windows executable is validated by the loader before a single instruction runs. The DOS MZ stub points to a PE header, which describes every section, import and entry point. Damage that chain and the program never starts, no crash, no partial execution, just a refusal.
What this tool destroys
- The MZ / DOS stub. The
MZsignature and the offset it carries to the PE header are destroyed. - The PE header. The
PE\0\0signature, COFF header and optional header describing the entry point are overwritten. - The section table. The records mapping
.text,.dataand.rsrcinto memory lose their structure. - Code and resources. Entropy is scattered through the sections, so even a manually rebuilt header points at unusable code.
What you will see afterwards
| Application | Behaviour |
|---|---|
| Windows | "This app can't run on your PC" or "%1 is not a valid Win32 application." |
| Windows Defender | Flags the file as malformed rather than executing it. |
| Dependency Walker / PE tools | Report an invalid PE image. |
| Wine on Linux/macOS | Refuses to load the binary. |
Common reasons people do this
- Testing that an installer verifies its payload before running it.
- Verifying a software updater detects a corrupt download and retries.
- Checking that code-signing validation actually fires on a damaged binary.
- Producing malformed PE files for a static analysis test suite.
How to corrupt a EXE file
- Drop your .exe file onto the box above, or click to browse.
- Leave the level on Standard unless you want partial damage (Light) or need to defeat recovery software (Heavy).
- Press Corrupt file. Processing happens on your device, so it finishes almost immediately.
- Download the result. It keeps the original filename and byte length by default.
EXE FAQ
Is a corrupted EXE dangerous to run?
It cannot run at all: Windows rejects it at load time, before any code executes. That said, only corrupt executables you own or are authorised to test.
Will antivirus flag the result?
Some engines flag malformed PE files as suspicious purely because the structure is invalid. That is expected behaviour, not a detection of anything harmful.
Does it work on MSI installers?
MSI is an OLE compound document rather than a PE binary, and is handled through that profile. It breaks just as reliably.
Can the executable be repaired?
No. The header chain and section table are destroyed, and the code itself is scattered.