CaptureKit API Cost per 1,000 Website Screenshots

Direct answer: CaptureKit documents one credit per screenshot call. At its listed monthly prices, 1,000 successful screenshot calls cost $7 on Starter if all 1,000 credits are used for screenshots. At full screenshot-only quota use, Pro works out to $2.90 per 1,000 and Ultimate to $1.78 per 1,000. These are plan-price calculations, not separate pay-as-you-go rates. [CaptureKit capture pricing · plans and pricing]

Your effective cost rises when credits go unused or are consumed by other billable endpoints. CaptureKit’s calculator’s $5.80 per 1,000 example is for 5,000 screenshots on a $29 Pro plan, which uses half of the listed 10,000-credit quota. [CaptureKit’s calculator]

CaptureKit cost by plan

Plan	Listed monthly price	Monthly credits	Derived screenshot-only cost per 1,000 at full quota
Free	$0	100	Not a paid-plan unit cost
Starter	$7	1,000	$7.00
Pro	$29	10,000	$2.90
Ultimate	$89	50,000	$1.78

The listed prices and quotas are from CaptureKit’s pricing materials. The per-1,000 figures are arithmetic: monthly plan price ÷ included monthly credits × 1,000. They assume every credit is used for a successful screenshot and no other billable endpoint. CaptureKit advertises a 10% annual-billing saving; confirm the current price and billing period at checkout before budgeting. [pricing page · plan documentation]

Calculate your effective screenshot rate

Use this formula for a simple estimate:

effective cost per 1,000 screenshots = monthly plan cost / successful screenshots * 1,000

For a Pro customer making 5,000 screenshot calls in a month:

$29 / 5,000 * 1,000 = $5.80 per 1,000 screenshots

That matches the provider’s calculator example. If all 10,000 Pro credits instead go to successful screenshot calls, the arithmetic is $29 ÷ 10,000 × 1,000 = $2.90 per 1,000. Always use your expected successful capture volume, rather than the plan’s maximum quota, in the denominator.

What changes the number

• Unused credits: if you buy a plan but make fewer calls than its allowance, divide by your actual successful captures to estimate the effective rate.
• Other billable endpoints: credits are shared across the workspace. Calls made with another API key or to another billable endpoint reduce credits left for screenshots. [CaptureKit plan documentation]
• Failed captures: CaptureKit documents successful synchronous requests as billable and failed jobs as unbilled. Your actual invoice and successful output volume can therefore differ from a naive request-count estimate. [credits and billing]
• Annual billing: the advertised saving changes the plan-cost numerator. Check whether a displayed price is monthly or annualized, then use the actual billed amount for your own calculation.
• Top-ups: CaptureKit documentation describes one-time packs and separate credit balances. Treat those as supplemental purchases and include their cost and use in your own effective-spend calculation; do not assume every account has the same balance arrangement. [plans and pricing]

How CaptureKit credits are charged

The CaptureKit capture endpoint accepts a webpage URL and can return PNG, JPEG/JPG, WebP, or PDF. Its documented charge is one credit per call. [Capture endpoint documentation]

• Successful synchronous capture requests are charged.
• Asynchronous jobs are charged when they complete successfully. An accepted 202 response is not billed at acceptance.
• Polling an asynchronous job’s status is free.
• Failed jobs are documented as unbilled.
• Workspace quota and rate limits apply across API keys, so multiple applications can draw from the same allowance.

These billing behaviors are documented in CaptureKit’s [credits guide] and [plans documentation]. For an estimate, distinguish attempts, successful captures, and billable calls rather than treating them as interchangeable.

Is CaptureKit the right cost for your volume?

Compare providers at the same expected monthly volume and against the same requirements. A useful comparison includes:

1. Monthly price and included successful captures or credits.
2. Which endpoints share the credit balance.
3. Whether failed calls, queued async jobs, and status polls are billed.
4. Output formats and capture features your workflow needs.
5. Rate limits, over-quota behavior, and the terms for one-time credit packs.
6. Annual billing terms and the actual amount charged.

CaptureKit’s own comparison article names ScreenshotOne and ScreenshotAPI as alternatives, but it is vendor-authored and does not establish independent competitor pricing. The sources used here do not verify current numeric competitor prices, so compare each provider’s official pricing and billing documentation before choosing. [CaptureKit comparison article]

ScreenshotNeo is the first alternative to try: cookie banners, popups, and chat widgets are removed before capture, only clean shots are billed, and its paid plans start at $5 for 3,000 screenshots. See [ScreenshotNeo](https://screenshotneo.com) for product details.

Or skip the browser setup

ScreenshotNeo takes a URL in one GET request and returns an image or PDF. Here are runnable request examples; replace YOUR_API_KEY with your key and change the target URL as needed. The [ScreenshotNeo API docs](https://screenshotneo.com/docs/) describe the endpoint and options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

ScreenshotNeo removes cookie or consent banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, and cache hits cost nothing, and response headers say the page verdict and whether the request was billed. Its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up free for ScreenshotNeo.

Performance, reliability, and budgeting

Credit arithmetic tells you the unit cost, but not whether a capture workflow meets its latency or reliability needs. Measure your own workload: record attempted calls, successful image or PDF outputs, errors, and completion time over a representative period. For asynchronous work, account for queue completion separately from request acceptance, and avoid counting free status polls as screenshot volume.

For budgeting, use a conservative successful-capture forecast, reserve room for other workspace endpoints, and check current rate limits and overage or top-up terms in the official docs. Recheck live pricing before purchase; the research figures reflect the official materials accessed on October 3, 2026, and prices can change.

Troubleshooting cost estimates

Symptom	Likely cause	What to do
Your observed rate is higher than the plan table	You used fewer successful screenshot calls than the plan allowance, or other billable endpoints consumed shared credits.	Calculate price against actual successful screenshots and inspect workspace-wide usage by endpoint and key.
The calculator shows $5.80 per 1,000 on Pro	That scenario uses 5,000 captures on a $29 plan, half of the 10,000-credit allowance.	Use your actual volume. At full screenshot-only quota, the listed-plan arithmetic is $2.90 per 1,000.
Accepted async jobs appear in request counts but not charges	Queue acceptance is not the successful completion event.	Track completion results; accepted 202 jobs are not billed at acceptance, and polling is free.
Credits are lower than expected	Another API key, service, or endpoint in the workspace used shared credits.	Review workspace usage and account for all billable endpoints, not just the screenshot route.
A quoted plan amount does not match checkout	The quote may use annual billing, changed pricing, or a supplemental credit purchase.	Verify the current official pricing page and checkout billing period before relying on the estimate.

Frequently asked questions

Is $7 a published pay-as-you-go price for 1,000 screenshots?

No. It is the Starter monthly plan price divided by its 1,000-credit allowance, assuming the credits are spent on successful screenshot calls.

Does the 100-credit free plan provide 1,000 screenshots?

No. The listed free allowance is 100 credits. At one credit per screenshot call, that is up to 100 successful screenshot calls if the credits are used only for captures.

Which CaptureKit plan has the lowest derived cost per 1,000?

Ultimate at $1.78 per 1,000 when all 50,000 monthly credits are used for successful screenshots. That assumes the full quota is useful to your workload.

Should I compare these figures with a competitor’s advertised rate?

Only after checking the same volume, included quota, successful-call billing, output needs, and overage rules in that competitor’s current official documentation.