# nps vs url-to-png

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

| | nps | url-to-png |
|---|---|---|
| Score | 74/100 ✓ | 49/100 |
| Rank in category | #2 of 31 in Networking | #13 of 16 in Web Scraping |
| GitHub stars | 34 263 ✓ | 256 |
| Stars, last 30 days | +28 ✓ | +0 |
| Stable releases, 12 months | 0 | 2 ✓ |
| Latest release | — | v2.1.4 · 18 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | No | Yes ✓ |
| License | GPL-3.0 | MIT |
| Main language | Go | Typescript |

## Which one should you pick?

nps scores 74/100 against 49/100 for url-to-png, so it is the safer default.

url-to-png ships more often: 2 stable releases in the past year, against 0 for nps.

If you want the quickest setup, url-to-png is easier to run; nps needs more configuration.

nps is growing faster right now (+28 stars in 30 days).

## Details

- [nps](https://selfhost.directory/project/nps) (markdown: https://selfhost.directory/project/nps.md)
- [url-to-png](https://selfhost.directory/project/url-to-png) (markdown: https://selfhost.directory/project/url-to-png.md)

---
Source: https://selfhost.directory/compare/nps-vs-url-to-png