imgproxyvstrigger
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| imgproxy | trigger | |
|---|---|---|
| Score | 72/100 | 76/100 |
| Rank in category | #2 of 13 in Image Processing | #7 of 32 in Workflow Automation |
| GitHub stars | 11 161 | 16 648 |
| Stars, last 30 days | +66 | +249 |
| Stable releases, 12 months | 23 | 49 |
| Latest release | v4.0.20 · 26 Oct 2026 | v4.8.1 · 23 Oct 2026 |
| Setup | Easy | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Typescript |
Which one should you pick?
trigger scores 76/100 against 72/100 for imgproxy, so it is the safer default.
trigger ships more often: 49 stable releases in the past year, against 23 for imgproxy.
If you want the quickest setup, imgproxy is easier to run; trigger needs more configuration.
trigger is growing faster right now (+249 stars in 30 days).
imgproxy details →trigger details →
Swap a project
Keep imgproxy, compare it with
Keep trigger, compare it with