# imgproxy vs sdnext

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

| | imgproxy | sdnext |
|---|---|---|
| Score | 72/100 ✓ | 71/100 |
| Rank in category | #2 of 13 in Image Processing | #3 of 11 in Image Generation |
| GitHub stars | 11 161 ✓ | 7 362 |
| Stars, last 30 days | +66 ✓ | +16 |
| 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 | Apache-2.0 |
| Main language | Go | Python |

## Which one should you pick?

imgproxy scores 72/100 against 71/100 for sdnext, so it is the safer default.

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

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

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

## Details

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

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