Account

What new tool do you want?

Developer Tools

SVG Optimizer (Minify SVG)

Shrink SVG files by removing editor metadata (Inkscape, Illustrator, Sketch), comments and whitespace, and rounding long decimals — with the size saving shown. Paste the SVG code.

How to use

  1. 1Paste SVG code (open the .svg in a text editor to copy it).
  2. 2Choose the decimal precision and copy or download the optimized SVG.

How it's calculated

Removes XML declarations, comments, <metadata>, editor namespaces and attributes, empty groups; rounds numbers with 3+ decimals; collapses whitespace in markup and path data.

Frequently asked questions

Will it change how my SVG looks?

At 2–3 decimal places, no visible change for icons and illustrations. Use 1 decimal for tiny icons, 3 for large, detailed drawings.

Why keep <title>?

<title> gives the graphic an accessible name for screen readers — keep it for meaningful images.

How does this compare to SVGO?

It applies the safest, highest-impact cleanups. SVGO can additionally merge paths and rewrite shapes.

Worked example: SVG Optimizer

A Sketch-exported icon with an XML declaration, a Sketch comment, the sketch: namespace and attribute, a version="1.1" attribute, an empty <g></g>, a <metadata> block, and a path with 6-decimal coordinates like M 12.123456 2.987654 L 20.5 20.5 — all of that strips down to <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><title>Icon</title><path d="M12.12 2.99L20.5 20.5L3.25 20.5Z"/></svg> at 2 decimal precision. Every byte removed here (the Sketch metadata, the redundant version attribute, the empty group, the whitespace inside the path data) is invisible to the rendered output — nothing about how the icon actually looks on screen changes.

Why rounding decimals is the one setting that can visibly matter

Editor tools like Illustrator and Figma often export path coordinates with far more decimal precision than any screen can actually render — a coordinate like 12.123456 implies sub-pixel precision that's meaningless at typical icon sizes, so rounding it to 12.12 (2 decimals) produces no visible difference for normal icon and illustration use. The precision setting exists because that's not universally true: a large, highly detailed technical drawing scaled up significantly can show faint seams or misalignment at 1-2 decimal places that aren't visible at the same precision on a small icon, which is why the tool recommends 1 decimal for tiny icons but 3-4 for large, detailed artwork.

Why this keeps <title> by default and what SVGO does differently

An SVG's <title> element is read aloud by screen readers the same way an <img>'s alt text is, giving an otherwise purely visual graphic an accessible name — which is why it's preserved by default here even though removing it would save more bytes. This tool deliberately limits itself to safe, purely structural cleanups: stripping editor metadata, comments and namespaces, collapsing whitespace, and rounding numbers — all changes that can never alter the rendered shape. A dedicated tool like SVGO goes further, actually rewriting path data into more compact equivalent forms and merging redundant paths together, which can save more space but carries more risk of subtly changing rendering in edge cases — this tool trades some additional savings for a guarantee of zero visual risk.

Sizes are shown in kilobytes with two decimals

Decimal places opens on 2, and I can pick 1, 3, or 4. Keep title and desc starts on. An empty box stays empty. Text that does not contain an svg element stops with a message that it does not look like SVG markup. Original size, optimized size, and the amount saved are shown in kilobytes with two decimal places. The download is an svg file. I turn the title switch off when I want those elements removed, and I leave it on when a screen reader should still find the title.

Related tools

More: Developer Tools