How Credits Work
Each plan includes a monthly or yearly allowance of screenshot credits. Understanding how credits are consumed helps you optimize your usage.What consumes credits
| Action | Credits |
|---|---|
| Successful screenshot | 1 credit |
| Failed screenshot | Free |
| Cached screenshot | Free |
Cached requests
Screenshots are cached for 4 hours. When you make identical requests within this window:- Cache hit: Free, no credits consumed
- Cache miss: 1 credit consumed (successful capture)
fresh=true parameter to bypass cache and force a new screenshot.
When credits reset
Credits are added at the beginning of each billing cycle:- Monthly plans: Credits added on the same day each month
- Yearly plans: Credits added annually on your signup date
Overage charges
If you exceed your credit allowance, you can continue using the service with overage charges:| Plan | Overage rate |
|---|---|
| Starter | $0.004 per credit |
| Growth | $0.002 per credit |
| Scale | $0.001 per credit |
Monitoring your usage
Check your credit balance and usage in the dashboard. The API also includes rate limit headers in every response:| Header | Description |
|---|---|
X-RateLimit-Limit | Requests per minute for your plan |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | ISO timestamp when window resets |
Tips to minimize credit usage
- Use cache: Make identical requests to benefit from 4-hour cache
- Optimize parameters: Only capture what you need (viewport, format)
- Batch requests: Group similar requests to maximize cache hits
- Set limits: Configure usage alerts in your dashboard
View your usage
Check your credit balance and usage statistics in the dashboard.
See also
- Pricing - Plan comparison and allowances
- Caching - How caching works
- Rate Limits - Request rate limits