Strip metadata, editor junk and excess whitespace from SVG files — safe cleanup that never changes how the graphic renders. All in your browser.
Design tools are generous with what they save. An icon exported from Illustrator or Inkscape carries editor metadata, document properties, licensing blocks, layer names and formatting whitespace — none of which a browser needs to draw the image. On a 3 KB icon, that overhead is often half the file.
XML comments, <metadata> and <desc> blocks, Inkscape and Sodipodi editor attributes, unused editor namespaces, and whitespace between tags. What it deliberately keeps: all geometry, styles, viewBox, IDs and classes (they may be referenced by CSS or scripts), and accessibility-relevant structure. The output renders pixel-identically — verify with the preview on each card.
SVGs are often inlined into HTML or loaded on every page (logos, icons), so their bytes are paid on each visit. Because SVG is text, it also gzips beautifully — but gzip can't fix bloat as well as removing it at the source. Optimize once at export time and every page load benefits.
No. This optimizer only removes things that don't affect rendering — comments, metadata, editor-specific attributes and whitespace. Paths, shapes, styles and IDs are left untouched, so the drawing is pixel-identical.
Files exported from Illustrator, Inkscape or Figma typically shrink 20–60%, because those tools embed generous metadata and formatting. Hand-written SVGs shrink less — they were never bloated.
They may be referenced by CSS, JavaScript or internal links within the SVG. Removing them can silently break styling and animation, so a safe optimizer leaves them alone.
No — parsing and cleanup happen in your browser with the built-in DOM parser. Nothing is sent to any server.