image VS oxipng

With the help of the image crate, loading an image from disk is fairly straightforward.

FTR there is a WebP decoder implementation in safe Rust in the image crate: https://github.com/image-rs/image

It used to be quite incomplete for a long time, but work last year has implemented many webp features. Chromium now has a policy of allowing the use of Rust dependencies, so maybe Chromium could start adopting it?

Hello! So I have a local app that I am currently running on desktop (windows). I'm using egui for the UI, and the program basically opens a folder, gets all the images in the folder, and then uses the image-rs library to resize and create a grid of images / some other operations.

png is the de-facto standard Rust crate for reading and writing PNG images, used e.g. by the image crate.

There's also a CLI to convert between formats. It uses the crate image.

exr is a is a 100% Rust and 100% safe code library for reading and writing OpenEXR images. It is used by the popular image crate to read and write OpenEXR.

We're currently looking for contributors to add support for zune-jpeg to the image crate. The image maintainers are open to it, but don't have the capacity to do it themselves. You can find more details here.

It uses https://github.com/1Password/arboard and https://github.com/image-rs/image under the hood. I haven't tested deeply but I assume it should handle many formats out of the box.

You can use the image crate.

As for image processing, I'd start on crates.io and search for "image processing" and skim through to find the most downloaded crates -- image seems to be the most popular, with over 7 million downloads, so I'd check if that has what you want, and if not photon-rs seemed relatively mature with perhaps more features (albeit far less commonly used)

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.

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

oxipng, pngquant and svgcleaner — optimizing images

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

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.

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.