SVG Compressor
Apply aggressive compression using path merging, decimal precision reduction, and whitespace removal.
- Precision control
- Whitespace stripping
- Path merging
- Gzip size estimate
Compress vectors with the engine, not a find-and-replace
Runs SVGO in your browser — path rewriting, style inlining and reference-aware id cleanup, not just whitespace. Reports the gzipped saving your server actually sends, and renders both versions side by side so you can see that nothing broke.
Preset
Individual passes
None of these can change how the document renders.
Reference-aware, not text-aware
An id is only removed when nothing in the document points at it, and a gradient keeps the name its url(#…) expects. Cleaners built on find-and-replace cannot tell those cases apart, which is how artwork arrives with unpainted shapes.
Proof, not just a percentage
The comparison tab rasterizes both versions and counts the pixels that moved. Aggressive settings stop being a gamble once you can see exactly what they cost.
The number your server sends
Reported gzipped as well as on disk. Whitespace removal looks dramatic uncompressed and almost vanishes over the wire, so the honest figure is the smaller one.
What actually makes an SVG smaller
Editors like Illustrator, Inkscape and Figma write a great deal of bookkeeping into an export: generator comments, RDF metadata, private namespaces and layer names. Removing it is worth doing and is the first thing every optimizer does — but on a typical icon it is a minority of the file.
The weight is in the geometry. A path exported as M 12.000000 2.000000 C 6.4771500 2.0000000 … carries trailing zeroes, absolute coordinates and separators it does not need; rewritten as M12 2C6.477 2… it means exactly the same thing in a fraction of the characters. That rewrite requires parsing the path grammar, which is why a cleanup pass built on string replacement plateaus early.
Rounding, and where it stops being free
Every decimal place is a character in every coordinate. Three places is invisible on artwork of any normal size; one place starts to move points on detailed work, and zero snaps everything to whole units. The comparison tab exists so this is a decision you make by looking rather than by guessing — and rounding is applied to coordinates only, never to the text your document displays.
When to keep an id
Ids referenced inside the document are safe to shorten automatically. Ids referenced from outside it are not: a sprite sheet exists to be addressed by other files, and CSS or JavaScript may target a shape by name. Nothing in the file itself distinguishes those from dead ids, so the report lists every id it intends to drop before you download anything.
Recolor, animate or audit the optimized file
Use “Send to” above to carry this document straight across, or start from one of these:
Who uses SVG Compressor?
Common workflows and use cases for this tool
Performance-Critical Apps
Squeeze every byte from inline SVGs in high-traffic web applications.
How SVG Compressor works
- 1
Upload or paste your file
Drag & drop your file into the tool, paste from clipboard, or enter a URL. Supports SVG, PNG, JPEG, and WEBP up to 5MB free.
- 2
Configure settings
Adjust the available options to suit your needs. All settings are applied in real-time with an instant preview.
- 3
Download your result
Click Download to save your optimized, converted, or processed file. No watermarks on free exports.
Frequently Asked Questions
- Difference between SVG Optimizer and SVG Compressor?
- The Optimizer uses balanced settings. The Compressor applies aggressive precision reduction for maximum byte savings.