katlab tools/svg-optimizer support on Ko-fi

SVG Optimizer · Minify SVG

Clean and minify SVG with SVGO — safe defaults, a live before/after preview and real byte savings, entirely in your browser.

SVGs are optimized locally. Nothing is uploaded to a server.
…or paste SVG markup
Precision (decimals)
3
Original
Original SVG
Optimized
Optimized SVG
⤓ Download SVG
View optimized markup

How to optimize an SVG (free)

  1. Drop your .svg file onto the box above, or paste the markup.
  2. Adjust precision if you like — fewer decimals means a smaller file, more decimals means more exact curves.
  3. Check the before / after preview to confirm it looks identical, then download or copy the optimized SVG.

Safe by default — it won't break your SVG

The reputation of an SVG optimizer lives or dies on whether it silently breaks files, so this one ships conservative defaults. The viewBox is always preserved — removing it is the classic mistake that stops an SVG from scaling. Element ids are kept by default too, because they're used by <use> sprites, CSS selectors, animations and external references; only turn on rewrite IDs for a standalone, self-contained icon. The side-by-side preview on a transparent checkerboard lets you verify the result pixel-for-pixel before you trust it.

Why SVGs from design tools are so big

Exports from Illustrator, Figma, Sketch and Inkscape carry a lot of invisible weight: editor metadata, comments, hidden layers, empty groups, default attributes and coordinates with 10+ decimal places. SVGO — the same optimizer that powers most build pipelines — removes that redundancy and rounds numbers to a sensible precision without changing the rendered image. Editor exports commonly drop 40–70%.

Runs entirely in your browser

SVGO is compiled to run client-side, so your file is optimized inside the page — nothing is uploaded, cached on a server, or logged. It works offline once loaded, and it's safe for unreleased logos and brand assets.

My SVG barely got smaller — why?

If most of the bytes are an embedded raster (a <image> with a base64 PNG or JPEG inside), there's little markup to optimize. In that case the weight is the picture, not the SVG — run it through image compression instead, or export the artwork as real vector paths.