SVG Optimizer and Minifier
Use SVG Optimizer and Minifier, review the result, and keep the original until the output is checked.
Keep your original file until you have checked the downloaded result. Browser memory and format support vary by device.
This conservative optimizer removes comments, metadata blocks, and unnecessary whitespace while keeping viewBox values.
How to use SVG Optimizer and Minifier
- Select one .svg file; this page takes a single document, not a batch.
- Choose what to strip - Remove metadata, title, and description blocks, and Collapse whitespace between tags are both on by default.
- Press Optimize SVG and compare the byte counts, then check the Optimized SVG preview still draws the same picture.
- Download writes <name>-optimized.svg beside your original.
What SVG Optimizer and Minifier actually does to your file
What this removes is the text layer of the file: XML comments, the metadata/title/desc blocks, and the indentation between tags. That is most of the bulk in a file exported from a design tool, and very little in an already-minified icon - it does not simplify paths, reduce coordinate precision or merge shapes. Leaving the title and description stripped also removes the accessible name and tooltip a screen reader or browser would have read, so tick that option off for standalone icons.
SVG Optimizer and Minifier FAQ
What does SVG Optimizer and Minifier do?
Reduce SVG markup noise with a conservative browser-based optimizer that keeps viewBox values.
Which files work with SVG Optimizer and Minifier?
This category commonly supports SVG and exported PNG. Use the accepted file types shown in the uploader, because support varies by browser and by the engine behind each tool.
Is optimising the same as compressing?
No. Optimising removes redundant markup and keeps the result equivalent, while compression trades quality for bytes. Optimising first is usually the cheaper win.
Will my original file be changed?
No. The work is done on a copy in this tab by the browser's own SVG document model, and the result arrives as a separate download, so your original is still there if you need it.
How is my file processed?
It is not uploaded. The processing is done locally by the browser's own SVG document model, so the practical ceiling is your device's memory and the limit shown beside the uploader - no queue, no account, no copy on a server.
Does it change the viewBox?
No. The current workflow keeps existing viewBox values while cleaning selected markup.