ScreenshotOne Pricing: How Much Do Website Screenshot API Plans Cost?

Direct answer: ScreenshotOne lists 100 free screenshots per month, then three monthly paid plans: Basic at $17 for 2,000 screenshots, Growth at $79 for 10,000, and Scale at $259 for 50,000. Paid plans allow 40, 80, and 150 requests per minute, respectively. Displayed prices exclude VAT. Annual billing advertises two months free; confirm the actual billed amount in checkout. These details were checked on October 3, 2026, and can change. Check ScreenshotOne’s live pricing page before subscribing. [Sources: pricing]

Plan	Monthly price	Included screenshots/month	Requests/minute	Extra usage rate
Free	$0	100	Not listed in the reviewed pricing data	Not listed
Basic	$17	2,000	40	$0.009 per extra screenshot
Growth	$79	10,000	80	$0.006 per extra screenshot
Scale	$259	50,000	150	$0.004 per extra screenshot

How to estimate your monthly ScreenshotOne cost

Estimate from successful, uncached outputs rather than raw requests. ScreenshotOne describes usage in credits and currently charges one credit for each available output, including a full-page or scrolling screenshot, PDF, or video. A cached response does not count; a cache miss that renders a fresh output can count. Failed HTTP, browser, or network requests do not count, while a successfully rendered screenshot can count even if its visual result is wrong. [Sources: credits documentation, pricing FAQ]

Count expected successful, uncached outputs in a typical month. Include PDFs and videos in the same output estimate.
Compare the estimate with the included monthly allowance: 2,000 on Basic, 10,000 on Growth, or 50,000 on Scale.
If you may exceed that allowance, check whether extra usage is enabled and what hard limit is configured.
Check your peak request rate against the plan limit, separately from your monthly volume.
For annual billing, verify the checkout total and remember that credits still reset monthly and unused credits expire.

For a rough paid-plan estimate, the listed overage is the number of billable extra outputs multiplied by the plan’s extra-use rate, subject to the configured hard limit. For example, 500 extra Basic outputs at the listed rate would be $4.50 in extra usage. Treat this as arithmetic from the listed rate, not a quote for taxes or any other account-specific charges.

What each ScreenshotOne plan includes

Free

The pricing page lists 100 screenshots per month at no charge. The reviewed data does not establish a free-tier request-per-minute limit or overage rate, so check the live plan details for those terms.

Basic

Basic costs $17 per month for 2,000 screenshots, with a limit of 40 requests per minute and listed extra usage of $0.009 per screenshot. The pricing page describes core screenshot and PDF features as included.

Growth

Growth costs $79 per month for 10,000 screenshots, allows 80 requests per minute, and lists extra usage at $0.006 per screenshot. It adds choosing an IP location, scrolling screenshots, and video generation. The pricing page labels it “Recommended”; that label is the vendor’s, and does not determine the best fit for your workload.

Scale

Scale costs $259 per month for 50,000 screenshots, allows 150 requests per minute, and lists extra usage at $0.004 per screenshot. It adds GPU rendering and priority support.

The lower per-output overage rate on larger plans does not automatically make them cheaper. Compare your expected total monthly usage, peak request rate, and required features with the plan allowance and base price.

Credits, caching, overages, and annual billing

Credits reset monthly: ScreenshotOne says credits reset each month, including for annual subscribers, and unused credits expire at the end of the cycle. They do not roll over. [Source: How credits work]
One credit per available output: The documented unit applies to each available screenshot, PDF, or video output. [Source: How credits work]
Extra usage is off by default: A paid-plan owner or admin can raise the monthly hard limit in Billing. Successful uncached requests can incur the listed extra-use charge after included credits are used, until that hard limit is reached. [Source: Charging Extra]
Documented maximum hard limits: Basic: 50,000; Growth: 200,000; Scale: 1,000,000 screenshots per month. These are maximum limits, not included allowances. [Source: Charging Extra]
Annual billing: The pricing page advertises two months free. Displayed prices exclude VAT; confirm the actual annual total during checkout rather than multiplying a monthly figure by ten. [Source: pricing]

Choosing a plan by workload

Your workload	What to compare	Likely starting point
Occasional development or a small prototype	Whether 100 monthly free outputs cover the successful uncached renders you need	Free
Up to roughly 2,000 outputs monthly	Basic’s 40 requests/minute and whether its core screenshot/PDF features suffice	Basic
More volume or Growth-only features	10,000 included outputs, 80 requests/minute, IP location, scrolling screenshots, and video	Growth
High monthly volume or need for GPU rendering	50,000 included outputs, 150 requests/minute, GPU rendering, and priority support	Scale

These are starting points based on the listed allowances and features, not guarantees that a plan will meet a particular application’s latency or throughput needs. If your traffic is bursty, request-per-minute limits may matter before you exhaust monthly credits.

Common pricing and usage surprises

“I made fewer requests than my credit count.” One request can produce an available output that consumes a credit. Count outputs and account for the documented billing rules, not only application-level calls.
“My successful capture still used a credit, but it looks wrong.” A successfully rendered screenshot with a visual problem can count. Validate the target page, viewport, timing, and output before scaling a workflow. [Source: pricing FAQ]
“My failed calls did not reduce usage.” The pricing FAQ says HTTP, browser, and network errors do not count. Cached responses also do not count; a cache miss can render anew and count. [Source: pricing FAQ]
“I expected overages but usage stopped.” Extra usage is off by default and subject to a configured hard limit. An owner or admin must adjust the limit in Billing. [Source: Charging Extra]
“My annual subscription has no credits left.” Annual payment does not mean all annual credits arrive at once: credits reset monthly and unused credits expire each cycle. [Source: How credits work]
“The checkout total is above the table price.” Listed prices exclude VAT. Check the checkout for the applicable total and billing period. [Source: pricing]

Cost control and reliability checklist

Estimate successful uncached outputs from representative production traffic.
Use caching where repeated captures can reuse results, and distinguish cache hits from misses in your usage expectations.
Set an intentional hard limit before enabling extra usage; the limit caps the monthly overage exposure.
Rate-limit or queue bursts to stay within the plan’s requests-per-minute allowance.
Monitor visual correctness as well as HTTP success: a visually incorrect successful render may still consume a credit.
Revisit the estimate when adding PDFs, videos, scrolling captures, or other output-producing work.
Verify the live pricing and billing documentation before committing, since prices and terms can change.

The available research establishes listed prices and usage rules, but not comparative rendering speed, uptime, or a performance benchmark. Do not choose a plan based on an assumed speed advantage; validate your own target pages and traffic pattern.

ScreenshotOne alternative: ScreenshotNeo

If you are comparing screenshot APIs, put ScreenshotNeo first to evaluate: it removes cookie banners, newsletter popups, and chat widgets before capture, bills only clean shots, and its lowest paid plan is $5 for 3,000 shots. It also offers 1,000 free shots monthly with no card. All features are available on every plan; confirm current terms on its site.

Or skip the browser setup

Make one GET request for an image capture. See the ScreenshotNeo API docs for options 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}`);

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 take screenshots.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

FAQ

Does ScreenshotOne’s free plan require a card?

The reviewed pricing data establishes 100 free screenshots per month but does not establish the card requirement. Check the live sign-up terms.

Do unused ScreenshotOne credits roll over?

No. Credits reset monthly and unused credits expire at the end of the cycle, including with annual billing.

Are failed requests billed?

The pricing FAQ says HTTP, browser, and network errors do not count. A successful uncached render can count even when its visual result is not what you wanted.

What is the cheapest ScreenshotOne paid plan?

Basic is listed at $17 per month for 2,000 screenshots. Displayed prices exclude VAT; check the live page for current terms.

Is ScreenshotOne Growth always the right choice?

No. It is labeled “Recommended” on the pricing page, but fit depends on volume, request rate, and whether you need its listed features.