# imgproxy vs SeaweedFS

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

| | imgproxy | SeaweedFS |
|---|---|---|
| Score | 72/100 | 81/100 ✓ |
| Rank in category | #2 of 13 in Image Processing | #1 of 11 in Cloud Storage |
| GitHub stars | 11 161 | 35 795 ✓ |
| Stars, last 30 days | +66 | +834 ✓ |
| Stable releases, 12 months | 23 | 28 ✓ |
| Latest release | v4.0.20 · 26 Oct 2026 ✓ | 4.51 · 25 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Go |

## Which one should you pick?

SeaweedFS scores 81/100 against 72/100 for imgproxy, so it is the safer default.

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

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

SeaweedFS is growing faster right now (+834 stars in 30 days).

## Details

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

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