imgproxy is a fast and secure standalone server for resizing, processing, and converting images. The guiding principles behind imgproxy are speed, security, and simplicity. It is well equipped to handle huge volumes of image-processing requests with ease. imgproxy is a drop-in replacement for all the image-processing code in your web application. With imgproxy, you don’t need to repeatedly re-prepare images to fit your design every time it changes, as imgproxy does this on demand.
This is the 2nd launch from imgproxy. View more
imgproxy v4
Launched this week
imgproxy is a fast and secure standalone server for resizing, processing, and converting images. The guiding principles behind imgproxy are speed, security, and simplicity. It is well equipped to handle huge volumes of image-processing requests with ease. imgproxy is a drop-in replacement for all the image-processing code in your web application. With imgproxy, you don’t need to repeatedly re-prepare images to fit your design every time it changes, as imgproxy does this on demand.
Free Options
Launch Team
imgproxy
Hey Product Hunt! 👋
Sergei here, the author and CTO of imgproxy.
Almost every product I have been involved in has dealt with images in some manner. So I know the pain of making the right choice for image processing. Building your own image processing solution is a huge time sink, and it can easily be done wrong. On the other hand, using a third-party service quickly becomes a money pit as your traffic grows.
That's why we created imgproxy – a self-hosted image processing server that just works. It's packed in a single Docker image, deployable anywhere in minutes, with no third-party dependencies. Combine it with a caching layer of your choice, and you have an enterprise-grade image processing solution that can handle any load.
Since its first release back in 2017, imgproxy has been adopted by thousands of developers and companies worldwide. You probably see images processed by imgproxy every day without even realizing it: Medium, Dribbble, Substack, and many more use imgproxy to serve their images.
imgproxy comes in two flavors: a forever-free open-source version and a paid Pro version with additional features and support. The Pro version is available as a subscription and includes features such as video preview generation, object detection, SVG minification, and more. Both versions are self-hosted, so you have full control over your data and infrastructure.
Today, we are happy to announce the new major release of imgproxy, version 4.0. This release includes a lot of new features and improvements, such as:
Better performance thanks to parallel source image downloading and processing
Internal cache for processed images
Support for digital cameras' RAW formats
Image classification
Improved SVG minification
... and much more!
Check out the full release notes for all the details: https://github.com/imgproxy/imgp....
Drop us a line in the comments if you have any questions or feedback. We are always happy to hear from the community!
With the new internal cache for processed images in v4, how does cache invalidation work when the source image changes? Does imgproxy check source ETags or Last-Modified headers, or is expiry purely time-based?
imgproxy
@sunnyallan imgproxy doesn't handle this. Changing content without changing the filename is generally a bad idea. Even if you manage to make imgproxy and the CDNs handle this, there's also cache in the user's browser that you can't invalidate.
imgproxy
Hi PH!
Marina here, co-founder & CEO of imgproxy.
One thing we’ve noticed over the years is that more and more teams want to own their infrastructure again.
Not because self-hosting is trendy, but because image and video processing becomes surprisingly expensive and limiting at scale when it’s fully outsourced to SaaS platforms.
A lot of companies start with third-party image APIs because they’re convenient early on. But later they run into:
unpredictable costs
vendor lock-in
limited control over caching and performance
imgproxy exists because we wanted a different tradeoff: a fast self-hosted system developers can run anywhere and fully control themselves. And honestly, seeing companies process billions of images through imgproxy every day is still surreal to us.
Huge thanks to everyone who tested v4 early and helped shape this release.
imgproxy
Hi PH! Viktor here, developer of imgproxy!
One thing we cared about from the beginning was building imgproxy as a sustainable long-term open-source project.
Why? Because the tools developers rely on most should be the ones they can actually own.
Not "own" as in pay for a license. Own as in run it yourself, on your own infrastructure, and trust it to do exactly what it claims. No hidden calls home, no lock-in, no surprises in your bill at the end of the month.
v4 is probably our most significant release in that spirit. We didn't just add features — we practically reworked the whole codebase. Cleaner architecture, better code quality, better performance. The kind of changes that don't make great screenshots but make a real difference when you're processing millions of images a day.
If imgproxy solves a problem for you, come say hi on GitHub. And if it doesn't yet — tell us why. That's how the best features get built