Skip to main content

Corrupt a File

Deliberately corrupt one or more files by flipping random bytes — for testing how software handles broken input. Runs entirely in your browser; files are never uploaded.

Input

Drop files or browse
Up to 10 files · 100MB each

Corrupting a file changes random bytes, making it unreadable. Higher percentages cause more damage.

Preserves the first and last 1% of each file, corrupting only the middle — often enough to keep a file partially readable while still damaging it.

Corrupted Files

Upload one or more files, set the corruption amount, and press Corrupt Files. Corrupted files are generated entirely in your browser and never uploaded.

Was this helpful?

Guides

Deliberately damage a file by flipping random bytes — useful for testing how software handles corrupted input, building a "broken file" test fixture, generating a prank file, or seeing whether a backup/restore pipeline actually notices bit rot.

How to use it

  1. Drag and drop up to 10 files (100MB each) into the upload area, or click to browse.
  2. Set Corruption Amount (%) — what fraction of the file's bytes get randomly changed.
  3. Toggle Maintain safe zones if you'd like the file to stay partially readable.
  4. Press Corrupt Files.
  5. Download each corrupted file individually, or all of them at once as a .zip.

Settings

  • Corruption Amount (%) — the percentage of the file's total bytes that get replaced with random values. Low percentages (1–5%) often still leave a file partially usable; high percentages make it unrecognizable to whatever normally opens it.
  • Maintain safe zones — when on, the first and last 1% of the file are left untouched and only the middle is corrupted. Many file formats keep header/footer metadata at the start or end, so this setting is more likely to leave a file partially readable (or at least still recognized by its type) while still meaningfully damaging its contents.

How it works

For each file, the tool picks random byte positions and replaces each one with a random value — entirely in memory, in your browser. Nothing is uploaded to a server at any point; the corrupted file is generated locally and offered straight back to you as a download.

Is this reversible?

No — corruption is one-way. The random bytes that get overwritten are gone; there's no way to recover the original content from the corrupted file. Keep a copy of the original if you want it back.

Privacy

Everything runs entirely in your browser. Your files are never uploaded to a server.

corrupt filedamage filetest filebroken filebyte flip

Love the tools? Lose the ads.

One payment clears every ad from your account, for good. No subscription, no tracking.