webp VS imgproxy

There is a decoder in golang.org/x/images/webp already [0] — the x libs are part of the Go Project but outside the main Go tree — and are fairly well-known to many Go developers, but clearly not all. Stuff in x sometimes makes its way into the standard library, although not always.

And there is a third-party package [1] for webp also, in native Go, which includes both a decoder and an encoder. Plus there are other third-party packages, that bind to external code (C libs, at a guess).

— If your complaint is speficially that webp support should be a part of the standard library, then perhaps keep an eye on the stuff in x, that's often where stuff happens before making it into the stdlib.

And/or file an issue.

And/or you are welcome to contribute code ;)

[0] https://pkg.go.dev/golang.org/x

[1] https://github.com/chai2010/webp

In my project[1], I convert all user-uploaded images to high-quality webp and store them like that. I discard the original files after the conversion. I use imgproxy[2] to further resize and convert them on the fly for actual display.

I don't do videos yet, but I'm kinda terrified of the idea of putting user-uploaded files through ffmpeg if/when I'll support them.

[1] https://github.com/grishka/Smithereen

[2] https://github.com/imgproxy/imgproxy

We use imgproxy which does 2->4 and all you need to do is change the URL on your site.

imgproxy interactive demo

You should also be using a variety of formats. Unless you need support for old browsers and transparency in the same image, don't use PNG. Stick with jpg, webp and avif. You can setup something like imgproxy to automatically resize and change format of images, or even fit into the space requirements you set.

If you look for something universal, you can try API for image optimization (e.g. imgproxy). However, the mechanism is different from build-time optimization.

Hey everyone, seeking some feedback about how to improve our project, imgproxy, an open source image processing tool.It’s designed to reduce costs and remove pricey requirements for all saved images to conform to specific formats. You can read the full list here if you’re curious: https://github.com/imgproxy/imgproxy In addition to crucial image processing stuff (like resizing, cropping, rotating), it can also sign urls, add watermarks, and a ton of other things.A ton of developers use it, and that’s great. We’re trying to improve it further, so wanted to put out the feelers and see if there is anyone using it (or a similar tool) who could suggest some additional features (or tell about the essential features of your current image processing tool).