One credit per successful capture.
A full-page PNG, a 40-page PDF, a scrolling screenshot and a 30-second video all cost the same: one credit. Failures cost nothing. Cache hits cost nothing.
Every feature unlocked, capped at 100 successful captures a month.
- 100 credits
- 5 starts / minute
- IP location — not available yet
- Scrolling screenshots
- Video and animated GIF
- GPU rendering — not available yet
$100/year — two months off
Images, PDF, HTML and Markdown for a single production workload.
- 2,000 credits
- 40 starts / minute
$470/year — two months off
Adds scrolling screenshots and video capture.
- 10,000 credits
- 80 starts / minute
- IP location — not available yet
- Scrolling screenshots
- Video and animated GIF
$1550/year — two months off
Priority support and the highest limits for heavy pipelines.
- 50,000 credits
- 150 starts / minute
- IP location — not available yet
- Scrolling screenshots
- Video and animated GIF
- GPU rendering — not available yet
- Priority support
Enterprise
Contracted volume, custom limits and additional controls. Contracted volume, custom rate limits, data-residency discussion and an agreement your legal team can actually sign.
How billing actually works
Only successful, non-cached captures
A capture that fails for any reason — timeout, missing selector, DNS, or our own bug — costs nothing. Neither does a cache hit.
Format does not change the price
A 40-page PDF and a 1200×630 thumbnail are both one credit. Video is one credit too.
Retries are free
If our worker crashes and retries internally, the request id stays the same and you are charged once.
Credits reset monthly
They do not roll over. The period starts on the first of the month, UTC.
Overage is opt-in
With it off, you get screenshots_limit_reached instead of a surprise invoice. With it on, extra credits bill in blocks of 1,000.
You set the ceiling
The hard limit is yours to choose, and it is enforced before the job enters the queue, not after.