Strip editor metadata, comments, and unnecessary coordinate precision from a whole batch of SVG files at once. Everything runs in your browser — files are never uploaded.
Design tools (Illustrator, Figma, Inkscape, Sketch) embed editor-specific data in every SVG export — XML comments, an xmlns:inkscape/xmlns:sodipodi namespace and its associated attributes, a <metadata> block with RDF/Dublin Core data about the file, and path coordinates carrying far more decimal precision than a screen can render (a value like 142.38571429... renders identically to 142.39 at any realistic display size). None of this affects how the SVG looks — it's purely bytes the browser has to parse and discard. This tool strips comments, editor namespaces and their attributes, the metadata block, and rounds coordinate precision in d and points attributes to the number of decimal places you choose, then removes any <g> or <defs> elements left empty by those removals.
<title> and <desc> elements, along with aria-* and role attributes, give an SVG an accessible name and description for screen readers — they cost a few bytes and provide real value, unlike genuinely inert editor metadata. This tool leaves them alone by default; the option to strip them too exists for cases where the SVG is a purely decorative background image with aria-hidden="true" already set elsewhere, where they add nothing.
SVGs exported directly from Illustrator or Figma commonly shrink 40–80% after this kind of cleanup — the exact number depends heavily on how complex the original paths are and how much editor metadata the exporting tool included. Simple icons with already-clean markup (hand-written or previously optimized) see much smaller reductions, since there's less bloat left to remove.
At 2 decimal places (the default), no — sub-hundredth-of-a-pixel differences aren't visible on any current display. Going down to 1 decimal place can occasionally introduce a barely perceptible shift on very large, zoomed-in graphics with fine detail; if you're optimizing something like a detailed illustration meant to be viewed at large sizes, 2 or 3 decimal places is the safer choice.
No — this is a lighter, custom-built cleanup pass covering the changes that account for most of the size reduction (metadata, comments, precision), not a full port of SVGO's complete plugin set (which also merges paths, converts shapes to paths, and other more invasive transforms). For most exported icons and illustrations, that covers the bulk of the achievable savings without the risk of more aggressive structural changes.
No. Every file is read and processed with your browser's FileReader and plain string operations — nothing is sent over the network, which you can confirm by checking the Network tab in your browser's dev tools while a batch runs.