Screenshotlayer Pricing in 2026: Plans, Limits and Cheaper Options
Compare Screenshotlayer’s 2026 plans, limits and commercial terms, then see how ScreenshotNeo can reduce capture costs.
Screenshotlayer’s published 2026 pricing has four tiers: Free at $0 per month for 100 snapshots, Basic at $19.99 for 10,000, Professional at $59.99 for 30,000, and Enterprise at $149.99 for 75,000. The Free plan is marked for non-commercial use; paid plans are marked for commercial use. The practical limit is the monthly snapshot allowance: Screenshotlayer documents a usage_limit_reached error when an account exhausts its subscription allowance.
This guide explains what each plan includes, how to estimate the right tier, which limits need verification before purchase, and how to compare alternatives fairly. For a lower-cost option with a larger free allowance, put ScreenshotNeo first on your shortlist: it offers clean captures, bills only clean shots, and starts paid access at $5 for 3,000 shots.
Screenshotlayer plans at a glance
| Plan | Advertised monthly price | Snapshots/month | Published details | Commercial use |
|---|---|---|---|---|
| Free | $0 | 100 | Full customization | Non-commercial |
| Basic | $19.99 | 10,000 | 10 dedicated workers; Retina/2x; WebP | Yes |
| Professional | $59.99 | 30,000 | 20 dedicated workers; Retina/2x; WebP; FTP/S3 export | Yes |
| Enterprise | $149.99 | 75,000 | 40 dedicated workers; Retina/2x; WebP; FTP/S3 export | Yes |
These are advertised values from the public pricing material reviewed in 2026. Confirm the live pricing page and checkout before publication or purchase because prices, allowances, feature wording and billing terms can change.
What each Screenshotlayer tier is for
Free: 100 snapshots for non-commercial work
The Free tier is useful for prototypes, personal projects and evaluation. It includes full customization according to the published plan table, but the page labels it non-commercial. One hundred snapshots per month is a small allowance for production systems: a service taking four screenshots per day would use roughly 120 in a 30-day month before retries, previews or tests.
Before using Free for a public product, check how Screenshotlayer defines commercial use and whether your organization or customer work qualifies. Do not assume that a free API key can be used in a paid SaaS, client reporting tool or internal business workflow.
Basic: 10,000 snapshots for $19.99
Basic is the advertised commercial starting point. It includes 10,000 snapshots per month, 10 dedicated workers, Retina/2x output and WebP support. At the listed price, the simple allowance calculation is about $2 per 1,000 snapshots, assuming you consume the full allowance and do not incur another charge.
Basic fits a moderate automation workload: scheduled page monitoring, a documentation preview service, or an application generating screenshots for a few thousand pages each month. Check concurrency behavior in your account before sending large bursts. “Dedicated workers” describes the published plan feature; it does not, by itself, establish a guaranteed requests-per-minute rate.
Professional: 30,000 snapshots for $59.99
Professional raises the allowance to 30,000 snapshots and lists 20 dedicated workers. It also lists Retina/2x, WebP, and FTP/S3 export options. The advertised effective price is about $2 per 1,000 snapshots when the allowance is fully used, the same simple ratio as Basic.
This tier is more appropriate when screenshots feed a larger catalog, visual regression process or reporting pipeline. Export options may reduce application-side transfer work, but confirm supported destinations, credentials, retention and failure behavior in the current documentation.
Enterprise: 75,000 snapshots for $149.99
Enterprise lists 75,000 snapshots per month and 40 dedicated workers, plus Retina/2x, WebP and FTP/S3 export options. Its advertised allowance works out to about $2 per 1,000 snapshots. The higher worker count is relevant to bursty workloads, but the published material does not define a universal rate limit, queue guarantee or uptime commitment.
If you need more than 75,000 captures, ask the provider how overages, custom quotas, concurrency, support and data handling are contracted. Do not infer those terms from the public tier table.
Screenshotlayer limits developers should check
Monthly allowance and exhaustion
The API specification identifies usage_limit_reached as the error returned when a subscription’s monthly request allowance has been reached or exceeded. Treat the allowance as a hard operational boundary unless your contract says otherwise. Track usage before the final few percent, reserve capacity for retries, and expose a clear fallback when the quota is exhausted.
No verified requests-per-minute number
The reviewed specification does not establish a general account rate limit. Avoid designing around an unverified number such as 60 or 1,000 requests per minute. Instead, measure the behavior of your account, use bounded concurrency, and ask support for documented limits if you need predictable burst capacity.
Capture controls
The API specification lists an access key and target URL as required inputs. Optional controls include full-page capture, width, viewport, output format, custom CSS, capture delay, cache TTL, forced refresh, placeholder, user-agent and language headers, and export. The documented default cache TTL is 2,592,000 seconds, or 30 days.
A 30-day default cache can be useful for stable pages, but it can surprise you during visual QA. Decide whether a screenshot represents the current page or a cached representation. Use the documented forced-refresh option when freshness matters, and choose a shorter TTL for frequently changing content.
How to calculate the plan you actually need
- Count successful captures. Start with the number of URLs and how often each URL is captured.
- Add retries. Include retry attempts for timeouts, transient network errors and downstream storage failures.
- Add development traffic. Preview pages, CI runs and manual checks can consume a surprising share of a monthly quota.
- Measure peak concurrency. A monthly count does not tell you whether a five-minute burst will queue or fail.
- Check commercial rights. Confirm that the plan’s use terms match your application and customers.
- Leave headroom. A 20% to 30% reserve helps absorb launches, reprocessing and retries.
For example, 2,000 URLs captured weekly produce about 8,000 captures per month before retries. With a 25% reserve, plan for 10,000 or more. That points to Basic by allowance, but you still need to validate worker capacity, export requirements and commercial terms.
Runnable screenshot request with ScreenshotNeo
If you want to compare a second provider using the same workload, run the following request against ScreenshotNeo. The API returns an image response; save it as a file and inspect the response headers for the page verdict and billing result. See the ScreenshotNeo documentation for the current parameter reference.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-o shot.webpPython
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(`HTTP ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', data);Or skip the browser setup
ScreenshotNeo handles the browser work behind one GET request. Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and whether the request was billed.
It also provides an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. Plans include full-page capture with lazy images loaded, element capture by CSS selector, dark mode, device presets, custom CSS and JavaScript, waits, blocking rules, headers, cookies, geolocation, PDF controls, signed links, asynchronous jobs, bulk capture and a usage API.
There is a free allowance of 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.
How to compare Screenshotlayer with cheaper alternatives
A lower sticker price is not enough to prove savings. Compare providers at the same successful-capture volume and include the controls your application actually uses.
| Axis | Questions to answer |
|---|---|
| Price | What does the plan cost at your monthly volume? Are overages allowed or blocked? |
| Allowance | Are snapshots, requests or successful captures counted? |
| Commercial use | Is production and client work permitted on the selected tier? |
| Rendering | Are full-page, viewport, element, Retina and WebP outputs available? |
| Freshness | What is the default cache TTL? Can you force refresh? |
| Workflow | Are FTP, S3, webhooks, bulk jobs or signed links supported? |
| Reliability | What happens on timeouts, bot checks, blank pages and failed loads? |
| Capacity | What concurrency and queue behavior are documented for your account? |
A dated comparison article lists GetScreenshot, ScreenshotOne, Urlbox and CaptureKit alongside Screenshotlayer. Use that source for discovery only. Verify each alternative’s current official plan page before describing it as cheaper, because prices, free allowances and included features can change.
Troubleshooting Screenshotlayer billing and capture issues
usage_limit_reached
Cause: The account has reached or exceeded its monthly allowance. Fix: stop automatic retries, inspect usage, wait for the next billing period or move to a plan with sufficient capacity. Add an alert before exhaustion.
Unexpectedly old screenshots
Cause: The documented default cache TTL is 30 days. Fix: use the cache controls and forced-refresh option when you need current content, and record the cache policy with each job.
Commercial-use uncertainty
Cause: The Free tier is marked non-commercial. Fix: review the current terms and use a paid tier or obtain written clarification before shipping customer-facing functionality.
Slow or bursty processing
Cause: Monthly allowance and worker count do not define a universal requests-per-minute guarantee. Fix: limit concurrency, queue jobs, use exponential backoff for transient failures and ask the provider for account-specific capacity.
Different output than expected
Cause: Viewport, width, full-page mode, delay, user-agent, language or custom CSS changes rendering. Fix: make those parameters explicit, keep a reproducible capture profile and compare images only after normalizing the profile.
Performance, reliability and cost practices
- Cache your own completed results when the source page has not changed.
- Use a queue so a temporary provider failure does not trigger a retry storm.
- Retry only transient errors; do not retry quota exhaustion without changing capacity.
- Store request parameters and response status with every image for auditability.
- Separate preview traffic from production traffic so testing cannot consume the entire monthly allowance.
- Use WebP where downstream systems support it to reduce storage and transfer size.
- Measure successful captures, failed captures, latency and billed requests separately.
- Budget for headroom rather than selecting a tier whose allowance exactly matches your average.
FAQ
Is Screenshotlayer Free suitable for a paid SaaS?
The public page labels Free for non-commercial use. Confirm the current terms before using it in a paid product; do not assume the free tier permits commercial workloads.
Does Screenshotlayer publish a general rate limit?
The reviewed API specification does not establish a general requests-per-minute limit. Use bounded concurrency and request account-specific guidance for burst workloads.
What is the documented cache TTL?
The specification documents a default TTL of 2,592,000 seconds, which is 30 days. Use the cache controls or forced refresh when freshness is required.
Which Screenshotlayer plan is the cheapest commercial entry?
Basic is the advertised commercial starting plan at $19.99 per month for 10,000 snapshots.
Why consider ScreenshotNeo?
ScreenshotNeo offers 1,000 free shots monthly with no card, paid plans from $5 for 3,000, consent and popup cleanup, billing only for clean shots, and an MCP server for AI agents. Start with the free account and compare it against your measured workload.
