# imgproxy vs llama.cpp

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

| | imgproxy | llama.cpp |
|---|---|---|
| Score | 72/100 | 93/100 ✓ |
| Rank in category | #2 of 13 in Image Processing | #2 of 25 in LLM Inference |
| GitHub stars | 11 159 | 132 646 ✓ |
| Stars, last 30 days | +67 | +3 289 ✓ |
| Stable releases, 12 months | 23 | 1458 ✓ |
| Latest release | v4.0.20 · 26 Oct 2026 | b11969 · 28 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | C++ |

## Which one should you pick?

llama.cpp scores 93/100 against 72/100 for imgproxy, so it is the safer default.

llama.cpp ships more often: 1458 stable releases in the past year, against 23 for imgproxy.

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

llama.cpp is growing faster right now (+3 289 stars in 30 days).

## Details

- [imgproxy](https://selfhost.directory/project/imgproxy) (markdown: https://selfhost.directory/project/imgproxy.md)
- [llama.cpp](https://selfhost.directory/project/llamacpp) (markdown: https://selfhost.directory/project/llamacpp.md)

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