SVG optimizer

Why an exported SVG is bigger than it needs to be

Design tools save a lot more than the shape of your icon. A file exported from Illustrator, Figma or Inkscape usually carries an XML declaration, editor-specific metadata, comments, long generated ids on every element, empty groups left over from editing, and coordinates with far more decimal places than a screen can ever show. None of that changes how the icon looks, but it adds up in a page that loads dozens of icons or in an email signature with limits on size.

What gets cleaned

• Comments left by design tools or written by hand.
• Editor metadata, such as Inkscape and Adobe Illustrator namespaces, the sodipodi:namedview block, and long ids like path1234 that only the editor needs.
• Empty groups such as <g></g>, left behind after edits.
• Extra whitespace between tags, repeated spaces and line breaks that only matter for reading the source, not for rendering it.
• Decimal precision. Coordinates with six or seven decimal places are rarely needed; rounding to one or two decimals shrinks the file with no visible difference.
• Fixed width and height, optionally, so the icon scales freely wherever you place it, using only its viewBox.

See the difference

Below the result you see the size before and after, and the percentage saved, so you know at a glance whether it was worth it. Icons with long paths and many decimal places usually shrink the most; already tidy, hand-written SVG shrinks less.

What it does not do

This is a text-based cleanup, not a full XML optimizer: it does not merge overlapping shapes, simplify paths mathematically or convert strokes to fills, which a dedicated design tool does better. Very unusual or malformed SVG may not clean up perfectly. Nothing is uploaded; the code is processed in your browser. To turn the result into a PNG, use the SVG to PNG converter.