Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Strip unnecessary metadata and whitespace from SVG markup to reduce file size.
Paste valid SVG markup to see a preview and cleaned output.
SVG files exported from design tools like Illustrator or Figma often carry significant bloat -- editor-specific metadata, XML comments, unnecessary whitespace, and namespace declarations that aren't needed for the image to actually render. This tool strips that safely, reducing file size without changing how the SVG looks.
Paste your SVG markup into the input box. The cleaned output appears instantly, with a size comparison showing how much smaller the result is, ready to copy or download.
XML comments, editor-specific metadata elements (like Illustrator/Inkscape-specific tags), redundant whitespace between elements, and unnecessary attributes that don't affect rendering are all stripped, while preserving every visual element (paths, shapes, groups, styles) that actually determines how the image looks.
Web developers preparing an SVG icon or logo for production, where every extra kilobyte affects page load time. Designers cleaning up an exported SVG before handing it off to a development team. Anyone embedding an SVG directly inline in HTML who wants to avoid shipping unnecessary editor cruft.
This performs safe cleanup only -- it doesn't simplify paths, merge shapes, or perform aggressive geometric optimization the way a dedicated SVG optimization library might. The goal is removing genuinely unnecessary content without any risk of visually altering the image.
The tool offers six switches, all enabled by default, so you can decide how much to strip. Each one targets a different kind of overhead.
Imagine a small icon exported with an XML declaration, a comment, a metadata element, a title, and a circle with an empty stroke attribute. After cleaning, only the svg element and the circle remain, with no blank lines. The size comparison shows both the byte counts and the reduction, so you can see the saving immediately. Small icons often shrink by a noticeable share because the overhead is large relative to the actual shapes, while a file made mostly of long path data will see a smaller percentage saving, since the paths themselves are untouched.
If the SVG conveys meaning, for example a logo or a chart, turn off the metadata option so the title and description remain, or add an aria-label to the element in your HTML afterward. If the graphic is purely decorative, removing them is fine, and you can mark it as decorative in the page markup. Check how the graphic is used before you strip anything that a screen reader relies on.
Whitespace and comment removal is only a first pass. If you need much smaller files, consider a full optimizer in your build process that rounds path numbers and merges shapes, and serve SVGs with gzip or Brotli compression, which reduces text-based files further.
No -- this tool only removes content that doesn't affect rendering (comments, metadata, redundant whitespace), leaving every visual element untouched.
Design tools like Illustrator and Figma embed editor-specific metadata (layer names, tool version info, editing history hints) that's useful for re-opening the file in that same tool, but completely unnecessary once the SVG is just being displayed on a webpage.
If the metadata, title, and description option is enabled, yes. Turn it off when the image needs an accessible name, or add an aria-label in your HTML.
Yes. Each cleaning step has its own toggle, so you can keep comments, titles, or other parts while still removing whitespace.
The input needs to look like SVG, meaning it should contain an svg element. Make sure you pasted the full markup and not a fragment or a different file type.
No. It leaves paths and shapes untouched, so files dominated by long path data will see smaller savings.
Reference: NIST Weights and Measures