Our take
Activeregular commits and releases- Activity
- 82
- Community
- 64
- Issues
- 49
- Pull requests
- 49
+78 stars in the last 30 days
- Releases more often than 81% of the projects we track
- More contributors than 78% of the projects we track
- Slower to close issues than 98% of the projects we track
imgproxy is an actively maintained, Apache-2.0-licensed option for teams that want a dedicated image-processing server, though its contribution and issue-resolution patterns deserve attention.
Good fit if
- You need on-demand image resizing or conversion over HTTP and want processing handled outside your application.
- Your formats and processing needs fit the documented OSS feature set, and you can deploy a Go service or use Docker.
- You value recent releases and commits, and can account for most code contributions coming from one person.
Look elsewhere if
- You need Pro-only capabilities such as video or PDF previews, object detection, or advanced smart cropping.
- Your adoption decision depends on a broad distribution of code contributions or rapid resolution of all issues. Issues have a long median time to close, despite recent project activity.
- Your image transformations are better handled in the client, such as rounding corners or applying masks with CSS.
All health signals
| Last commit | 2026-11-12 (4 days ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 32 (latest v4.0.24, 2026-11-12) |
| Contributors | 100+ (top contributor: 81% of commits) |
| Issues closed, last 90 days | 46 (typically closed in 782 days) |
| Pull requests merged, last 90 days | 19 (typically merged in 1 day) |
| Project age | 9 years |
Checked on 2026-11-17 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
11,204Forks
794Change since Nov 16, 2026: +4 stars·0 forks
Overview
imgproxy is a standalone HTTP image server built on libvips, an image-processing library. It moves resizing, processing, and conversion out of an application: clients request an image using a URL containing the source and processing options, and imgproxy returns the result.
It is aimed at teams that need to serve images in different sizes or formats without generating and storing every variant in advance. The server can sit behind a CDN, load balancer, or reverse proxy, and its URL-signing and source restrictions help control access to image processing.
Key Features
- Resize, crop, and rotate images from HTTP requests.
- Apply watermarks and filters, and use simple smart cropping.
- Accept formats including JPEG, PNG, GIF, WebP, AVIF, and JPEG XL.
- Optimize images by stripping color profiles and metadata, and quantizing PNGs.
- Sign processing URLs and restrict image sources, file sizes, and processing options.
- Check image types and dimensions to reduce resource risks from unwanted files and image bombs.
- Run as a standalone server, with Docker as the README's recommended quick start.
Use Cases
- A web application team can serve responsive image sizes without adding image-processing code to its application.
- A content platform can generate image variants on demand as page layouts and display sizes change.
- A media service can convert and optimize user-uploaded images before serving them to clients.
- An infrastructure team can put image processing behind a CDN or reverse proxy and use signed URLs to control requests.
What you need
Detected in the repository
- Go 1.27.0 or newer (from go.mod)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Run imgproxy with Docker:
docker run -p 8080:8080 -it ghcr.io/imgproxy/imgproxy:latest
Then follow the Getting Started guide to make a processing request. See the README and documentation for configuration and usage details.
Alternatives
- reubah: Reubah offers a web interface for image and document tasks, while imgproxy serves processed images on demand through URLs.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| imgproxy | Go | Apache-2.0 | 11.2k | Active |
| reubah | HTML | MIT | 701 | Quiet |
Considerations
- The project is active, with regular commits and releases, but most code comes from one contributor. This concentration is a continuity risk even with a larger contributor community.
- Issue closure is slow by the measured median, while pull requests are merged quickly. Teams relying on issue support should factor that contrast into adoption planning.
- The OSS feature set is not the full product: advanced compression controls, video and document previews, object detection, and other features are listed as imgproxy Pro capabilities.
- The README recommends running behind a CDN, load balancer, or reverse proxy rather than implementing HTTPS in imgproxy itself. Plan that deployment layer separately.
- The project uses the Apache-2.0 license. Review its terms for your distribution and deployment model.
Found this useful?
Share it with someone who would like imgproxy.