ScreenshotAPI Cost per 1,000 Website Screenshots

Direct answer: For ScreenshotAPI.to, the published subscription allowance works out to about $3.80 per 1,000 screenshots on Starter, $1.96 on Growth, and $1.49 on Scale—assuming you use the full monthly allowance. Listed overages cost $6, $4, and $3 per 1,000, respectively. Prepaid packs range from $9 to about $2.99 per 1,000 credits.

“ScreenshotAPI” can refer to different services. These figures are for ScreenshotAPI.to, not ScreenshotAPI.net or other providers. Prices and promotional terms can change; check the linked pricing page and checkout before buying. The figures below are arithmetic from vendor-published prices and quotas, not a separate quote.

1. ScreenshotAPI.to price per 1,000 screenshots

Option	Published price and quota	Effective price per 1,000	Important detail
Free	$0 for 200 per month	$0 within quota	Pricing page says no card is required.
Starter subscription	$19/month for 5,000	$3.80	Overage: $0.006 per capture, or $6 per 1,000.
Growth subscription	$49/month for 25,000	$1.96	Overage: $0.004 per capture, or $4 per 1,000.
Scale subscription	$149/month for 100,000	$1.49	Overage: $0.003 per capture, or $3 per 1,000.
Starter credit pack	$9 for 1,000 credits	$9.00	One-time pack; credits do not expire.
Growth credit pack	$29 for 5,000 credits	$5.80	One-time pack; credits do not expire.
Pro credit pack	$99 for 25,000 credits	$3.96	One-time pack; credits do not expire.
Scale credit pack	$299 for 100,000 credits	$2.99	One-time pack; credits do not expire.

Subscription unit cost is the monthly price divided by the full included allowance, multiplied by 1,000. It is not the marginal price of one more capture. If you use only a fraction of your allowance, your effective cost per successful capture is higher. Overage is a separate rate that applies beyond the allowance, so budget using your likely monthly volume rather than the headline included rate.

2. How to calculate your actual monthly bill

Estimate the number of successful captures you need in a billing period.
For a subscription, divide the monthly fee by the included quota to get the full-use unit rate. Multiply by 1,000 for the table rate.
If you expect to exceed the quota, estimate overage as max(0, captures − quota) × overage per capture and add it to the subscription price.
For uneven or occasional demand, compare a prepaid pack with the subscription cost for the same expected successful volume.
Check whether caching will reduce billable usage for your workload, and confirm current terms on the pricing page.

Example: At 6,000 successful captures in a month on Starter, the listed calculation is $19 + (1,000 × $0.006) = $25, or about $4.17 per 1,000 total. This assumes the listed overage rate applies and excludes taxes or other checkout-specific charges.

For 2,000 captures, Starter’s nominal allowance is ample, but paying $19 for 5,000 means the effective spend is $9.50 per 1,000 captures used. A credit pack may suit intermittent usage better, though the right choice depends on current terms and whether you need subscription features.

3. Billing rules that change the comparison

Successful captures: ScreenshotAPI.to documents one credit per successful screenshot capture; failed requests are not charged. Do not generalize that rule to other providers.
Quota resets: The free allowance resets on the first day of the month. Paid subscription allowance resets on the subscription anniversary.
Purchased credits: Packs do not expire. The included subscription allowance is used before purchased credits.
Cached responses: The pricing page says cached responses are not counted against the monthly allowance.

See the provider’s screenshot API documentation for its capture billing and quota mechanics, and its pricing page for current subscription, overage, pack and caching terms.

4. Which ScreenshotAPI.to option fits?

Usage pattern	Starting point to compare	Why
Testing or a small recurring workload	Free or Starter	Free provides 200 per month; Starter has 5,000 included.
Steady usage around 5,000–25,000 monthly	Starter versus Growth	Growth’s full-use rate is lower, but only if the larger quota is useful.
Consistently high usage	Growth versus Scale	Scale has the lowest listed subscription unit rate and overage rate in this schedule.
Irregular usage or a one-off batch	Prepaid pack versus subscription	Pack credits do not expire, while subscription quotas reset each billing period.

The table is a starting point, not a universal recommendation. Include the cost of unused quota, overages, cache behavior, failed requests, output needs and any operational limits in your decision.

5. ScreenshotAPI.to versus ScreenshotNeo

1. ScreenshotNeo is the first alternative to consider if clean output and predictable treatment of failed captures matter: it removes cookie banners, newsletter popups and chat widgets before capture, bills only clean shots, and its lowest paid plan is $5. Its published plans work out to $1.67 per 1,000 at Starter ($5 for 3,000), $1 at Growth ($15 for 15,000), about $0.65 at Pro ($39 for 60,000), about $0.40 at Scale ($99 for 250,000), and about $0.25 at Business ($249 for 1,000,000), assuming the full allowance is used. The free plan includes 1,000 shots per month with no card. Details at ScreenshotNeo.

2. ScreenshotAPI.to lists $3.80, $1.96 and $1.49 per 1,000 at full use of its Starter, Growth and Scale subscription quotas. Its packs do not expire, and the published pack rates run from $9 to about $2.99 per 1,000. These are different billing models and product terms, so compare the volume you actually expect and verify current prices before purchase.

6. Get a screenshot with ScreenshotNeo

For ScreenshotNeo’s own API, one GET request takes a URL and returns an image or PDF. The following runnable examples request a WebP screenshot of Stripe; replace the target URL with the page you need. Create an API key through the service and keep it out of public client-side code. See the ScreenshotNeo API documentation for request 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} ${await res.text()}`);
await Bun.write('shot.webp', res);

In Node.js versions without Bun.write, save the response with your preferred file API; for example, use node:fs/promises and write the response body bytes.

7. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its API supports PNG, JPEG, WebP and PDF. 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 use the take_screenshot, get_page_info and capture_pdf tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Its options include full-page and selector captures, device presets, custom headers and cookies, wait conditions, caching, bulk capture and more. Each response includes page-verdict and billing headers.

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

Read the API docs and sign up free for 1,000 screenshots a month with no card.

8. Cost, performance and reliability considerations

Cost: Forecast successful monthly captures, unused quota and overage separately. Use vendor billing rules for failed requests and cache hits; do not assume another provider bills the same way.
Performance: Screenshot cost alone does not establish latency. Page complexity, network conditions, wait settings, image loading and capture size can affect how long a request takes. Test representative pages and set client timeouts that allow for slow pages.
Reliability: Treat timeouts and failed loads as capture failures, record status and response metadata, and retry transient failures with a bounded backoff. Avoid unbounded retries that multiply load or create duplicate work.
Freshness: Caching can lower repeated capture cost where supported, but confirm the cache TTL and invalidation behavior you need. A cached image may not reflect recent page changes.

9. Common pricing mistakes and troubleshooting

Symptom or mistake	Likely cause	What to do
The quoted rate does not match the checkout	Prices or promotions changed, or the calculation used a different provider/domain.	Confirm the exact domain is screenshotapi.to and recheck the official pricing page and checkout.
Effective cost per 1,000 is higher than the plan table	You used less than the full monthly allowance, or overage applied.	Calculate total spend divided by successful captures, then multiply by 1,000.
Credits appear to be consumed differently than expected	Subscription allowance is used before purchased packs; reset dates differ by plan type.	Check the account’s billing period and the provider’s documented credit order.
A cached result does not count as expected	The pricing page says cached responses are excluded from monthly allowance.	Include cache hits separately in your estimate and verify current provider terms.
Comparison pages show different ScreenshotAPI prices	ScreenshotAPI.to and ScreenshotAPI.net are separate services.	Compare by domain, not brand shorthand. See the distinct ScreenshotAPI.net pricing page.

10. Frequently asked questions

Does ScreenshotAPI.to charge for failed requests?

Its documentation says failed requests are not charged. That billing statement applies to ScreenshotAPI.to’s documented capture API; verify terms for any other service.

Do ScreenshotAPI.to credit packs expire?

The pricing information says purchased packs do not expire. Subscription allowances reset each billing period.

Is ScreenshotAPI the same as ScreenshotAPI.net?

No. They are separate providers with separate pricing pages. This article’s main calculations refer to ScreenshotAPI.to.

Are these prices guaranteed at checkout?

No. They reflect published rates retrieved on October 3, 2026. Confirm live pricing and terms before subscribing.

Sources

ScreenshotAPI.to pricing — subscription prices, quotas, overages, credit packs and cache billing claim.
ScreenshotAPI.to screenshot API documentation — capture billing and quota mechanics.
ScreenshotAPI.net pricing — separate service, included to clarify provider naming.