Use cases
What people point it at
The same endpoint, from four different directions. Each of these is a problem somebody already had before they went looking for a webshot API.
Social preview images
OG images from a real page, emoji included.
Generate the preview image from the page itself instead of reimplementing your design in an image library — and get the emoji right on every platform you are sharing to.
Visual regression
A diff that means the page changed.
Byte-identical output for the same request against the same renderer version, so a difference between two runs is a difference in the page rather than in the machine that photographed it.
Design QA across platforms
How the page reads on a device you do not own.
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.
Docs and changelogs
Screenshots of your own product, from CI.
Take the pictures in your documentation on every release, from the pipeline, so they are never a version behind the thing they document.
Take your first webshot in a minute
Sign up, paste a URL in the form, and see it. Reach for a token when you are ready to automate it.