10 tools · Free · On-device

Document File Corrupter Tools

Office documents and PDFs are the formats people most often need broken, and the hardest to break convincingly. Word, Excel and PowerPoint files are ZIP packages with built-in recovery; PDFs rebuild their own cross-reference tables. These tools destroy the container and index structures those recovery paths depend on.

Each tool at a glance

  • PDF Corrupter .pdf
    The %PDF- header. The first bytes declare the format and version. Overwriting them means the file is no longer recognised as a PDF at all.
  • Word Corrupter .docx, .doc, .docm
    Local file headers. Every PK\x03\x04 record that marks the start of an entry inside the package is destroyed.
  • Excel Corrupter .xlsx, .xls, .xlsm
    ZIP entry headers. Every local file header inside the package is destroyed, including xl/workbook.xml and each worksheet part.
  • PowerPoint Corrupter .pptx, .ppt, .pptm
    Package structure. Local file headers, the central directory and the EOCD record of the presentation package are all destroyed.
  • Text File Corrupter .txt, .log, .ini, .conf
    Invalid UTF-8 sequences. Bytes in the 0x80–0xFF range are injected without valid lead bytes, which is a decoding error rather than a strange character.
  • RTF Corrupter .rtf
    The \rtf1 header. The opening {\rtf1 declaration is destroyed, so the file is no longer identified as RTF.
  • ODT Corrupter .odt, .fodt
    The mimetype entry. ODF requires an uncompressed mimetype entry as the first item in the archive. Destroying it breaks format detection immediately.
  • ODS Corrupter .ods, .fods
    The package index. Local file headers, the central directory and the EOCD record are destroyed, so the archive cannot be enumerated.
  • ODP Corrupter .odp, .fodp
    The archive index. Local file headers, the central directory and the EOCD record are all destroyed.
  • eBook Corrupter .epub, .mobi, .azw3, .azw
    EPUB container. The mimetype entry, META-INF/container.xml, the central directory and the EOCD record are all destroyed.

About these documents tools

Every tool listed here runs the same engine. The dedicated pages exist because each format fails differently and it is worth knowing what to expect, which application shows which error, whether a repair feature will rescue the file, and what survives at each damage level.

What they have in common

  • Nothing is uploaded. Every byte is processed in your browser.
  • No size limit. Files are handled in 8 MB slices.
  • The output looks normal. Same filename, byte length and MIME type.
  • Four damage levels. From partial damage to cryptographic noise.