# imgproxy vs Subgen

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

| | imgproxy | Subgen |
|---|---|---|
| Score | 72/100 ✓ | 60/100 |
| Rank in category | #2 of 13 in Image Processing | #1 of 4 in Media |
| GitHub stars | 11 161 ✓ | 1 506 |
| Stars, last 30 days | +69 ✓ | +19 |
| Stable releases, 12 months | 23 ✓ | 0 |
| Latest release | v4.0.20 · 26 Oct 2026 | — |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |

## Which one should you pick?

imgproxy scores 72/100 against 60/100 for Subgen, so it is the safer default.

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

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

imgproxy is growing faster right now (+69 stars in 30 days).

## Details

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

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