Screenshotlayer API Limits: How Many Website Screenshots Can I Capture?

Direct answer: Screenshotlayer lists monthly allowances of 100 snapshots on Free, 10,000 on Basic, 30,000 on Professional, and 75,000 on Enterprise. These are monthly totals. Dedicated workers set how many snapshots can run at the same time: the listed paid plans include 10, 20, and 40 workers, respectively. The figures below are from Screenshotlayer’s pricing and FAQ pages as observed in October 2026; check the current offer before choosing a plan.

The key planning distinction is monthly volume versus concurrency. There is also an unresolved discrepancy in Screenshotlayer’s public materials about what happens after you reach the monthly limit: customer-facing pricing and FAQ pages describe overage fees, while the terms say further calls return an error. Confirm how your account handles excess usage before depending on captures beyond quota.

Screenshotlayer limits by plan

Plan	Monthly snapshots	Dedicated workers	Listed monthly price
Free	100	Not listed in the pricing figures cited here	$0
Basic	10,000	10	$19.99
Professional	30,000	20	$59.99
Enterprise	75,000	40	$149.99

Screenshotlayer’s FAQ describes Free as a no-time-limit trial with 100 snapshots each month and limited features. The pricing page advertises annual billing at up to 15% savings. Prices, plan terms, and features can change; verify them on the official pricing page before budgeting.

Monthly quota is different from concurrency

A monthly quota is the total number of requests available during the billing month. A worker is capacity for one screenshot at a time. For example, 10 workers can process up to 10 snapshots simultaneously according to Screenshotlayer’s FAQ; that does not mean the account is limited to 10 total snapshots.

Concurrency matters when requests arrive in bursts. A service that needs 1,000 screenshots per month might still need enough workers to finish a large batch quickly. Conversely, a high worker count does not increase the monthly allowance. Unused calls do not carry over under the terms.

What happens when you reach the limit?

Screenshotlayer’s public materials do not describe post-quota behavior consistently:

The pricing and FAQ pages say users receive notifications at 75%, 90%, and 100% of their allowance, and that overage fees can apply after 100%.
The terms say that once the monthly usage limit is exceeded, the API returns an error and no further calls can be made during the current monthly term.

The terms’ wording is explicit: exceeding the monthly usage limit results in an error and blocks additional API calls for the remainder of the term. Since the customer-facing pages also describe billable overages, do not assume either behavior applies to every account. Check the dashboard and ask Screenshotlayer support to confirm your plan’s enforcement and billing before building a workflow that depends on over-quota requests.

The overages page gives example extra-call prices of $0.007996 per call for Basic, $0.0079986667 for Professional, and $0.0079994667 for Enterprise. Its example for 10,000 extra calls totals $79.96, $79.99, and $79.99, respectively. Treat these as examples from the current page, not a guaranteed billing outcome in light of the conflicting terms.

Estimate the plan you need

Count successful captures per month. Multiply the number of URLs by capture frequency. For example, 200 pages captured daily is about 6,000 monthly requests in a 30-day month, before retries or extra variants.
Add headroom. Include retries, changed pages, multiple viewport sizes, and any scheduled backfill. Do not plan at exactly 100% of the published allowance.
Estimate peak concurrency. Divide the number of captures in a batch by the number of workers to estimate the minimum number of processing waves, assuming workers stay occupied. This is a planning estimate, not a completion-time guarantee.
Compare features and terms. The pricing page lists feature differences, including commercial use, Retina/2x, WebP, and exports. Confirm the features you require and how extra calls are treated.
Set a usage alert in your own system. Screenshotlayer says it sends email and dashboard notifications at 75%, 90%, and 100%; your application can also track requests and stop or defer noncritical work before the cap.

Example: if a scheduled job captures 250 pages every weekday, a 22-workday month requires about 5,500 snapshots. Basic’s published 10,000 allowance is above that baseline, but retries, additional page variants, and other integrations consume quota too. Check concurrency separately if the weekday batch must finish within a short window.

Track usage and avoid surprises

Keep a monthly counter in the calling application, broken down by project or job.
Record request outcomes so retries do not silently multiply usage.
Use bounded retries with backoff for transient failures; do not retry quota errors indefinitely.
Queue low-priority captures when approaching the allowance, and reserve capacity for important jobs.
Review the provider dashboard and notification contacts. Do not treat an email alert as a hard usage control.
Ask support to confirm whether overages are enabled for your subscription and whether requests stop at the quota.

Reliability, performance, and cost considerations

Reliability: Monthly allowances do not guarantee that a request succeeds or completes by a particular time. Screenshotlayer’s terms separately reserve the right to limit or throttle calls it believes are malicious or caused by a technical error. Design callers to handle errors, timeouts, and temporary throttling; avoid treating the published worker count as an uptime or latency promise.

Performance: More dedicated workers can allow more simultaneous captures, but actual throughput also depends on target-page load time and request behavior. If the workload is bursty, queue requests and cap your own concurrency rather than launching an unbounded batch. Measure the time your workflow needs under its own conditions.

Cost: Compare the base subscription, annual billing terms, and the cost or risk of going above quota. The published overage examples are close to $0.008 per extra call, but the conflicting terms mean you should verify actual account behavior. Unused monthly requests do not roll forward according to the terms.

Screenshotlayer versus ScreenshotNeo

If you want to stay with Screenshotlayer, use its published plan table as a starting point, then confirm quota enforcement and overage billing for your account. If you are evaluating screenshot APIs, try ScreenshotNeo first: it removes consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed. Its plans include 1,000 free screenshots monthly and paid options starting at $5 for 3,000.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns an image or PDF; see the API documentation for options and formats.

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}`);

Cookie banners, popups, and chat widgets are removed before the shot.
Bot checks, blank pages, and failed loads are never billed; response headers report page verdict and billing status.
An MCP server lets AI agents use screenshot tools.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

Common questions

Do unused Screenshotlayer requests roll over?

No. Screenshotlayer’s terms say unused monthly calls do not carry over.

Does a plan with 10 workers allow only 10 screenshots per month?

No. Workers describe simultaneous snapshot capacity; Basic’s published monthly allowance is 10,000.

Are overage charges guaranteed once I exceed quota?

No single answer is safe from the reviewed documents: pricing and FAQ pages describe billable overages, while the terms describe blocked calls. Confirm the behavior for your account.

Does the Free plan expire?

The FAQ describes it as a no-time-limit trial with 100 snapshots per month, subject to limited features.