If it’s using Chrome headless, it’s superior to wkhtmltopdf. The latter has lots of little gotchas and things that may render fine in a browser but not in wkhtmltopdf. Chrome headless doesn’t suffer from those issues, obviously.
but the site itself says it "runs headless".
Running headless does not imply that it's running Chrome headless, just that it runs without a GUI.
One is a hosted service and one isn't.
I know but if I need to use an API to an external server I can also launch a command locally. 7$ is not much but I don't see any real benefit unless you want to capture a subsection of a website.
The clip to a specific DOM element seems unique to this.
Also with screen.rip, you can run a custom JS before capturing the screenshot and also can wait for certain elements to appear (which is quite important today with client-side rendered sites)
Disclaimer: I created screen.rip
> Disclaimer: I created screen.rip
No need for a disclaimer, after all, this is your Show HN ;)