🪶 SVG Optimizer
Paste SVG code to strip comments, metadata and editor junk, round coordinates, and see exactly how many bytes you saved — with a live preview.
Frequently Asked Questions
What does the optimizer remove?
XML comments, <metadata> blocks, Inkscape and Sodipodi editor elements and attributes (inkscape:*, sodipodi:*, and their xmlns declarations), the redundant version and xml:space attributes, whitespace between tags — and optionally <title>/<desc> elements. The visible drawing is never changed.
Is rounding coordinates safe?
For nearly all graphics, yes. Editors export coordinates like 50.000000186 that carry no visible detail; rounding to 2 decimals keeps precision to 1/100th of an SVG unit. For icons drawn on a small viewBox (e.g. 0 0 16 16), 2–3 decimals is still far finer than a screen pixel. Check the preview — if anything looks off, raise the precision or untick the option.
How much smaller will my SVG get?
Depends on the source: hand-written SVGs may only shrink a few percent, while files exported from Inkscape, Illustrator or Figma often carry heavy metadata and long decimals and can shrink 30–70%. The tool shows exact bytes before and after.
Should I remove <title> and <desc>?
For decorative images, yes — they only add bytes. Keep them (untick the option) when the SVG conveys meaning, because screen readers announce <title> as the image's accessible name.
Is the preview safe for untrusted SVG files?
Yes. The preview renders the SVG through an <img> element, where browsers disable scripts and external requests inside SVG content. And since the whole tool runs locally, the file itself never leaves your device.
How is this different from SVGO?
SVGO is a Node.js build-tool with dozens of aggressive plugins (path merging, transform collapsing). This tool covers the safe, high-value subset — junk removal, whitespace and decimal precision — instantly in the browser with no install, which is usually enough for icons and exported graphics.