SVG toolkit

SVG optimizer.

Paste SVG code or upload a file, strip editor metadata, minify the markup, and export to high-resolution PNG or WebP. Everything runs locally in your browser — no files are ever uploaded to a server.

SVG optimizer

Export to Raster

Scale

Output: × px · PNG

What gets cleaned

  • XML declarations and HTML comments
  • Inkscape & Illustrator editor metadata
  • Redundant whitespace and empty attributes
  • Unused namespace declarations

How the optimizer works

Clean markup

Strips XML declarations, Inkscape/Illustrator metadata, unused namespaces, and redundant whitespace in one click.

Export at any size

Export to PNG or WebP at 1x–4x scale with custom dimensions. Uses the native HTML5 Canvas API for crisp, accurate rasterization.

100% private

No server uploads, no cloud processing, no third-party access. Your SVG files never leave your device.

How to use it

Getting a useful result.

  1. Paste the SVG code, or drop in the .svg file your designer sent. Everything runs in your browser.
  2. Compare the preview against the original before you copy anything out. Optimisation should be invisible; if the shape changed, lower the precision setting rather than accepting it.
  3. Copy the cleaned markup and paste it straight into your page, or save it back over the file.
  4. For a logo, paste the SVG inline in the HTML rather than linking it as an image — that removes a network request and lets the logo take its colour from CSS.

Files exported from Illustrator, Figma or Canva carry a surprising amount of dead weight: editor metadata, hidden layers, comments, empty groups, and coordinates written to ten decimal places. None of it draws anything. Stripping it commonly halves the file with no visible change at all.

There is a real safety reason too. An SVG is code, not a picture — it can legally contain scripts and external references. If you accept logos from clients or download icons from the internet, cleaning them before they go anywhere near your site removes that class of problem.

Keep the viewBox. It is what lets the graphic scale to any size, and removing it is the one common optimisation that visibly breaks things.

Common questions

Why is my logo file so large when it is just a few shapes?

Almost always because it was exported with editor metadata and full-precision coordinates, or because a photo has been embedded inside it. The first two this tool removes. If the file is still large afterwards, open it and look for a base64 image block — that is a raster photo wearing an SVG wrapper, and it needs the image optimizer instead.

Will this change how my graphic looks?

It should not. The transformations remove data that does not draw anything. The one setting that can alter appearance is coordinate precision — round too aggressively and curves visibly flatten — which is why the preview sits next to the output.

Is SVG better than PNG for logos?

Yes, in almost every case. An SVG is drawn from instructions, so it stays sharp at any size and on any screen, and it is usually far smaller than a PNG large enough to look crisp on a high-resolution display. Use PNG only where you need a photographic texture inside the mark.

Free Learning Guide

Speed up your vector graphics: SVG minification guide

Learn why SVGs generated by Illustrator or Figma contain double the file weight they need, and how minifying raw code boosts speed.

Read Simple Guide →

A clean vector starts with how the mark was drawn, which is where a logo either survives every size or does not — graphic design and brand identity.