Use case

Design QA across platforms

See a page as an Android user and as an iPhone user, with the right viewport, the right touch behaviour, the right user agent and the right emoji — without owning either device.

The problem
A narrow browser window is not a phone. Sites branch on touch, on the user agent and on device pixel ratio, so a squeezed desktop layout looks like a mobile bug that is not there — and the emoji are wrong on both.
What we do about it
A preset is a whole device: viewport, scale, touch, user agent, and the emoji set that device would actually render. Change one parameter to change the device.

The call

Presets are frozen by name. `iphone` will not quietly become a newer model and change everybody's webshots.

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", "preset": "iphone", "color_scheme": "dark"}' \
  -o webshot.png

Other use cases

How the page reads on a device you do not own

Free to start, no card, and one endpoint to learn. The first webshot takes about a minute.