# imgproxy vs wger

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | imgproxy | wger |
|---|---|---|
| Score | 72/100 | 73/100 ✓ |
| Rank in category | #2 of 13 in Image Processing | #1 of 31 in Health & Fitness |
| GitHub stars | 11 162 ✓ | 7 203 |
| Stars, last 30 days | +67 | +240 ✓ |
| Stable releases, 12 months | 23 ✓ | 4 |
| Latest release | v4.0.20 · 26 Oct 2026 ✓ | 2.7 · 3 Sept 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | Python |

## Which one should you pick?

wger scores 73/100 against 72/100 for imgproxy, so it is the safer default.

imgproxy ships more often: 23 stable releases in the past year, against 4 for wger.

If you want the quickest setup, imgproxy is easier to run; wger needs more configuration.

wger is growing faster right now (+240 stars in 30 days).

## Details

- [imgproxy](https://selfhost.directory/project/imgproxy) (markdown: https://selfhost.directory/project/imgproxy.md)
- [wger](https://selfhost.directory/project/wger) (markdown: https://selfhost.directory/project/wger.md)

---
Source: https://selfhost.directory/compare/imgproxy-vs-wger