Comparison
Webshotter vs Browserless
Browserless sells you a browser to drive; we sell you a picture. They are different products, and the choice is really about how much of the browser you need.
Where we win
One call, no session
POST a URL, get an image in the response body. No job to poll, no bucket to fetch from, no Puppeteer to write.
The fonts problem solved
A hosted browser is still a Linux image with one emoji font in it. Fixing that is a Dockerfile per set and then maintaining eight of them.
Priced per picture
You pay for renders, not for browser-seconds you have to reason about.
Where Browserless wins
Everything else a browser does
Filling forms, logging in, scraping, multi-step flows, PDFs from authenticated sessions. If you need to drive the browser, drive the browser.
Control
Their product is the whole devtools protocol. Ours is one endpoint.
Try the difference in one call
The emoji set is a parameter. Change one word and the browser that takes the picture changes with it.
bash
curl -X POST https://webshotter.com/api/v1/webshots \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com", "emoji_set": "apple"}' \
-o webshot.pngOther comparisons
See it against Browserless yourself
A hundred webshots a month on the free plan, no card. Point both at the same page and look at the emoji.