Corrupt an SQL File Online
Corrupt a .sql dump online for free. Breaks statement structure and encoding so imports fail instead of loading partial data.
- No upload
- No size limit
- No sign-up
Corrupt your SQL file
Tuned for .sql, .dump, and works with every other format too.
Why SQL files are hard to corrupt properly
An SQL dump is a text file of statements executed in order. That makes partial corruption genuinely dangerous in the real world, an import can succeed for thousands of rows and then fail halfway, leaving a database in an inconsistent state. Reproducing that on demand is exactly what this is for.
What this tool destroys
- Statement terminators. Semicolons and line breaks are overwritten, so statements run together into unparseable input.
- String literal quoting. Quotes are broken up, leaving literals unterminated and swallowing subsequent statements.
- The dump header. The opening bytes containing the client and server version comments are destroyed.
- Encoding validity. Invalid UTF-8 sequences make the file fail on import before any statement executes.
What you will see afterwards
| Application | Behaviour |
|---|---|
mysql < dump.sql | "ERROR 1064 (42000): You have an error in your SQL syntax" and the import aborts. |
psql -f | Reports invalid byte sequence for the encoding and stops. |
| phpMyAdmin / Adminer | Import fails with a syntax error and a line number. |
| Light level | Import may run partway before failing, the realistic partial-restore scenario. |
Common reasons people do this
- Rehearsing a restore from a damaged backup before it happens for real.
- Verifying an import runs inside a transaction and rolls back cleanly on failure.
- Testing that a migration tool reports the failing statement rather than continuing.
- Demonstrating why backups must be verified, not just taken.
How to corrupt a SQL file
- Drop your .sql file onto the box above, or click to browse.
- Leave the level on Standard unless you want partial damage (Light) or need to defeat recovery software (Heavy).
- Press Corrupt file. Processing happens on your device, so it finishes almost immediately.
- Download the result. It keeps the original filename and byte length by default.
SQL FAQ
Can I simulate a partial restore?
Yes, and this is the most useful case. Light level leaves most statements intact, so an import typically runs for a while before failing, which is precisely the scenario that catches missing transaction handling.
Does it work on compressed dumps?
A .sql.gz file is handled as a gzip archive instead, which breaks the whole thing at once. Decompress first if you want statement-level damage.
Will it break a specific table?
Not deterministically, damage is scattered, not targeted at named objects.
Is the original dump modified?
No. The corruption is applied to a copy in memory and downloaded separately.