Hey everyone 👋

I built SlimVG after repeatedly running into the same problem while working on Android apps: SVGs that looked innocent in design files but turned out to be surprisingly expensive to render.

Some assets contained:
-Massive path definitions
-Excessive gradients and filters
-Embedded raster images hidden inside SVGs
-Hundreds of unnecessary nodes

The result? Larger app sizes, rendering issues, and occasionally performance problems that were difficult to trace back to the asset itself.

Most optimisation tools stop at a single pass. SlimVG takes a slightly different approach:

⚡ Automatically optimises SVGs until the gains become negligible
🔍 Detects heavy paths, gradients, masks, filters, and embedded raster images
💡 Recommends WebP when an asset simply isn't a good candidate for SVG anymore

One thing I learned while building this: some SVGs are really just PNGs wearing a fake moustache.

I'd love feedback from Android, Web, and iOS developers. If you've ever had a painful asset-related bug, I'd be curious to hear about it.

Thanks for checking it out 🙌

SlimVG

SVGs were never meant to carry this much emotional baggage.

SVGs were never meant to carry this much emotional baggage.