imgproxy VS Glide

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

Now signup for Vultr and make a $5 instance and put imgproxy on it. Setup a subdomain for images in Cloudflare and point it to the imgproxy IP.

We use https://glide.thephpleague.com/. It's dead easy to crop and resize with it too.

Best library for image manipulation is https://glide.thephpleague.com/

A solution for self hosted in PHP is Glide: https://glide.thephpleague.com

You should check out Glide. It provides an easy to use RESTful API for dynamically transforming images on the fly, handles caching them in Flysystem automatically, is easy to integrate in most modern frameworks, and allows you to secure the endpoint via signed URLs, presets and maximum sizes.

This is some pretty powerful stuff. Here's a more information-dense and up-to-date rundown of srcset and sizes: https://bitsofco.de/the-srcset-and-sizes-attributes/

Notably, it shows how it's possible to use different images based on a portrait or landscape layout of the viewport, which OP doesn't cover. That's not always useful but it's good to know it's there when you might want to use it.

I was recently (well, several months ago) tasked with improving the Google PageSpeed scores on mobile for a site which has a lot of image-heavy pages. The end solution involved adapting all images to use a image with a WebP alternative for browsers that can show it (Google's tools like it when you use their near-proprietary image format; go figure), plus using srcset and sizes (which can be used on tags inside of tags as well as tags) plus a script which resizes and caches resized versions of large images based on URL parameters (basically an ersatz Glide [0]; I wish I had known it existed when I started). The end result severely reduced page weight for mobile visitors and was successful in raising our PageSpeed scores and appeasing my client.

[0]: https://glide.thephpleague.com