All tools
Design tools

SVG Optimizer

Remove Inkscape, Illustrator and Sketch metadata, unused namespaces and XML comments from SVGs. Reduce file size by up to 70% without any visual change.

Inkscape metadata Illustrator tags Unused namespaces Up to 70% smaller Preview output Copy or download
Get started free Sign in

Free · No credit card · 50 credits/day

What gets removed vs. kept

Element Action Why
sodipodi: / inkscape: namespace Removed ✂️ Inkscape-only metadata invisible to browsers
dc: / cc: / rdf: metadata Removed ✂️ Dublin Core author/license info not needed for rendering
XML comments <!-- --> Removed ✂️ Zero visual impact, pure file bloat
Unused namespace declarations Removed ✂️ xmlns: declarations with no matching elements
Visible paths and shapes Kept ✅ All rendering content is preserved exactly
Gradients, masks, filters Kept ✅ Defs section preserved — only unused defs removed

Frequently asked questions

Why are SVGs exported from Inkscape so large?

Inkscape embeds its own metadata namespace (sodipodi:, inkscape:), Dublin Core tags (dc:, cc:, rdf:), creator info, document history, grid definitions and layer labels. These are useful in Inkscape but invisible to browsers and often double or triple the file size of a simple icon. Optimization strips all of it while keeping visual paths intact.

What does SVG optimization actually remove?

Optimization removes: editor metadata, XML comments, unused namespace declarations, hidden elements, default attribute values (fill="black" is already the default), whitespace between tags, empty groups, and redundant transforms like translate(0,0). What stays: all visible paths, shapes, text, gradients, masks, and filters.

Will optimizing an SVG break it?

Aggressive optimization can break SVGs that rely on IDs for CSS or JS selectors, or animations referencing specific element IDs. Conservative optimization (metadata and comments only) is safe. This tool uses conservative defaults. Always preview the optimized SVG before using it in production.

Should I inline SVGs or use an img tag?

Inline SVG: styleable with CSS, accessible, animatable — but adds to HTML size. <img src="icon.svg">: cached separately, simpler markup, but not CSS-styleable. <use href="sprite.svg#icon">: best for repeated icons — one cached file, styleable with currentColor. Rule: inline for unique icons, sprite for repeated icons, img for decorative static SVGs.

Related design tools

More tools for SVG and image workflows.

Icon Finder

Search 500+ open-source SVG icons — already optimized, MIT licensed.

Favicon Generator

Convert an SVG icon into PNG favicons at all required sizes.

Image Compressor

Compress the rasterized versions of your SVG exports.

Ship leaner SVGs today

Free account. 50 credits per day. Access to 75+ tools instantly.

Create free account →