scriptiii
100% Client-Side

Safe subset only

SVG optimizer

Drop the comments, editor attributes and dead precision that design tools leave behind — and see the render beside the result, so smaller never means broken.

Optimising happens in this tab. Your artwork is never uploaded.

Short answer: paste or open the SVG and press optimise. Comments, metadata, editor attributes, empty groups and long decimals go; the drawing does not. The result is rendered above the code and downloaded as .svg.

What is safe to remove, and why

Editor attributes are notes to the editor, not instructions to the renderer. Comments are invisible. Empty groups draw nothing. A coordinate with fifteen decimals came from a transform matrix, and rounding it to two moves the point by less than a pixel while shrinking the file noticeably. None of that is guesswork — each one is a category this tool handles and nothing else.

The optimisations it refuses

Path simplification, transform flattening and group merging all change geometry. They save more and they break artwork, which is why they live in dedicated tools that can show you a pixel diff. A page that quietly rewrote your logo to save four kilobytes would be worse than one that leaves it alone.

SVG optimizer questions

What gets removed?

XML declarations and doctypes, comments, metadata/title/desc blocks, editor namespaced attributes, namespaces nothing references any more, empty groups, and decimals past your chosen precision. Every one of those is droppable without changing a single rendered pixel.

What is deliberately not removed?

Paths are not re-drawn, shapes are not merged, transforms are not baked and groups are not retyped. Those optimisations can change the artwork, and this page shows a live render of its own output precisely because that is the failure mode worth checking. If you need path rewriting, use a dedicated tool that renders before and after.

Why does it render the result next to the code?

Because "smaller file" is only good news if the picture is the same. The preview is drawn from the optimised markup, so a broken transform or a dropped attribute is visible immediately instead of at the printer.

How much does it usually save?

On a file exported from a design tool, with comments and editor attributes along for the ride, 10–40%. On a hand-written or already-optimised SVG, almost nothing — and the tool says so rather than claiming a win it did not make.

Related tools

SVG to PNGRasterise the optimised file.Barcode generatorThe opposite direction: markup out.Image converterPNG, JPG and WebP between each other.