> Did you try converting svgcleaner processed SVG to a TVG?

I would but I can't build the SDK (gets some zig error about failing to add a package) and the darwin-arm downloads don't include `svg2tvg`.

If I use the darwin-x86 download, `svg2tvgt` can't convert the file - `UnitRangeException: NaN is out of range when encoded with scale 1`.

I guess it doesn't really parse all SVGs.

If the goal is smaller files than it's fair and SVG with SVGCleaner wins.

Maybe we need a TVGCleaner too.

While you're not wrong, I'm gonna put my graphic designer hat back on for the first time since high school and point out that sometimes you _do_ want those invisible elements still there, especially if you're gonna want to do further editing on the file later on.

> especially if you're gonna want to do further editing on the file later on.

I think you'd generally only use the cleaning / optimising step when deploying / packaging the asset - you'd leave the original as, well, the original for further editing (and to take advantage of better optimisations if they come about.)

Very true, and I'd expect graphic designers and most dev's to know that.

I've worked with enough people who only had the optimized assets because "Well optimized is better, right?" [0] that I thought it was worth pointing out.

[0] I was working on some web stuff for them and they were curious if I could also do some graphics work, small local company