SVG Optimizer
Strip editor junk and excess precision from SVGs โ with a visual diff.
About this optimizer
Paste SVG markup or drop a file: editor junk, comments and XML prologs are stripped, numbers are rounded to sane precision, and whitespace collapses. Before/after previews render side by side so you can SEE nothing changed, and the size readout shows what you saved.
What's actually inside a bloated SVG
Open an exported SVG in a text editor and meet the freight: Inkscape and
Illustrator write their whole session state โ sodipodi: window
positions, inkscape: tool settings, RDF metadata blocks โ none of
which any browser reads. Then the coordinates: seven decimal places on every
point, when one decimal of an SVG unit is already sub-pixel at any sane
render size. Typical icons shrink 40โ70% from deletion and rounding alone,
with zero visual change โ this is why build pipelines run SVGO; this tool is
the paste-and-go version of the same idea, deliberately conservative: shapes,
styles and structure are untouched, and the two-decimal default keeps a wide
safety margin (drop to one decimal for icons, stay at three for fine
technical drawings). Inline SVG this small is often worth embedding straight
into HTML. Rasterising instead is SVG to PNG; animated
waves and blobs to optimize come from the wave maker and
the blob generator.
Frequently asked questions
Can optimizing break my SVG?
The passes here are conservative โ metadata, comments and precision only; shapes and styles untouched. The side-by-side preview exists precisely so you confirm before trusting it; fine technical drawings should use the 3-decimal setting.
How much smaller will my file get?
Editor exports typically drop 40โ70% โ the metadata alone is often half the file. Hand-written or already-optimized SVGs shrink little, and the tool says so.
What do the decimal settings mean?
How many decimal places coordinates keep. One decimal of an SVG unit is sub-pixel at normal sizes โ 2 is a safe default, 1 squeezes icons harder, 3 protects intricate drawings.
Why optimize SVGs at all?
Smaller downloads, faster parsing, and cleaner diffs in version control. An icon set carrying 60% dead weight is pure waste on every page load.