rankato

Shrink SVGs by up to 80% — losslessly

Drop up to 50 SVG files and the compressor strips editor cruft, rounds coordinates, and collapses transforms. Zero visual change, dramatic size drop.

Preset:Lossless — no visible change

Most SVGs exported from design tools contain 50–80% cruft: editor metadata, unused clip paths, unnecessary group wrappers, verbose XML declarations, and coordinates with 8 decimal places of precision. The Rankato SVG Compressor runs your files through SVGO — the same optimizer built into Figma, Sketch, GitHub's SVG upload pipeline, and every serious SVG asset workflow — with a preset that removes only lossless bloat. Nothing about the rendered image changes; only the file size does. Batch up to 50 files, see before/after previews side by side, and download a ZIP of the optimized set.

What SVGO removes (and why it's safe)

SVGO's default plugin set targets the specific classes of bloat that design tools inject: XML processing instructions and doctype declarations that browsers ignore anyway, XML comments, editor-only namespaces (xmlns:sketch, xmlns:adobe), unused IDs and definitions, empty containers, redundant strokes/fills that match the SVG default, transform matrices that collapse to identity, and coordinate precision beyond what your viewport can display. Every one of these transformations is provably lossless — the rendered pixels are byte-identical before and after — which is why SVGO is the default choice for build pipelines that ship SVGs to production.

Typical savings by source

Real-world savings depend on the exporter. Figma SVGs typically drop 50–65% because Figma exports lots of group wrappers and preserves per-element transforms. Illustrator SVGs drop 60–80% due to the massive Adobe metadata block that lives at the top of every export. Sketch SVGs drop 40–55%. Hand-written SVGs (or ones already passed through SVGO) may only drop 5–15% — mostly whitespace and coordinate rounding. Icon-font SVGs from IcoMoon are usually already tight and see 2–8% gains. Across a mixed portfolio, expect an average of ~55%.

Safe defaults vs. aggressive mode

The default preset — Safe — only runs plugins whose transformations are provably lossless. If you want more, toggle Aggressive, which additionally: converts <path> shape primitives into shorthand path commands, merges adjacent paths with identical styles, and rounds path precision to 2 decimals (default is 3). Aggressive mode can sometimes introduce sub-pixel visual differences on very fine detail — the tool shows a side-by-side visual diff and highlights any pixel that changed, so you can review before downloading.

Batch processing and download

Drop up to 50 SVGs at once. Each file is processed in a Web Worker so the UI stays smooth even on a low-end laptop. The file list shows per-file thumbnail, original size, compressed size, savings percentage, and a per-file download link. Hit Download all (.zip) for a ZIP archive with every optimized SVG — filenames preserve the original names. If any file would grow in size after optimization (rare, but happens with already-minified SVGs where minification actually adds a re-encoded XML declaration), the tool ships the original and marks the row.

When to run this vs. a build-time optimizer

If you're a solo developer or a designer handing off assets, this tool is the fastest path — drop, download, paste. If you're on a team with a build system, install svgo-cli or imagemin-svgo and put optimization in your CI pipeline so nobody ships an unoptimized SVG by accident. This tool uses the same optimizer with the same defaults, so switching between the two is seamless.

Tool FAQs

Everything you need to know about using SVG Compressor.

Will compression change how my SVG looks?+

Not with the default Safe preset. Every transformation is provably lossless — the rendered pixels are identical. Aggressive mode may introduce sub-pixel differences from precision rounding; we show a visual diff so you can decide whether to keep those savings.

Can I compress an SVG that's already minified?+

Yes, but expect small gains (0–15%). Once SVGO has run once, most of the low-hanging fruit is gone. Running twice occasionally squeezes out an additional 1–2% because plugins can catch cases that only become optimizable after other plugins run first.

Do you preserve accessibility attributes like aria-label and title?+

Yes. title, desc, aria-label, aria-labelledby, role, and any data-* attributes are preserved by default. Editor-only metadata (data-name, data-figma-*) is removed — that's junk your users never see.

Is there a file size limit?+

Per file: 5 MB. Batch: 50 files or 100 MB total. Larger SVGs almost always indicate an <image> tag with an embedded base64 PNG or JPEG — SVGO won't help there. Extract the raster with the SVG editor and optimize it as a raster image instead.

Does the compressor work offline?+

Yes. SVGO is bundled into the page as WebAssembly, so once the tab loads you can disconnect and keep compressing. No network round-trip means the tool works on plane Wi-Fi, in air-gapped environments, and inside corporate networks that block outbound requests.