imgproxyvsrimgu
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| imgproxy | rimgu | |
|---|---|---|
| Score | 72/100 | 46/100 |
| Rank in category | #2 of 13 in Image Processing | #21 of 26 in Proxy |
| GitHub stars | 11 200 | — |
| Stars, last 30 days | +83 | — |
| Stable releases, 12 months | 27 | 0 |
| Latest release | v4.0.24 · 12 Nov 2026 | — |
| Setup | Easy | Easy |
| Official Docker image | Yes | No |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | — |
Which one should you pick?
imgproxy scores 72/100 against 46/100 for rimgu, so it is the safer default.
imgproxy ships more often: 27 stable releases in the past year, against 0 for rimgu.
imgproxy is growing faster right now (+83 stars in 30 days).
Key differences
- License: imgproxy is Apache-2.0, rimgu is AGPL-3.0.
- Only imgproxy ships an official Docker image.
- Platforms only imgproxy lists: Heroku.
- Platforms only rimgu lists: Node.js.
- Features only imgproxy lists: Auto-quality by file size, Cropping and trimming, Fallback image, Health check endpoint and 11 more.
- Features only rimgu lists: Album browsing, Built-in caching or HTTPS serving, Gallery with comments, HTTP/HTTPS forward proxy support and 7 more.
imgproxy details →rimgu details →
Swap a project
Keep imgproxy, compare it with
Keep rimgu, compare it with