File Corruption Simulator

Random byte edits for resilience tests

The tool copies one file into browser memory and applies max(1, floor((size-protected)*percentage/100)) edit attempts. Each attempt selects an offset after the protected prefix and XORs its byte with a random value from 1 to 255. The input limit is 64 MiB.

Checkable example

For a 1,000-byte file, a 64-byte protected prefix and 10%, the count is floor((1000-64)*10/100)=93. The first 64 bytes remain unchanged. Positions are sampled with replacement: repeated edits can affect the same byte and can even restore it, so 93 attempts do not guarantee 93 distinct changes.

Output and limits

The generated download has the same byte length and a name beginning with corrupted- followed by the input filename. It uses the browser-reported MIME type, or application/octet-stream when that type is empty. The original disk file is not overwritten.

Generation prepares the download; it does not start an automatic transfer. The copy button copies the status report. Each run begins from the selected original, so changes do not accumulate between runs. The tool does not target particular records or regions beyond protecting the initial prefix.

All processing stays in the browser. A modified file may still open successfully; the tool does not diagnose corruption, repair data, verify backups or guarantee unreadability. Use disposable copies and validate the result with the software you are testing. Fractional percentages are supported; 0 and values above 100 are rejected.