Who is using it

[tbarbugli]

It would be great to see something like this in the readme or docs.

[DarthSim]

Hi Tommaso,

I'd be happy to add this info to readme, but I don't have one. I developed imgproxy for the needs of https://ebaysocial.ru/, and we successfully use it for a long time.

I keep this issue open, so anyone can share their experience with imgproxy in their projects.

We use it for www.rosebikes.com and our other country shops.
Up to 8 imgproxy pods on google kubernetes engine behind nginx reverse proxy behind google http loadbalancer (with enabled google cdn). Round about 100.000 product images, mostly in png (bike images with transparent background) mounted from a nfs volume.
We convert to png/jpg/webp. We use 2.0.0 now and will implement the background and maybe the sharpening options in the next week, as we need white background for zoom images (jpeg).
We love imgproxy for its focus on relevant functions and we do not have any problems.
Memory usage is very light, we had max. 100MB. CPU usage can be high, the pods are allowed to use up to 2 cores each.

[ineagu]

We are using it as a base of https://optimole.com, for now, is mainly used on our own sites and it seems to work well, thanks a lot for your work.

[mkushner]

We on https://farmguests.com have started migrating to imgproxy recently, and have a perceptible performance increase (even not finished migration to the last).

Having hundreds of heavy listing images (with an average single image size ~4-5mb) previously tried to resize images for different cases, but this worked expectedly slow; had to keep all the necessary sizes (small avatars, listing view, page view etc.), but this monster approach took so much time to handle.
The use of on-the-flow conversion with imgproxy solved both converting and keeping issues.
Nice job :)

[daneren2005]

We at PhotoLynx have been using ImgProxy for a couple of weeks. Currently we are using it only for our PLIC suite of apps, which is not publicly accessible and do not have public sign-up. We were previously using Pilbox which had memory leaks and just generally terrible performance. So far running ImgProxy on EC2 t3.small's and behind CloudFront is going great. For smaller images the time to create thumbnails is absolutely tiny and we can handle a huge number of concurrent requests. I do notice that when we start getting into 5-10 MB images there is some issues, but I don't think there really is a solution for that. Every other image server we have tried handles them even worse. Overall our move has been great and we recommend more people give ImgProxy a try!

[DarthSim]

Hi guys,

Thank you for your stories!

I'd be very appreciated if you could spend a bit of time filling our survey form. Your feedback would help me to bring more awesomeness to imgproxy.

[stewartmcgown]

We're using it at ecoeats to power image resizing for consumer apps on web and react native. Throw this thing behind a caching server and it is seriously the best solution for image resizing.

Thanks for a fantastic tool 💕

[scratchoo]

@stewartmcgown what caching server you are using? any recommendation?

[stewartmcgown]

Cloudflare!

[boardmain]

anyhone can share the k8n services configuration file?

[DarthSim]

@boardmain We have an official Helm chart: https://github.com/imgproxy/imgproxy-helm