SVG Optimizer & Viewer: Frequently Asked Questions

Typical savings range from 30–70% for SVGs exported directly from design tools (Illustrator, Figma, Sketch, Inkscape). Simpler SVGs with less editor metadata may only reduce by 15–25%. The before/after stats show the exact saving for your specific file.

With the default settings, no — the optimisation only removes non-visual data. The live preview lets you verify this. Decimal rounding occasionally causes very slight changes to complex path shapes, but these are imperceptible at any normal rendering size.

SVGO (SVG Optimiser) is a Node.js command-line tool and the industry standard for SVG optimisation. This browser-based tool implements the most impactful SVGO operations (comment removal, metadata removal, whitespace collapse, decimal rounding) without requiring any installation. For a build pipeline, SVGO or its integrations (Vite plugin, webpack loader) are recommended.

This is rare but can happen if the optimiser adds indentation where the original had none, or if the original SVG was already highly optimised. If the output is larger, try enabling the Minify option.

Yes — the optimiser preserves all animation elements (<animate>, <animateTransform>, <animateMotion>) and SMIL animation attributes. CSS animations and JavaScript-driven animations in SVG are also preserved unchanged.

For simple decorative SVGs, yes. For SVGs where elements are referenced by other elements (<use href='#id'>), CSS (fill: url(#gradient)), or JavaScript, removing ids will break those references. The 'Remove editor attributes' option removes ids — uncheck it if your SVG uses internal references.