imaginary VS imagor

WebP also frequently produces lower quality or blurry images: - https://wordpress.org/support/topic/images-going-blurry/ - https://github.com/h2non/imaginary/issues/240

One thing I didn't mention that AIO includes is a container called imaginary which is written in Go and processes images. I think this is mainly used here for generating image previews in NC.

Thanks. This is new to me. How is it different from https://github.com/h2non/imaginary?

There is also battle-tested imaginary tool [1], offering similar functionality and much more, also using libvips

[1] https://github.com/h2non/imaginary

Imaginary is a fast HTTP microservice written in Go allowing high-level image processing. Behind the scene, imaginary uses bimg and libvips libraries to perform the image manipulations.

I have used https://github.com/cshum/imagor infront of S3 before and liked it, there is many (some commercial) offerings for this

This is basically a self-hosted Cloudinary transformation tool. Was hoping to find something more polished and user-friendly, but still hunting.

https://github.com/cshum/imagor maybe what's you wish but without admin panel.

imagor requires only a tiny subset of the features from gocloud.dev/blob. For instance implementing a imagor.Storage takes ~150 lines of code so it is not all that complex after all.

We now support lots more image types if you're happy to run Imagor HEIC, SVG, HDR, TIFF... Anything that is supported by Imagor