No upload, 100% local, no account

SVG optimizer

Paste or drop an SVG and shrink it with SVGO. Everything stays in your browser.

How SVG optimizer works

SVG Optimizer runs SVGO (SVG Optimizer) in a Web Worker inside your browser to minify and clean your SVG files without uploading them. SVGO applies a configurable set of plugins that remove comments, collapse whitespace, merge identical paths, convert shapes to their most compact representation and strip attributes that have no visual effect. The result is a smaller SVG that renders identically to the original.

SVG files produced by design tools like Figma, Illustrator or Inkscape often contain significant overhead: editor-specific metadata, empty groups, redundant transform attributes and namespace declarations that no browser needs. SVGO's default plugin set removes this overhead reliably. The optimised file is offered as a download and the percentage size reduction is shown so you can confirm the optimisation was worthwhile.

Written by Bastien Sulyan

How to use SVG optimizer, step by step

  1. Drop your SVG file onto the upload area or click to browse.
  2. The SVGO Web Worker runs the optimisation immediately with the default plugin set.
  3. View the percentage reduction and the original versus optimised file sizes.
  4. Click Download to save the optimised SVG to your device.
  5. If specific plugins cause rendering issues, adjust the plugin configuration and re-optimise.

Common use cases

  • A front-end developer optimises icons exported from Figma before committing them to a production asset pipeline, reducing each icon from 4 KB to under 1 KB.
  • A web designer cleans up SVG illustrations exported from Illustrator that contain layers of editor metadata invisible in the browser but bloating the file.
  • A developer building an icon font from SVG glyphs ensures each source SVG is clean and consistently structured before the font build step.
  • A performance engineer audits inline SVG in HTML and replaces each bloated original with an SVGO-optimised version to improve page weight.

Frequently asked questions

Will SVGO change how my SVG looks?

SVGO's default plugins are chosen to be visually lossless: the optimised SVG renders identically to the original in all standard browsers. Some aggressive plugins (such as those that round path coordinates very heavily) can introduce subtle rendering differences. If you notice a visual change, compare the original and optimised files in a browser and disable the specific plugin causing the issue.

Is the SVG file sent to a server for optimisation?

No. SVGO runs in a Web Worker inside your browser tab. The SVG text is read from your local disk, processed in JavaScript memory, and the output is returned to the page for download. The file content does not leave your device.

How much smaller will my SVG get?

Reduction depends on the source. SVGs exported from design tools with editor metadata commonly shrink by 30 to 70 percent. Hand-written SVGs that are already lean may see only 5 to 15 percent reduction. The tool shows the exact byte counts and percentage so you can evaluate each file individually.

Does optimisation affect SVG animations or JavaScript inside the file?

The configuration preserves animation elements and SMIL attributes. It does remove script elements: the tool adds the removeScripts plugin on top of the SVGO default preset, because an SVG you are about to embed should not carry executable code. Some plugins that clean up attributes could interact with animations if the animation references those attributes by ID; check the rendered output after optimising files that use complex animations.

Can I optimise multiple SVG files at once?

The current version processes one SVG file at a time. Drop a file, download the result, then drop the next file. Batch processing for multiple files in a single session is not available in this release.

What version of SVGO does the tool use?

The tool bundles SVGO running in a Web Worker. The bundled version is noted in the tool's about information. SVGO is actively maintained and the plugin API changed significantly between v1, v2 and v3; the current tool uses the v3 plugin format.