Make SVGs small without breaking them.
Paste SVG code or drop a file. We strip editor metadata, round absurd coordinates, remove useless attributes, and shave whitespace — without touching the visible result. See the byte count drop in real time, then copy the clean version or download it.
SVGs, explained.
What's actually getting removed?
Mostly junk: editor metadata (Illustrator/Inkscape/Figma tags), XML comments, unused <defs>, and default attribute values the browser assumes anyway. None of it affects how your SVG looks.
What's "rounding numbers"?
Design tools often export 12.857142857142858 when 12.86 is visually identical. Rounding to 2 decimal places typically saves 20–40% of file size on its own.
Will it break my SVG?
No. All optimizations preserve visual output. If you're pixel-paranoid, use the Visual check preview below — if "before" and "after" look identical, you're safe. At precision 2, differences are below what the human eye can detect.
When should I use precision 3 or 0?
Precision 3 for icons with very fine detail (small logos, complex line art). Precision 0 for SVGs used at large sizes where decimal precision is wasted. Most icons work fine at 2.
Why optimize SVGs anyway?
SVGs are often used as inline icons (one per component). On a page with 30 icons, the difference between 2KB vs 800B per icon is real. Also: less code = faster parse time, less DOM bloat.
Is this SVGO under the hood?
No — we wrote a minimal optimizer that runs in-browser with no dependencies. It does fewer things than SVGO but the things it does, it does fast and correctly. No WebAssembly, no libraries, just a few hundred lines of regex and DOM work.