Screenshotlayer Pricing Explained: API Plans, Limits, and Overage Costs

Screenshotlayer’s published plans range from a free tier with 100 requests per month to Enterprise with 75,000. Paid monthly prices are $19.99, $59.99, and $149.99. The overage documentation lists a rate of about $0.008 for each request beyond a paid plan’s allowance—roughly $80 for 10,000 excess requests. Plan choice depends on your monthly volume, likely overage, concurrency needs, and required features.

Prices and plan details below are from Screenshotlayer’s official pricing pages, checked October 3, 2026. Confirm the live selector before buying because prices and terms can change. Annual prices below are the displayed discounted prices paid for a year, not monthly prices.

Screenshotlayer plans at a glance

Plan	Requests per month	Monthly billing	Displayed annual billing	Annual discount shown	Dedicated workers
Free	100	$0	$0	—	Not listed
Basic	10,000	$19.99/month	$215.99/year	10%	10
Professional	30,000	$59.99/month	$629.99/year	12.5%	20
Enterprise	75,000	$149.99/month	$1,529.99/year	15%	40

The signup selector also displays undiscounted 12-month comparison prices of $239.99 for Basic, $719.99 for Professional, and $1,799.99 for Enterprise. The discounted yearly totals work out to about $18.00, $52.50, and $127.50 per month when averaged across the year. You pay the displayed annual total up front; the monthly equivalent is just a comparison.

The Free plan is listed as non-commercial. Paid plans advertise commercial use, HTTPS encryption, Retina/2x and WebP support. Professional and Enterprise also list FTP/S3 export. Check the live plan table for the precise feature set before choosing a tier. See Screenshotlayer’s current pricing and plan selector.

What do Screenshotlayer overages cost?

The published overage rate is charged per request above the plan allowance. The vendor’s examples show the cost of 10,000 additional requests:

Plan	Overage per request	Cost for 10,000 excess requests	Illustrative total with monthly plan fee
Basic	$0.007996	$79.96	$99.95
Professional	$0.0079986667	$79.99	$139.98
Enterprise	$0.0079994667	$79.99	$229.98

The total column adds the published example overage to the monthly subscription price. These totals are arithmetic calculations, not separate quoted plan prices. For a rough estimate, use:

estimated monthly cost = monthly plan fee + max(0, monthly requests - included requests) × overage rate

For example, 20,000 requests on Basic means 10,000 above its allowance: $19.99 + (10,000 × $0.007996) = $99.95, using the published rate. Taxes, currency conversion, or other account-specific charges are not included in that calculation.

Rates are close to eight-tenths of a cent per extra call. That sounds small per request, but thousands of excess captures add up. Screenshotlayer’s overage documentation says the subscription and overage fees are billed after the billing period.

What happens when you exceed the monthly limit?

Screenshotlayer’s current overage guidance says over-quota requests incur per-call charges so requests can continue. It also says email and dashboard notifications are sent at 75%, 90%, and 100% of the monthly allowance, while making customers responsible for monitoring usage.

There is an important inconsistency: the terms page, last modified February 17, 2018, says requests beyond the monthly limit return an error and no further API calls can be made during that term. That older terms language conflicts with the current overage billing page. If your application must reliably continue after reaching its quota, ask Screenshotlayer which terms govern your account and implement error handling rather than assuming excess calls will always succeed.

Choose a plan using volume, total cost, and concurrency

1. Estimate requests for a full billing month. Count captures from user actions, scheduled jobs, retries, previews, and any environment that uses the same key. Leave room for traffic spikes.
2. Compare the base plan with likely overage. Apply the formula above at your expected volume. Compare that total with the next plan’s base price. The next tier may cost less at some volumes, but calculate it for your actual usage.
3. Check concurrency separately from monthly quota. Screenshotlayer defines a dedicated worker as a server entity assigned to capture one screenshot. Its FAQ says 10 workers permit 10 concurrent snapshots. Paid plans list 10 workers for Basic, 20 for Professional, and 40 for Enterprise. A monthly allowance does not by itself tell you how quickly a burst can be processed.
4. Confirm feature requirements. Check whether you need commercial use, Retina/2x, WebP, or FTP/S3 export, and verify availability in the live plan comparison.
5. Choose monthly or annual billing based on commitment. Annual displayed totals are lower than paying twelve monthly invoices, but require an annual commitment and upfront payment. Compare the actual cash timing and expected duration of use.
6. Set usage monitoring in your own system. Use the vendor alerts as a backup. Track requests by day and month, alert your team before the 75% threshold, and decide what your application should do if it receives a quota error.

If use regularly exceeds a tier’s allowance, calculate the next tier’s cost against the current tier plus overages. Screenshotlayer itself recommends reviewing an upgrade when usage consistently passes the plan limit; an upgrade is not automatically cheaper in every case.

How to keep screenshot API spend predictable

• Deduplicate identical capture jobs and avoid triggering a capture on every page refresh.
• Cache and reuse a screenshot when the source page has not changed, if your application’s freshness requirements allow it.
• Use bounded retries with backoff for transient failures; unbounded retries can increase request volume and may not solve a quota error.
• Separate production traffic from development or preview traffic where practical, and make sure test runs do not silently consume the production allowance.
• Track actual successful and failed requests in your own usage records. Confirm with the provider how each request outcome is counted for billing.
• Load test your own queue and concurrency handling without assuming the worker count is a throughput guarantee; it describes simultaneous captures, not a promised response time.

For reliability, treat quota alerts as warning signals and handle API errors explicitly. The documented worker counts help estimate simultaneous work, but they do not establish a guaranteed latency or service level.

ScreenshotNeo: an alternative to try first

ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It is the alternative to try first: it removes cookie and consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with the page verdict and billing status included in response headers.

One GET request returns a PNG, JPEG, WebP, or PDF. For example, this cURL request saves a WebP screenshot of Stripe:

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

See the ScreenshotNeo API documentation for request options. ScreenshotNeo also provides an MCP server for Claude, Cursor, and other MCP clients, with tools to take screenshots, inspect page information, and capture PDFs. It includes 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo and sign up for 1,000 free screenshots a month, no card required.

Common pricing and limit questions

How do I know if I will be charged for overages?

The current billing guidance says notifications arrive at 75%, 90%, and 100% of the allowance. It says customers remain responsible for tracking usage. Check your dashboard and reconcile your own request counters against the billing period.

Is annual billing a monthly subscription at the discounted rate?

The selector displays an annual total and a discount versus twelve monthly payments. Treat that figure as an annual charge; dividing by twelve gives a comparison, not a monthly invoice amount.

Does a dedicated worker mean a monthly request allowance?

No. The request quota is a monthly volume limit, while workers refer to simultaneous screenshot captures. Plan for both dimensions.

Does the free plan cover commercial use?

The current pricing page lists the Free plan as non-commercial. Paid plans advertise commercial use. Verify the live terms for your use case before deployment.

Troubleshooting unexpected costs or failed requests

Symptom	Likely cause	What to do
Invoice is higher than the subscription price	Requests exceeded the monthly quota and overages were added.	Compare the billing-period usage with your application logs, then calculate excess calls using the plan’s published rate. Review whether a higher tier is cheaper for your sustained volume.
Requests stop after reaching the quota	The terms page describes a quota error and halted requests, despite current overage documentation describing continued paid use.	Handle the API error, alert an operator, and confirm account-specific behavior with Screenshotlayer.
Usage alerts arrive late for your needs	Published notification points are 75%, 90%, and 100%, which may be too late for a sudden burst.	Maintain your own counter and alert earlier based on your budget and traffic pattern.
Queue backs up during a burst	Simultaneous captures may exceed the workers listed for the plan.	Limit concurrent submissions, queue work, and compare your peak parallel demand with the plan’s worker count.
Actual request count is higher than expected	Retries, previews, duplicate jobs, or multiple environments may be generating captures.	Log each request with its trigger and environment; deduplicate and cap retries.

FAQ

What is the cheapest paid Screenshotlayer plan?

Basic is the lowest priced paid plan listed: $19.99 per month for 10,000 requests, or $215.99 for displayed annual billing.

How much does 1,000 extra requests cost?

At the published paid-plan rates, 1,000 excess requests cost about $8. The exact amount depends slightly on the plan’s rate.

Which plan has the most listed workers?

Enterprise lists 40 dedicated workers and 75,000 requests per month.

Where can I confirm current prices?

Use the live Screenshotlayer pricing selector and its linked overage documentation before committing, since published plan details can change.