Priced per webshot, not per request
A webshot is what costs a Chrome tab for half a second — the only unit you can predict before you call us. Failed renders are not billed.
100 webshots a month
- One emoji set
- 7-day retention
- 10-second render ceiling
- Community support
2,000 webshots a month
- All eight emoji sets
- PDF output
- 30-day retention
- 15-second render ceiling
- Email support
15,000 webshots a month
- Everything in Hobby
- Priority render lane
- Webhooks
- Scheduled captures and visual diff
- 90-day retention
- 30-second render ceiling
- Three seats
75,000 webshots a month
- Everything in Pro
- Reserved render capacity
- 99.9% availability target
- Ten seats
- Custom retention
- Invoicing and a signed DPA
What counts as a webshot
The rules, before you have to discover them from an invoice.
Questions about the bill
No. It does not expire and it does not ask for a card. It is small enough to be a real cost to us only if somebody automates against it, which is what the rate limit is for.
The new allowance applies immediately and you are charged the difference for the rest of the period. Downgrades take effect at the end of the period, so you never lose allowance you have already paid for.
Not yet. When there is, it will be the usual two months off, and it will not be the only way to get a feature.
A seat is a person who can sign in to the team and see its webshots and keys. API tokens are not seats — you can have as many as you want on any plan.
If something we did lost you renders, yes, and you should not have to argue for it. Email support@webshotter.com.
Start on the free plan
A hundred webshots a month, no card, no expiry. Move up when the pipeline you built on it matters.