CaptureKit Free Plan Limits for Website Screenshot Captures
CaptureKit’s Free plan includes 100 credits per month. Here’s how that translates to screenshot captures, what shares the quota, and how to check your usage.
Direct answer: CaptureKit’s Free plan is listed at $0 per month with 100 credits per month. A successful screenshot capture uses one credit, so the allowance can cover up to 100 successful captures in a billing period if you spend no credits on other billable CaptureKit endpoints. The quota is shared across every API key in your workspace. CaptureKit’s plan documentation and credit documentation describe these limits.
What does 100 credits mean for screenshots?
CaptureKit charges one credit for each successful screenshot capture. That makes the arithmetic straightforward: 100 credits can pay for 100 successful screenshot calls. It is a maximum, not a separate bucket reserved just for screenshots. Other billable endpoints use the same workspace quota, so using them reduces the credits left for captures.
| Usage | Credits | Captures left from 100, if no other usage |
|---|---|---|
| One successful screenshot capture | 1 | 99 |
| 25 successful screenshot captures | 25 | 75 |
| 100 successful screenshot captures | 100 | 0 |
| A billable call to another endpoint | Endpoint dependent | Reduced by that endpoint’s cost |
The plan documentation lists Free at $0/month and 100 credits/month. It also lists Starter at $7 for 1,000 credits, Pro at $29 for 10,000 credits, and Ultimate at $89 for 50,000 credits. Pricing can change; check the live plan page or your dashboard before making a purchasing decision.
How the shared quota works
The allowance applies to the workspace, not to each API key. If a team has multiple keys, requests made with all of them draw from the same pool. Creating another key does not create another 100-credit allowance.
CaptureKit says subscription quota renews each billing period. The exact renewal date and current remaining balance depend on your workspace. Check the dashboard’s usage view or its machine-readable Usage endpoint rather than estimating from the plan name. The Usage endpoint is documented as free to call.
When CaptureKit charges credits
For a synchronous request, CaptureKit documents billing on a successful HTTP 200 response. For an asynchronous request, the accepted 202 response is not the billable completion: a successfully completed job is billed when it finishes, and polling the job status is free. Failed jobs are not billed. CaptureKit notes endpoint-specific handling for 404 responses, so do not assume every error status has identical billing behavior. Consult the endpoint’s own billing details for unusual responses.
- Successful synchronous screenshot: one credit.
- Accepted asynchronous screenshot job: not billed at acceptance; billed if it completes successfully.
- Polling job status: free according to the credit documentation.
- Failed job: not billed according to the credit documentation.
- 404 response: billing depends on endpoint; verify the specific endpoint.
How to estimate and monitor usage
- Count successful screenshots. Start with the number of captures you expect to return successfully during the billing period.
- Add other billable API calls. The screenshot endpoint is not the only endpoint that can consume credits.
- Multiply captures by one. Each successful screenshot capture is one credit.
- Leave room for shared usage. Include requests from teammates, scheduled jobs, and other API keys in the same workspace.
- Check the live balance. Use the dashboard or the documented Usage endpoint to see current usage and renewal information.
For a workload that takes 70 screenshots and makes 20 other one-credit calls in the same period, the documented costs add to 90 credits. That leaves 10 of the 100-credit allowance, assuming all calls succeed and no other billable usage occurs.
Free plan details to verify before relying on it
The plan quota is documented clearly, but CaptureKit’s pricing page has conflicting information for some advanced feature entitlements: descriptive bullets and feature-comparison rows do not agree. If your workflow depends on an advanced option, verify its availability in the current account dashboard or with CaptureKit support. Do not infer access from a marketing bullet alone.
Plan limits and prices are volatile. The numbers here reflect the official documentation retrieved on October 3, 2026. Confirm the live pricing page and workspace dashboard before designing a production budget around them.
What if 100 captures are not enough?
If your capture volume is higher, compare the live paid-plan quotas with your expected successful calls and other endpoint use. At the figures currently listed in the plan documentation, Starter includes 1,000 monthly credits for $7, Pro includes 10,000 for $29, and Ultimate includes 50,000 for $89. Use the current dashboard checkout amount as the source of truth.
If you are evaluating screenshot APIs, ScreenshotNeo is a useful alternative to try first: cookie banners, popups, and chat widgets are removed before capture, and only clean screenshots are billed.
Or skip the browser setup
ScreenshotNeo returns a screenshot or PDF from one GET request, without setting up a browser. For example, this cURL command saves a WebP capture of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up free for ScreenshotNeo.
Troubleshooting credit questions
“I have multiple API keys. Why is the allowance shared?”
CaptureKit applies plan quota workspace-wide. All keys in a workspace share the same pool, so adding keys does not increase the quota.
“A screenshot failed. Did it use a credit?”
CaptureKit’s credit documentation says failed jobs are not billed, and synchronous calls are billed on HTTP 200. Check the request log and the endpoint documentation for the specific status, especially for 404 responses, whose billing can vary by endpoint.
“Why did an asynchronous request not reduce my balance yet?”
An accepted 202 response is not billed immediately. CaptureKit documents charging when the job completes successfully. Status polling is free.
“The dashboard and my estimate disagree.”
Include usage from every API key and every billable endpoint in the workspace, then check the current usage view. A screenshot-only estimate will be too high if other calls consume credits.
“The Free plan page says a feature is included, but the comparison table says it is not.”
The pricing information has conflicting feature details for some advanced capabilities. Check the current dashboard or ask CaptureKit support before depending on that feature.
FAQ
Does Free mean 100 screenshots every month?
It means 100 monthly credits. That is enough for up to 100 successful screenshot captures only when no credits are spent on other billable endpoints.
Does polling an asynchronous screenshot job use a credit?
No. CaptureKit documents status polling as free.
Do credits carry over?
The plan documentation describes a monthly subscription quota. Check the live plan and dashboard for current renewal and rollover terms before relying on unused credits.
Can I use the same quota with a team?
Yes. The quota is workspace-wide and shared by its API keys.
Are PNG, JPEG, WebP, and PDF supported on Free?
The pricing page lists those output formats among Free features. Verify your current account if a particular format or related advanced setting is essential.
