CaptureKit Pricing for Scheduled Website Screenshots

CaptureKit lists plans from a $0 monthly free trial with 100 credits to $89 per month with 50,000 credits. A successful Screenshot API capture costs one credit, so estimate scheduled usage by multiplying the number of URLs by captures per URL per billing period, then allow for retries and any other API calls.

For example, capturing 100 URLs once a day for a 30-day month requires about 3,000 successful capture calls before retries. CaptureKit’s Pro plan is listed at $29 per month with 10,000 credits. The reviewed documentation describes API calls and integrations, but does not establish a native recurring schedule setting or a separate CaptureKit scheduling fee; check the scheduler or automation service you choose for its own charges.

CaptureKit plans and listed prices

These plan prices and credit allowances are from CaptureKit’s billing documentation. The pricing page also lists the same paid monthly tiers and says annual billing saves 10%. Confirm the selected billing cadence and live amount at checkout: CaptureKit’s billing documentation says checkout shows the current amount. Country-specific taxes and payment fees were not established in the reviewed sources.

Plan	Listed monthly price	Credits per month	Typical fit
Free trial	$0	100	Small evaluation or very low volume
Starter	$7	1,000	Lower-volume use
Pro	$29	10,000	Moderate scheduled volume
Ultimate	$89	50,000	Higher-volume use

These are listed subscription prices, not a complete estimate of an end-to-end scheduled workflow. Scheduler or automation platform charges may apply separately. CaptureKit’s pricing page names Zapier and Make integrations, but the reviewed endpoint documentation does not establish a recurring schedule feature or a separate scheduling price. See the [CaptureKit pricing page](https://www.capturekit.dev/pricing) and [billing documentation](https://docs.capturekit.dev/billing/plans-and-pricing) for current terms.

Estimate credits for a scheduled workload

CaptureKit documents one credit per successful Screenshot API capture. Start with this estimate:

monthly capture credits = URLs × captures per URL per month

Then add the calls your workflow expects to make for retries or other endpoints. This is a planning formula based on the documented per-call credit cost, not a guarantee of actual usage.

Workload	Calculation	Estimated capture calls
10 pages, once daily, 30 days	10 × 1 × 30	300
100 pages, once daily, 30 days	100 × 1 × 30	3,000
100 pages, four times daily, 30 days	100 × 4 × 30	12,000
500 pages, once weekly, about 4.3 weeks	500 × 1 × 4.3	About 2,150

For example, 100 pages captured daily for 30 days is about 3,000 calls. CaptureKit’s pricing calculator uses a 5,000-screenshot-per-month example and recommends Pro at $29 per month with 10,000 credits; it displays $5.80 per 1,000 screenshots for that example. Treat that as the calculator’s example, not a universal effective rate. CaptureKit also says failed requests are not charged and monthly credits reset. See its [screenshot pricing calculator](https://www.capturekit.dev/screenshot-api-calculator).

Include retries and workflow behavior

• Count each URL captured on each scheduled run. If a run captures three formats via three calls, account for those calls separately.
• Include retry attempts in your budget. CaptureKit’s credit reference says successful synchronous requests and completed asynchronous jobs are billed; consult it when deciding how your job states map to credits.
• Estimate from the schedule’s actual calendar period. A daily job can run 28 to 31 times in a month, and a weekly schedule may cross month boundaries.
• Check whether the integration retries automatically, and whether a retry creates another capture request.
• Keep some headroom for temporary failures and growing URL lists. The right buffer depends on your observed workload; the sources do not specify a universal retry rate.

The [CaptureKit credits reference](https://docs.capturekit.dev/credits) documents the per-call credit rule and the billing treatment for synchronous requests and completed asynchronous jobs.

Choose a plan for daily screenshots

1. List every page or URL to capture.
2. Set the intended frequency per URL and calculate the number of scheduled runs in a billing period.
3. Multiply URLs by runs, then add expected retries and any other billed API calls.
4. Compare that estimate with the plan allowances: 100, 1,000, 10,000, or 50,000 credits.
5. Check whether you need one-time quota packs, a different subscription tier, or a different billing cadence. CaptureKit says one-time packs can add quota without changing the tier.
6. Check the checkout amount and the charges for your scheduler or integration before relying on the total.

CaptureKit says quotas and rate limits are workspace-wide, so API keys share the workspace pool. Its billing documentation says upgrades apply immediately with a prorated charge, downgrades take effect at the period end, and changing plans does not invalidate existing keys. Verify current terms in the [billing documentation](https://docs.capturekit.dev/billing/plans-and-pricing).

Scheduling: what the reviewed documentation confirms

CaptureKit describes its Screenshot API as an HTTP API that you call from your backend, an automation platform, or an AI agent. Its pricing page names Zapier and Make integrations. The reviewed API reference documents capture parameters, but does not document a recurring cron or schedule parameter, nor a separate CaptureKit schedule charge. A careful setup is to arrange recurring calls with your own scheduler or an integration, then account for any charges that service applies. Do not assume the API subscription includes a scheduler.

Relevant primary references: [CaptureKit overview](https://docs.capturekit.dev/getting-started/overview), [pricing](https://www.capturekit.dev/pricing), and [Screenshot API reference](https://docs.capturekit.dev/capture).

Or skip the browser setup

If the goal is recurring clean page captures rather than operating capture infrastructure, [ScreenshotNeo](https://screenshotneo.com) is the first alternative to try: cookie banners, popups, and chat widgets are removed before the shot, and only clean shots are billed. Bot checks, blank pages, and failed loads are never billed; each response identifies the page verdict and billing status. Its MCP server lets AI agents use screenshot tools, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. See the [ScreenshotNeo API docs](https://screenshotneo.com/docs/) for parameters and setup.

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

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

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

Reliability, performance, and cost checks

• Reliability: Record each scheduled run’s URL, start time, result, and retry count in your own workflow so missed runs and repeated requests are visible. The reviewed CaptureKit sources do not establish a scheduling guarantee.
• Retries: Use bounded retries for transient failures and avoid immediate, unbounded retry loops. Successful capture calls consume credits according to the documented rule; failed requests are described as uncharged by the pricing calculator.
• Performance: Spread large capture batches over time if your scheduler or API rate limits require it. CaptureKit’s reviewed references do not provide a universal throughput figure, so use the account’s current limits and measure your own run duration.
• Cost: Budget for the API plan plus any scheduler, automation platform, or other workflow charges. Check annual versus monthly billing and live checkout pricing. Do not treat the calculator’s per-thousand example as a promise for your own mix of retries and jobs.
• Shared quota: Since API keys in a workspace draw from the same quota, coordinate scheduled jobs across teams and environments.

Troubleshooting

Symptom	Likely cause	What to do
Scheduled captures stop before month-end	The workspace has used its shared credit allowance.	Check total usage across all API keys and jobs, then adjust frequency, tier, or quota using the billing options.
Usage is higher than URL count suggests	The estimate omitted multiple daily runs, retries, other API calls, or asynchronous jobs.	Recalculate URLs × runs and inspect workflow retry behavior and the credits reference.
Two jobs appear to consume the same allowance	API keys share the workspace quota and rate limits.	Review all workspace jobs together; separate API keys do not provide separate pools according to the billing docs.
Workflow did not run at the expected time	The external scheduler or integration may not be configured for that recurrence or timezone.	Check the scheduler’s run history, recurrence, timezone, and its own service limits. The reviewed CaptureKit API reference does not define a cron setting.
Plan change does not immediately lower the charge	CaptureKit says downgrades take effect at the period end; upgrades are prorated immediately.	Check the effective date and live checkout or billing details.
Credits appear depleted despite failed attempts	Some requests may have succeeded, or asynchronous jobs may have completed.	Inspect the request and job results against CaptureKit’s documented charging rules; its calculator says failed requests are not charged.

Frequently asked questions

How many CaptureKit credits does one screenshot use?

The Screenshot API is listed at one credit per successful capture call. See the [credits reference](https://docs.capturekit.dev/credits).

Which CaptureKit plan covers 5,000 screenshots a month?

The pricing calculator’s 5,000-screenshot example recommends Pro at $29 per month with 10,000 credits. Your actual needs depend on retries and other calls.

Does CaptureKit include recurring scheduling?

The reviewed references document API capture and integrations, but do not establish a native recurring schedule control or a separate schedule fee. Arrange the recurrence through your backend or an integration and check its charges.

Do CaptureKit API keys each have their own credits?

No. CaptureKit’s billing documentation says workspace keys share quota and rate limits.

Can I add credits without changing plans?

CaptureKit’s billing documentation says one-time packs can add quota without changing the subscription tier. Check current availability and terms in billing.