ValidStitch accepts SVG as a vector source for digitizing handoff, but the upload pipeline rejects SVGs that fail the safety scan or that the parser can't reliably digest. Here's how to identify what's wrong and fix it.
1. Embedded scripts (most common rejection)
SVGs created or exported by interactive web tools sometimes include <script> tags, javascript: URLs, or event handlers (onclick, onload) that run when the SVG renders in a browser. ValidStitch rejects any SVG containing executable content as a security measure. Fix: open the SVG in a text editor and strip the script tags, or re-export from Illustrator / Figma / Inkscape with 'web optimized' or 'minimal' export settings — those drop scripts by default.
2. foreignObject blocks
foreignObject elements embed HTML inside the SVG. Some browser tools use them to layer text or images; the parser can't reliably convert them to stitch geometry. Fix: open in Inkscape, convert text to paths (Path → Object to Path), and re-save. The foreignObject becomes regular SVG paths the digitizer can work with.
3. Missing or zero-sized viewBox
An SVG without a viewBox attribute (or with a viewBox of '0 0 0 0') has no defined drawing region — the parser can't compute extents. Fix: open in any vector tool and re-export. Modern exports include the viewBox by default; the issue is usually with files generated by an automation script.
4. File size above 200 MB
ValidStitch caps individual uploads at 200 MB. Most SVGs are well under that; if you're hitting the cap, the file probably contains embedded raster images (PNG / JPEG) inside an <image> element. Those usually shouldn't be in a digitizing source. Fix: extract the raster, vectorize it separately, and re-export the SVG with only the vector content.
5. Corrupt or truncated download
If the SVG was downloaded over a flaky connection, the XML might end mid-element. Browsers tolerate this; the parser doesn't. Fix: re-download on a wired connection. The validator's error message will mention 'unexpected end of input' or 'malformed XML' for this case.
If none of the five resolve, attach the SVG to a support ticket — we can reproduce server-side and tell you which parser branch rejected.