Compress SVGs.
Smaller SVG files in your browser — nothing is uploaded.
Drop SVG files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Minify SVG files entirely in your browser: strip comments, metadata and editor junk, clean up IDs and round coordinates to fewer decimals. Your artwork is never uploaded — it never leaves your machine. Need pixels instead? The output format switch renders your SVG to PNG at any size, or straight to a multi-size ICO favicon.
Before / after
Original
85 KB
Compressed
54.3 KB
Saved
−36%
Real result, not a mock-up: what you're dragging is the two actual SVG files — the original and the output of the Compress SVG tool, SVGO with default settings — rendered live by your browser. Same pixels, 36% fewer bytes: comments, editor metadata and excess coordinate precision are gone, and the file dropped from 85 KB to 54.3 KB. Drag all you like — nothing changes, which is the point.
Artwork via Magnific .
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
What gets removed
SVGs exported from Figma, Illustrator or Inkscape carry editor metadata, comments, hidden layers, default attributes and coordinates with absurd precision. The tool strips what doesn’t render and rewrites what does — same picture, a fraction of the file. And because SVG is text, the wins compound when your website serves it compressed. If the same artwork also needs a favicon, SVG to ICO builds one straight from the vector.
Precision, explained
Coordinate precision is the main size dial: each extra decimal adds bytes to every point of every path. Three decimals is beyond visual perception for screen graphics; simple icons survive two. Lower it until something visibly shifts, then step back one.
Safe vs aggressive optimizations
The default toggles — comments, metadata, ID cleanup, dimension removal with the viewBox kept — are safe for virtually every file. The aggressive pass merges paths and collapses groups: usually fine for static icons, but test SVGs that are styled from CSS or animated through their IDs and classes, because collapsing can rename what your code targets.
Under the hood
Minification runs on SVGO — the standard SVG optimizer, the same tool front-end build pipelines run before shipping icons — bundled into this page so your artwork never leaves your machine. Every toggle in the panel maps to a documented SVGO plugin, so the output here matches what a professional toolchain would produce, byte for byte.
Frequently asked questions
Is it safe to optimize proprietary artwork here?
Yes. The pixels are decoded and re-encoded right in your browser — images are never uploaded, and the server does nothing but deliver this page. Close the tab and no trace of your photos remains. Want proof? Run one file through, switch your connection off, and run another — it still works.
Is a minified SVG still editable?
Yes — the output is still plain, valid SVG. Comments, metadata and redundant precision are gone, but you can reopen it in any editor.
Will minification change how my SVG looks?
With the default settings, no — they are visually safe. Aggressive mode and low precision can shift hairline details, so check the preview for intricate artwork.
How much smaller do SVGs get?
Exports from design tools often shrink 30–70%, since editors embed metadata and overly precise coordinates that the tool safely removes.