Online SVG Optimizer
Clean and compress SVGs. Removes Inkscape metadata, empty groups and unnecessary code. No dependencies.
Built by
Miguel Ángel Colorado Marin
Built by
Miguel Ángel Colorado Marin
Full-Stack Developer · Guadalajara, España
I develop web apps, digital tools and full projects — from design to deployment.
How to optimize your SVG
- 1
Paste the SVG or upload the file
Enter the code in the left area or upload the .svg directly. Optimization is automatic and instant.
- 2
Check the statistics
See the original size, optimized size and percentage reduction achieved in the cards below.
- 3
Check the visual preview
Verify that the optimized SVG looks the same as the original before using it.
- 4
Download or copy the result
Download button to save the .svg, or copy to use it directly in your HTML/CSS code.
Why optimizing SVGs matters
An SVG exported directly from Inkscape or Adobe Illustrator can contain between 30% and 70% of code that never renders in the browser: creation metadata, editing layer information, proprietary Inkscape attributes, alignment guides and internal comments. All that code adds download weight and unnecessary parsing time.
For web projects where SVGs are used as icons, logos, background illustrations or inline graphics, the difference between an optimized and unoptimized SVG can be significant. On pages with many SVGs, the cumulative savings in network transfer and DOM parsing time translates directly into better loading performance and better Core Web Vitals scores.
Frequently asked questions
Why are Inkscape SVGs so large?
Inkscape adds its own metadata, namespace attributes (inkscape:, sodipodi:), layer information, guides and other data useful for editing but unnecessary for displaying the SVG in a browser.
What exactly does it remove?
HTML comments, metadata/title/desc elements, sodipodi:namedview, all attributes prefixed with inkscape:/sodipodi:/dc:/cc:/rdf:, global attributes like id/version/xml:space, empty groups and redundant whitespace.
Can optimization break the SVG?
In some cases. SVGs with SMIL animations, embedded scripts or internal references to removed ids could be affected. Always check the preview before using the result.
Why doesn't it use SVGO?
It uses the browser's native DOM parser, no external dependencies. Faster to load, 100% private and sufficient for 90% of cases. For more aggressive optimizations (path simplification), SVGO CLI would be more complete.
How much can an SVG be reduced?
An Inkscape SVG with metadata can be reduced 30-70%. Already-clean SVGs will have smaller reductions (5-15%). The biggest savings come from metadata and namespace attributes.
Related tools
Embed this tool
<iframe src="https://miguelacm.es/embed/svg-optimizer" width="100%" height="700" style="border:none;border-radius:16px;" loading="lazy"></iframe>