💔 Broken files
Intentionally corrupted files for error-handling verification. Use them to test validation and error-handling logic.
A PNG file with a corrupted header
A PNG file with a corrupted header
PNG / 10 KB
A PNG file truncated part-way through
A PNG file truncated part-way through
PNG / 30 B
A PDF file with a corrupted header
A PDF file with a corrupted header
PDF / 10 KB
A PDF file truncated part-way through
A PDF file truncated part-way through
PDF / 40 B
A corrupted ZIP file
A corrupted ZIP file
ZIP / 10 KB
A JSON file containing a syntax error
A JSON file containing a syntax error
JSON / 36 B
A CSV file whose rows have inconsistent column counts
A CSV file whose rows have inconsistent column counts
CSV / 231 B
Why testing with broken files matters
In production, files can arrive corrupted from network failures or transfer errors. Malicious users may also upload files with spoofed extensions.
Use these broken files to test that your application detects and handles errors properly — never crashing, and always returning a clear error message.