Metadata cleanup is the safest first step
Comments, editor metadata, and redundant XML declarations are often removable without affecting rendering. These changes reduce noise and can improve privacy when the SVG was exported from a design tool.
Clean SVG comments, metadata, editor attributes, XML declarations/DOCTYPE and extra whitespace, and shorten color notation. Browser only. Processing stays local while reducing file size.
Or paste SVG code directly into the field below.
SVG optimization can remove comments, metadata, editor-specific attributes, whitespace, and optional descriptive nodes, but not every byte is disposable. Accessibility text, IDs used by CSS or JavaScript, and complex path data may be functionally important, so optimization should be reviewed visually and structurally.
Comments, editor metadata, and redundant XML declarations are often removable without affecting rendering. These changes reduce noise and can improve privacy when the SVG was exported from a design tool.
Removing title or desc elements can reduce size, but those nodes may describe the graphic to assistive technology. Keep them when the SVG relies on its own accessible name or description.
The tool focuses on structural cleanup and text-level optimization rather than aggressively rewriting path geometry like a full SVGO pipeline. That conservative approach reduces the chance of altering shapes but also means some SVGs will have modest size savings.