imgproxy
A fast and secure standalone server for resizing, processing, and converting images.
Platform availability
Available on 2 of 6 install platforms
Also on Docker Hub and GitHub
Health score
81/100 Excellent
- Maintained
- 100last commit 7 days ago
- Popular
- 8111,100 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
How is this calculated?
A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.
Availability: platform listings confirmed today, links checked 7 days ago
- GitHub stars
- 11,100
- Open issues
- 67
- Last commit
- 2026-09-28
- Latest release
- v4.0.16
- License
- Apache-2.0
- Activity
- steady
Checked 7 days ago - source: GitHub (imgproxy/imgproxy)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 7 days ago - source: Docker Hub image tags and published docs
First-install notes
- Choose the port imgproxy listens on Choose the network port (the numbered line other devices connect to) that imgproxy uses to accept requests, then allow it in your router or firewall. Other apps can't ask for resized images if that port is wrong or blocked. source
- Set imgproxy's startup settings Put the settings imgproxy needs, such as where to listen and where your images come from, into environment variables (name-and-value pairs the app reads at startup) before you start it. If these are missing or wrong, it may use unexpected defaults or fail to serve your images. source
- Cap the largest source image Set a maximum size for source images, for example 50 MB, when imgproxy downloads them. Without a limit, one very large image can use a lot of memory or make processing slow. source
Fetched 7 days ago - each note links to its source
Variants
Alternatives (2)
- Cloudinary - Image and video API platform for developers, covering uploads, storage, AI-powered transformations, optimization, and delivery for web and…
- Fottly - Fottly is a self-hosted, open-source (AGPL-3.0) image transformation API with built-in AI background removal, a cost/control-focused altern…
Checked 4 days ago - source: AlternativeTo
Common questions
Which port should self-hosters expose for imgproxy?
Choose the network port that imgproxy listens on in its configuration, then allow that port in the router or firewall. If the port is wrong or blocked, other apps cannot request processed images.
How should imgproxy startup settings be supplied?
Set the startup settings, such as where to listen and where images come from, as environment variables before starting imgproxy. Missing or wrong values can make it use unexpected defaults or fail to serve images.
Should I limit the size of source images imgproxy downloads?
Yes, set a maximum source image size, for example 50 MB, when imgproxy downloads images. Without a limit, one very large image can use a lot of memory or make processing slow.
How does an imgproxy request work?
Send imgproxy a specially crafted URL containing the source image URL and the desired processing options. It fetches the image, processes it, and serves the resulting image.
Answers sourced from docs.imgproxy.net, github.com, github.com, github.com
Community
- (Almost) free image processing with imgproxy and AWS Lambda - Reddit (reddit)
- Smart, self-hosted image resizing with imgproxy : r/webdev - Reddit (reddit)
- Imgproxy: An open source image proxying server case study - Reddit (reddit)
- Free tier real-time image processing with imgproxy (OSS) and ... - Reddit (reddit)
- Any selfhost image proxy optimization? : r/selfhosted - Reddit (reddit)
Collected 2 days ago - public community threads