oxipng VS img-hash

Depending on your workflow it might make sense to export PNGs directly from Affinity and then reduce their size with a utility like Oxipng, which uses all your cores to find the best algorithm for each particular image.

Assuming your frames are PNG files, you could use a lossless optimizer like optipng to try if their size can be reduced. I prefer oxipng, which is faster and multithreaded, and seems to have more active development.

Not sure what extensions of images you use, but if they’re PNG you could use oxipng: https://github.com/shssoichiro/oxipng

For PNGs specifically oxipng is awesome. It even has Zopfli compression, which is compatible regular compression, but is ~30% smaller (but requires lots of CPU time to compute).

They do. ripgrep and fd extensively use parallelism, which is specifically enabled by Rust's safety guarantees. oxipng is also in the same boat.

PNG: oxipng SVG: svgcleaner

Or go Commando: https://github.com/shssoichiro/oxipng

I absolutely loved all the crates available that made my life very simple in many cases. I used (among others) the slint ui framework, kamadak-exif, img_hash, fast_image_resize and rawloader.

I'm using default img_hash algorithm - Gradient. It is also possible to use with this library different algorithms - https://github.com/abonander/img_hash/blob/master/src/alg/mod.rs#L20-L81