imgproxyvsrimgo
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| imgproxy | rimgo | |
|---|---|---|
| Score | 72/100 | 57/100 |
| Rank in category | #2 of 13 in Image Processing | #2 of 6 in Media |
| 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 | Yes |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | — |
Which one should you pick?
imgproxy scores 72/100 against 57/100 for rimgo, so it is the safer default.
imgproxy ships more often: 27 stable releases in the past year, against 0 for rimgo.
imgproxy is growing faster right now (+83 stars in 30 days).
Key differences
- License: imgproxy is Apache-2.0, rimgo is AGPL-3.0.
- Platforms only imgproxy lists: Docker, Heroku.
- Platforms only rimgo lists: Linux, Nix, Podman.
- Features only imgproxy lists: Auto-quality by file size, Cropping and trimming, Fallback image, Health check endpoint and 11 more.
- Features only rimgo lists: Bandwidth-efficient image formats, HTTP/SOCKS proxy support, Instance privacy disclosures, No ads or tracking and 5 more.
imgproxy details →rimgo details →
Swap a project
Keep imgproxy, compare it with
Keep rimgo, compare it with