OptiPNG VS Oxipng

This project uses HTMLMinifier, optipng, and zopfli to create a custom production Elm build pipeline. You can see how I make use of these tools in this build script. Here are the results in case you're interested. I used the same ideas from this project to build and deploy dwayne/elm-conduit, which you can learn more about in my article Yet Another Tour of an Open-Source Elm SPA. - Source: dev.to / 4 days ago

Did you compare to PNG crush and optipng? Those are what I used to use because they're easily installable Linux/brew packages. Source: about 1 year ago

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. Source: over 2 years ago

I have had good experiences with https://github.com/shssoichiro/oxipng . Although, I suspect this wouldn't give you nearly enough space savings as jpg. Source: 12 months ago

If you do want the file as a PNG (for transparency and a common format that's well supported), but don't want it so huge, consider something like oxipng. https://github.com/shssoichiro/oxipng. Source: over 1 year ago

Oxipng, pngquant and svgcleaner — optimizing images. Source: over 1 year ago

I wonder how `pngcrush` compares to `oxipng` (https://github.com/shssoichiro/oxipng). Personally, I use `oxipng` if I want lossless compression. However, most of the time, I use `pngquant` instead, since it gives significant size reduction even at `99%` (I can't even distinguish between the original and reduced image).

    pngquant --quality=99 --ext=.png --force file.png

. - Source: Hacker News / over 1 year ago

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. Source: almost 2 years ago