SVG Optimizer — smaller files, identical rendering
Optimize SVGs locally with the SVGO engine: strip editor metadata, junk attributes and excess precision — typical savings run 30-80%. Three intensity levels with a before/after preview, viewBox always kept, batch processing with ZIP export. Files never uploaded. Works on desktop, tablet & mobile.
SVGs exported from design tools (Figma / Illustrator / Sketch) are stuffed with editor metadata, comments, default attributes and needlessly long decimals — none of it affects rendering, yet it often makes up over half the file. SVG optimization strips that cruft by rule: this tool runs the industry-standard SVGO engine (browser build) with Safe / Standard / Aggressive levels, always preserves the viewBox (removing it breaks responsive scaling), and shows a side-by-side before/after render so you can confirm nothing shifted before downloading. Batch processing with ZIP export, plus one-click copy of the optimized markup for inlining. Everything runs locally in your browser — files never upload.
When you need it
Before shipping web icons
Smaller inline or referenced SVGs mean faster pages.
Design handoffs
Clean the editor junk out of Figma / AI exports before delivering.
Icon set maintenance
Run a whole icon set through in one batch — consistent and lean.
The trade-offs
- Typical 30-80% smaller with identical rendering
- Three controlled levels; viewBox always preserved
- Batch + ZIP + one-click copy of optimized markup
- Aggressive level reduces numeric precision — complex artwork may shift subtly, so check the preview
- SVGs with scripts / animations / filters deserve a per-file check after optimizing
- Already-optimized SVGs won’t shrink much further
SVG Optimizer FAQ
Safe and Standard levels only strip redundant data — rendering is identical. Aggressive lowers coordinate precision, which can subtly shift very complex artwork — the built-in before/after preview lets you verify before downloading.
The viewBox is what makes an SVG scale responsively; removing it breaks sizing in different containers. This tool keeps it at every level — a key difference from some “maximum minify” tools.
Yes, but SMIL/CSS animations and script-referenced ids or classes may be renamed or cleaned — verify the result per file, and prefer the Safe level for these.
No. The SVGO engine runs right in your browser; files are never uploaded or stored. Previews render in an isolated way, so SVGs containing scripts are never executed.