About SVG Optimizer

SVG Optimizer cleans and minifies SVG markup by stripping elements and attributes that bloat file size without affecting the rendered graphic. It removes XML declarations, HTML comments, <metadata> blocks, <title> and <desc> elements, empty <g> groups, editor-specific namespaces (Inkscape, Sodipodi, Adobe Illustrator), and excessive whitespace. It also rounds floating-point coordinates to a configurable decimal precision to reduce numeric bloat.

A side-by-side preview lets you confirm the optimized SVG looks identical to the original before you download. All processing is done locally in your browser — your SVG code and any embedded brand assets stay entirely on your machine.

Common Use Cases

Reducing SVG icon file sizes before bundling them into a web app to improve page load performance
Cleaning Inkscape or Illustrator exports that contain large metadata blocks and editor-specific namespaces
Preparing SVG assets for inline embedding in HTML to minimize page weight
Prettifying hand-written or minified SVG markup for easier reading and manual editing

How to Use

Paste SVG code into the Input panel or click "Load Example" to try the built-in demo
Select which optimizations to apply using the checkboxes in the Options panel
Click "Optimize" to run the selected transformations — the savings percentage appears in the stats bar
Compare the original and optimized previews, then click "Download" to save the result as a .svg file

Frequently Asked Questions

Will optimization break SVGs that use IDs for animations or gradients?

The "Remove unused IDs" option is unchecked by default precisely to protect IDs that are referenced internally (e.g., by <use>, <clipPath>, gradient <stop> elements, or SMIL animations). Only enable it if you have confirmed your SVG contains no internal ID references. All other options are safe for most SVGs.

What decimal precision should I use for coordinate rounding?

A precision of 2 (the default) is a good balance for most icons and illustrations — it rounds values like 50.000000 to 50 while keeping sub-pixel accuracy for curves. For large illustrations with complex paths, try precision 1 for maximum compression; for icons that need crisp sub-pixel rendering at small sizes, precision 2 or 3 is safer.

How does this differ from tools like SVGO?

SVGO (SVG Optimizer Node.js library) is a full-featured command-line tool with dozens of plugins including path merging, transform collapsing, and shape conversion. This browser tool focuses on the most impactful and safe operations — metadata removal, whitespace collapse, and coordinate rounding — with zero setup, no Node.js required, and full privacy since everything runs locally.