Corrupt an SVG File Online
Corrupt an .svg file online for free. Breaks the XML structure and path data so browsers and editors refuse to render the vector graphic.
- No upload
- No size limit
- No sign-up
Corrupt your SVG file
Tuned for .svg, .svgz, and works with every other format too.
Why SVG files are hard to corrupt properly
SVG is XML, not a binary image format, which changes everything about how it breaks. Browsers parse SVG strictly (unlike HTML) so a document that is not well-formed is rejected outright rather than partially rendered.
What this tool destroys
- The XML declaration. The opening declaration and
<svg>root element are destroyed, so the document has no valid root. - Path data. The
dattribute strings that define every shape are overwritten, leaving unparseable coordinates. - viewBox and dimensions. The attributes that establish the coordinate system are damaged, so nothing has a place to render.
- Encoding validity. Invalid UTF-8 sequences cause the strict XML parse to fail before rendering begins.
What you will see afterwards
| Application | Behaviour |
|---|---|
| Browsers | "XML Parsing Error: not well-formed", nothing renders at all. |
| Figma / Illustrator | Import fails with an invalid-SVG message. |
| Inkscape | Refuses to open the document or reports a parse error. |
<img src="…"> | Shows a broken-image placeholder. |
Common reasons people do this
- Testing that an SVG upload path validates and sanitises input.
- Verifying an icon build pipeline fails on a malformed source file.
- Checking that an SVG sanitiser rejects rather than partially accepts bad input.
- Producing malformed vectors for a rendering test suite.
How to corrupt a SVG file
- Drop your .svg 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.
SVG FAQ
Why does SVG fail harder than HTML?
Because browsers parse SVG as XML, which is strict. HTML has error recovery built into the specification; XML does not.
Will the file still open in a text editor?
It will open, but the content is mojibake, invalid UTF-8 is injected, so it is no longer readable text.
Does it work on compressed SVGZ?
Yes, but SVGZ is gzip underneath, so it is handled as a gzip archive and breaks as a whole.
Can I keep it looking like valid SVG?
Light level preserves most of the markup, so it still reads as SVG at a glance while failing to render.