Intentionally damage a PDF file for testing. Corrupt header, xref, pages, streams. For developers & QA.
Select a healthy PDF to intentionally damage
3 steps to create a damaged PDF
Select a healthy, working PDF file.
Choose corruption types and intensity level.
Download the intentionally corrupted PDF.
Developers and QA teams need corrupted test files to test error handling in their PDF viewers, parsers, repair tools, and upload validators. This creates realistic corruption scenarios.
8 types: Header destruction, xref table corruption, trailer removal, EOF removal, stream corruption, file truncation, random byte injection, and page tree damage. Each can be combined.
Intensity (1-10) controls how severe each corruption is. Low = minor damage (some readers may still open). High = severe damage (most readers will reject the file).
Yes! Use our Repair PDF tool to test if it can recover the damaged file. That's the whole point of this tool — creating test cases for repair tools.