What does an SVG optimizer actually remove?

It strips things that browsers never render — XML comments, editor metadata (Inkscape, Illustrator and Sodipodi namespaces), empty and default attributes, redundant whitespace between tags, and the optional XML declaration and DOCTYPE. It also rounds long coordinate numbers to a chosen precision, which is usually where the biggest savings on hand-exported icons come from.

Will optimizing change how my SVG looks?

The default passes are visually lossless — they only remove data the renderer ignores. The one pass that can shift appearance is aggressive coordinate rounding at precision 0 or 1 on a very small viewBox, so the live preview updates instantly to let you confirm the image still looks right before you copy it.

What is the viewBox and why keep it?

The viewBox defines the internal coordinate system and aspect ratio of the SVG, written as 'min-x min-y width height'. Keeping it while dropping the fixed width and height attributes makes the SVG scale fluidly to whatever container it sits in, which is ideal for responsive icons and logos.

Is my SVG uploaded anywhere?

No. Everything runs locally using your browser's built-in XML parser and serializer. The markup never leaves your device, and your last input plus your chosen passes are remembered only in this browser via localStorage.

How much smaller will my file get?

It depends entirely on the source. Editor exports from Illustrator or Inkscape often shrink 40 to 70 percent because of stripped metadata and rounded coordinates, while an already hand-written SVG might only drop a few percent. The savings bar shows the exact figure for your file.

Can I read the dimensions of an SVG without an image editor?

Yes. Paste the markup and the metrics panel reports the width, height and viewBox immediately, along with how many elements and path nodes the file contains — handy for checking an icon's intrinsic size before placing it.

SVG Optimizer & Editor

An SVG optimizer and editor that cleans up vector markup the way a build pipeline would, but instantly and entirely in your browser. Paste or upload an SVG and it strips the data that browsers never render — comments, editor metadata, empty and default attributes, redundant whitespace — rounds bloated coordinate numbers to a precision you choose, and reports the exact byte savings. It is built for designers exporting icons from Illustrator or Inkscape, developers inlining SVGs into a component, and anyone who just wants to know an SVG’s real dimensions without opening a heavy editor.

Vector files exported from design tools are notoriously wasteful. A single icon can carry kilobytes of inkscape: and sodipodi: namespace junk, a <metadata> block, decorative whitespace, and coordinates printed to fourteen decimal places like 120.000000000001. None of that affects the rendered image, yet it inflates every page that ships the file. This tool removes it in one pass and shows you the before-and-after size so the win is measurable, not guesswork.

How it works

The optimizer parses your markup with the browser’s native XML parser, so it understands real SVG structure rather than guessing with regular expressions. It then walks the document tree and applies the passes you have enabled: removing comment, metadata, title and desc nodes; deleting editor-namespaced elements and attributes; dropping empty and default attributes such as version="1.1" or x="0"; and rounding every coordinate-bearing value — path d data, points, transform, radii and stroke widths — to your chosen decimal precision. Finally it serializes the cleaned tree back to text, collapses the whitespace between tags, and optionally removes the XML declaration and DOCTYPE. A live preview renders the result so you can confirm nothing broke, and the metrics panel reports original size, optimized size, percent saved, the width, height and viewBox, and the element and path counts. Everything — including your last input and toggle choices — stays on your device.

Example

Take a 240×240 icon exported from a vector editor. The source weighs in with an XML prolog, a comment, an inkscape namespace declaration, a metadata block, a <desc>, version="1.1" x="0" y="0", an empty fill="", and coordinates like cx="120.000000" and r="100.123456". With the default passes enabled, the optimizer deletes the comment, metadata and editor data, removes the redundant root attributes, rounds 100.123456 to 100.12, collapses the indentation, and serializes a single tidy line of markup.

Pass	Effect
Strip editor data	Removes `inkscape:`/`sodipodi:` attributes and the `xmlns:inkscape` declaration
Remove metadata	Deletes `metadata`, `title` and `desc` nodes
Round coordinates	`100.123456` becomes `100.12` at precision 2
Collapse whitespace	Joins indented lines into compact markup

The result is typically 40 to 70 percent smaller, ready to copy straight into a component or save as optimized.svg. Switch to the readable view first if you would rather keep the markup indented for a codebase. No file is ever uploaded.