ScreenshotMachine API pricing: how many website screenshots do the plans include?
ScreenshotMachine lists 100 to 50,000 fresh screenshots a month across four plans. See the prices, cache rules, overage billing, and how to estimate usage.
Direct answer: ScreenshotMachine lists four monthly plans: Starter is free for 100 fresh screenshots; Basic costs €9 for 2,500; Pro costs €59 for 20,000; and Enterprise costs €99 for 50,000. These allowances count fresh screenshots. ScreenshotMachine says repeat requests served from cache are not billed as fresh captures, so the number of API calls can be higher than the fresh-capture allowance.
| Plan | Monthly price listed | Fresh screenshots included | Listed overage rate | Support listed |
|---|---|---|---|---|
| Starter | Free | 100 | No rate listed | Basic |
| Basic | €9 | 2,500 | €0.004 per additional screenshot | Priority |
| Pro | €59 | 20,000 | €0.003 per additional screenshot | Priority |
| Enterprise | €99 | 50,000 | €0.002 per additional screenshot | Priority |
These are figures displayed on ScreenshotMachine’s official pricing page, checked October 3, 2026. The page does not show a publication date, and plan details can change; confirm current prices and terms before purchasing.
How to estimate how many fresh screenshots you need
Count distinct page captures that need to be newly rendered during one billing month. A request for a URL and capture settings that can be served from cache may not consume a fresh screenshot, while changed content or settings may require a new capture. ScreenshotMachine says its pricing cache lasts 14 days; its API documentation describes cacheLimit from 0 to 14 days, with 0 requesting a fresh capture and 14 as the default.
- Estimate unique URL-and-settings combinations that require a new image each month.
- Subtract repeat requests likely to be served from cache. Treat this as an estimate; cache behavior depends on the request and freshness you require.
- Compare the remaining fresh captures with the plan allowance.
- Allow headroom for retries, changed pages, and recurring jobs that run more often than the cache period.
For example, if a job requests the same page and settings daily, do not automatically count 30 fresh captures: the vendor says cached repeats are not billed, and documents a default cache age of 14 days. If the workflow requires a fresh render every time, set cacheLimit=0 and budget each run as a fresh capture.
How overage billing works
ScreenshotMachine says extra screenshots are counted at the end of the billing period and billed in groups of 1,000, rounded down. Its example says up to 999 additional screenshots incur no extra charge, while 1,999 are billed as 1,000. The published marginal rates apply to Basic, Pro, and Enterprise; the pricing content retrieved does not list a Starter overage rate.
| Plan | Listed rate per extra fresh screenshot | Cost for 1,000 billed extra screenshots at listed rate |
|---|---|---|
| Basic | €0.004 | €4 |
| Pro | €0.003 | €3 |
| Enterprise | €0.002 | €2 |
The final column is arithmetic from the listed per-screenshot rates; actual billed quantities follow the vendor’s 1,000-unit rounding rule. For example, on Basic, 1,500 extra fresh screenshots would be billed as 1,000 under the described rule, or €4 at the displayed rate. Confirm how the vendor applies the rule to your account and current terms.
The vendor says VAT may be added for non-business customers in the EU depending on the customer’s country tax rules. Its pricing page also advertises a 30-day money-back guarantee; check the current terms directly before relying on it.
ScreenshotMachine API request basics
The official API documentation describes HTTP GET requests with a customer key and target URL. Optional settings include dimensions, device, output format, cache age, delay, zoom, and a CSS selector to click before capture. Documented output formats are JPG, PNG, and GIF; device presets are desktop, phone, and tablet. Widths are documented from 100 to 1,920 pixels, heights from 100 to 9,999 pixels, and full is accepted for full-length screenshots. The documentation’s examples include a 1024xfull capture.
Use your account’s actual key and encode the target URL as a query parameter. This shell example shows the general GET shape; check the current API page for exact parameter names and key format before use:
curl -G 'https://api.screenshotmachine.com' \
--data-urlencode 'key=YOUR_SCREENSHOTMACHINE_KEY' \
--data-urlencode 'url=https://example.com' \
--data-urlencode 'dimension=1024xfull' \
--data-urlencode 'format=png' \
--data-urlencode 'cacheLimit=14' \
--output screenshot.pngThe host and parameter spelling above illustrate the documented request pattern; use the endpoint and exact parameter names shown in ScreenshotMachine’s current documentation for your account. Protect the key as a secret and avoid putting it in browser-side code.
Options that affect usage and output
| Control | What it changes | Usage consideration |
|---|---|---|
| Dimensions | Viewport width and height; full can request full page height |
Larger or full-page captures may take longer to render and return. |
| Device | Desktop, phone, or tablet capture profile | Use consistent settings when comparing cached results. |
| Format | JPG, PNG, or GIF according to the documentation | Choose an output compatible with your downstream system. |
cacheLimit |
Cache age from 0 through 14 days; 0 requests a fresh capture | Longer cache reuse can reduce fresh-capture consumption when the content need not be current. |
| Delay | Wait before capture for animation or late-loading content | Use a targeted delay only when needed; longer waits increase latency. |
| Zoom | Adjusts page zoom for the capture | Check layout and text legibility at the chosen value. |
| Click selector | Clicks a CSS-selected page element before capture | Useful for opening a menu or dismissing a page state; selectors can break when a site changes. |
The documented page lists these controls; it does not establish a request-per-minute limit or guarantee that every site will render identically. Do not infer either from the plan table.
Capacity, reliability, and cost planning
- Budget fresh renders, not raw requests. Separate likely cache hits from captures that must be fresh. Monitor actual monthly consumption in the account.
- Use cache deliberately. If a page changes infrequently, allowing cache reuse can reduce fresh capture use. For time-sensitive pages, choose a shorter cache age or zero and budget accordingly.
- Keep room for retries. Failed network or page loads may lead your own integration to retry. Use bounded retries with backoff to avoid making an incident into a burst of duplicate calls.
- Measure end-to-end latency. Full-page pages, late-loading content, and deliberate delay can make a capture slower. Set client timeouts appropriate to your workload and handle errors explicitly.
- Check vendor claims in context. ScreenshotMachine’s pricing page lists full-length captures, custom error images, unlimited cached impressions, unlimited traffic, and a 99.99% uptime SLA across plans. These are vendor-stated terms; review the current plan and service terms for the definition and applicability of the SLA.
- Recheck currency and tax. Prices here are listed in euros. EU VAT may apply to non-business customers according to local rules.
Common pricing and API questions
Do cached screenshots count toward the monthly allowance?
ScreenshotMachine says only new, fresh screenshots are charged and cached screenshot loads are not billed as fresh captures. Its pricing page describes a 14-day cache, while the API documentation exposes the cacheLimit setting.
Is Starter overage priced?
The pricing content retrieved lists no Starter overage rate. Do not assume it is the same as a paid tier; check the current pricing page or account terms.
Can I request a full-page screenshot?
The API documentation accepts full as the height, with 1024xfull shown as an example.
Is there a published request-per-minute limit?
No request-per-minute limit appears in the retrieved pricing and API material. Ask ScreenshotMachine or check the current account documentation for applicable limits.
Or skip the browser setup
If your goal is simply to get a clean screenshot from a URL, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Make one GET request; the API returns an image or PDF. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.
