imageproxy VS imgproxy

I wrote https://github.com/willnorris/imageproxy for exactly this purpose about 10 years ago. It's just been a personal project, but handful of folks have used it over the years. As mentioned below, imgproxy.net is the other pretty popular option, also written in go. Notably, it's backed by Evil Martians (makers of postcss and a bunch of other things), so is a bit more robust, and has gotten a lot more real-world usage and large scales.

If you can't specify the resolution, then there exists tools like imageproxy which is a server which does resizing for you, and sits as a middleman between your client and the API you are requesting images from. I honestly wouldn't bother with this just because lighthouse says that image sizes are a problem. The amount of effort to host an imageproxy like service outweighs the benefits of simplicity in my opinion. So I would only use imageproxy if I'm expecting a lot of visitors using very slow connections or the images you are loading are large (>1 megabyte).

This gem is just a client for using ImageProxy

I've used Imgix on a lot of projects and can't really complain, it's a bit pricey though. If your needs are simple enough you might be able to host your own transform proxy https://github.com/willnorris/imageproxy

You can try ImageProxy. You will need to host it yourself but the original images can come from third parties.

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).