When this tool is useful
Reducing obvious active-content exposure before reviewing a simple icon, logo, or illustration in a controlled destination that accepts SVG.
How local processing works
A strict XML parser rejects document types and entities, walks bounded elements and attributes, keeps only an explicit graphics allowlist, accepts only local fragment references, and deterministically serializes the reduced tree.
How to use it
- Prepare and preserve the source: Keep the unchanged source, review the intended destination, and begin with conservative limits. Reducing obvious active-content exposure before reviewing a simple icon, logo, or illustration in a controlled destination that accepts SVG.
- Run the bounded local operation: Process only in this browser and stop on unsupported, malformed, or ambiguous input. A strict XML parser rejects document types and entities, walks bounded elements and attributes, keeps only an explicit graphics allowlist, accepts only local fragment references, and deterministically serializes the reduced tree.
- Inspect the result: Review the removal report and serialized text, compare appearance in a sandboxed viewer, confirm there are no external references or unexpected elements, and prefer raster output for untrusted distribution.
Important limitations
This is risk reduction, not a security certification. Unsupported content is removed or rejected, visual appearance can change, parser and destination differences remain, and a reduced SVG must still be treated as untrusted.
Verify the downloaded result
Review the removal report and serialized text, compare appearance in a sandboxed viewer, confirm there are no external references or unexpected elements, and prefer raster output for untrusted distribution.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this tool useful?
Reducing obvious active-content exposure before reviewing a simple icon, logo, or illustration in a controlled destination that accepts SVG.
What does the local operation do?
A strict XML parser rejects document types and entities, walks bounded elements and attributes, keeps only an explicit graphics allowlist, accepts only local fragment references, and deterministically serializes the reduced tree.
Which limitations matter?
This is risk reduction, not a security certification. Unsupported content is removed or rejected, visual appearance can change, parser and destination differences remain, and a reduced SVG must still be treated as untrusted.
How should I verify the result?
Review the removal report and serialized text, compare appearance in a sandboxed viewer, confirm there are no external references or unexpected elements, and prefer raster output for untrusted distribution.