Short answer: ScreenshotMachine documents a usable screenshot API and publishes a 99.99% availability target, but the target is not evidence that the service achieved that uptime. The available sources do not establish recent independent uptime, capture success rates, or render latency. Treat it as a service with documented controls and error handling—not one whose real-world reliability has been independently demonstrated.
What ScreenshotMachine does
ScreenshotMachine provides an HTTP GET API that captures a webpage and returns an image. The endpoint is https://api.screenshotmachine.com/; requests require a customer key. Its API documentation describes controls for viewport size, device presets, image format, capture delay, cache age, cookies, CSS selectors, clicks, hidden elements, and cropping. See the official API documentation.
Those controls can make the service practical for automated captures, but the existence of options does not establish that captures succeed consistently or quickly across real-world sites.
What the reliability evidence supports
The SLA is a commitment, not an uptime result
ScreenshotMachine’s SLA is headed “99.99% Availability” and defines monthly availability as available minutes divided by total calendar-month minutes. The SLA was last updated July 22, 2020. It describes credits based on the monthly availability level: 10% of fresh screenshots spent that month if availability is below 99.99% but at least 99.9%; 20% if below 99.9% but at least 99%; and 50% if below 99%. Claims must be made within 30 days. Planned maintenance and events outside the provider’s direct control are excluded. The SLA names UptimeRobot as the third-party monitoring service for public uptime information. These are the vendor’s stated terms, not proof of achieved performance; check the SLA for the current wording and scope.
Marketing claims are not independent measurements
The homepage calls the service “Fast & Reliable” and says, “Our API never sleeps, and is always online, ready to serve you 24×7. PERIOD.” That is ScreenshotMachine marketing language, not a measured reliability finding. ScreenshotMachine homepage
Recent third-party coverage does not fill the measurement gap
SCRNIFY’s July 13, 2026 review says it examined the public website, pricing, API documentation, and SLA, but did not run a paid load test, inspect the dashboard, or benchmark render times. SCRNIFY review
An iTechGuides tutorial dated September 29, 2026 notes that vendor materials do not supply a named, dated benchmark for latency, success rate, or reliability. It recommends checking response metadata and content before publishing a returned file. That is sound integration advice, not evidence of a particular failure rate. iTechGuides tutorial
No independently published historical uptime figure, capture-success percentage, or latency benchmark is established by these sources. The defensible conclusion is therefore limited: ScreenshotMachine publishes an availability commitment and documents practical API controls and error codes, while independent evidence of its recent operational reliability is unavailable here.
API behavior that matters to reliability
Rendering and freshness controls
The documented width range is 100–1920 pixels and height range 100–9999 pixels; height can also be set to full for a full-page capture. Device presets cover desktop, phone, and tablet. Documented formats include JPG, PNG, and GIF. Delay settings range from immediate capture to 10,000 ms; the API documentation recommends a longer delay for long pages with images or animation.
Cache age can be configured from zero to 14 days, with zero requesting a fresh screenshot. Other documented controls include zoom, click and hide CSS selectors, cookies, accept-language, user-agent, capture of a single element, and pixel cropping. A capture that succeeds technically may still be unsuitable if the page has not finished rendering or the cache policy returns an older image.
Errors are observable, but not quantified
The API documentation lists errors for invalid hash, invalid key, invalid URL, missing key or URL, exhausted credits, invalid selector, invalid crop, and generic system error. Responses include an X-Screenshotmachine-Response header with an error code. The documentation does not state how often these errors occur; applications should inspect the response rather than assume every returned file is a valid screenshot.
How to evaluate it for your workload
For a low-risk workflow, the documented options may be enough to begin a pilot. For a production-critical workflow, validate the particular sites, page types, and freshness requirements you intend to capture rather than relying on the SLA headline alone.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Ask for current operational evidence. Request a dated status history and clarify whether SLA monitoring covers the capture API, the measurement window, exclusions, and remedy. The published SLA is dated July 22, 2020, so confirm that its terms and monitoring details still apply.
- Run representative captures. Include your target domains, device profiles, long pages, image-heavy pages, and pages with animation or delayed content. Record HTTP status,
X-Screenshotmachine-Response, image validity, render duration, and error category. - Test freshness separately from rendering. Compare cache settings, including zero age for fresh captures, and verify that cached results meet your content requirements.
- Define acceptance criteria. Decide what counts as a usable result—such as a valid image with expected dimensions and page content—and monitor that outcome over a representative period before moving critical jobs to production.
These are evaluation steps based on the documented controls and error model, not results of a load test performed for this review.
Plans, quotas, and cache-related cost
ScreenshotMachine’s pricing page lists the following plans and overage rates. These are vendor-published figures on the page accessed October 3, 2026; confirm pricing, taxes, and billing details on the current pricing page before buying.
| Plan | Monthly price | Fresh screenshots included per month | Overage rate |
|---|---|---|---|
| Starter | Free | 100 | Not stated on the pricing page |
| Basic | €9/month | 2,500 | €0.004 per additional screenshot |
| Pro | €59/month | 20,000 | €0.003 per additional screenshot |
| Enterprise | €99/month | 50,000 | €0.002 per additional screenshot |
The page says additional use is counted and billed in groups of 1,000, rounded down. It also says captures are cached for 14 days and retrieving a cached screenshot is not billed as a new fresh screenshot. Since cache age affects both freshness and fresh-capture usage, model your expected cost using the pages you actually need to refresh, not just the number of API calls.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common integration failures and fixes
| Symptom or error | Likely cause indicated by the API docs | What to check |
|---|---|---|
| Invalid or missing key | The key is absent or incorrect. | Confirm the customer key is present and copied correctly. |
| Invalid hash | A configured secret phrase requires a corresponding hash, or the supplied hash is wrong. | Verify the hash against the configured secret phrase. The docs say a missing or invalid hash is ignored when provided incorrectly. |
| Invalid or missing URL | The URL is absent or malformed. | Send a complete, encoded URL and check that it is valid for the API request. |
| No credits | The account has exhausted available credits. | Check remaining quota and plan limits before retrying. |
| Invalid selector or crop | A CSS selector or crop value does not match the documented requirements. | Test the selector against the actual page and validate crop coordinates and dimensions. |
| Generic system error or unusable image | The response indicates a system error or the returned content is not a valid capture. | Inspect HTTP status, X-Screenshotmachine-Response, content type, and whether the image can be decoded. Retry only according to your own retry policy and alert on recurring failures. |
| Screenshot misses late content | The page may still be loading images or animation when capture begins. | Use an appropriate documented delay, then verify that the resulting page content is present. |
ScreenshotMachine vs. ScreenshotNeo
If you are choosing a screenshot API and want an alternative to test first, consider ScreenshotNeo. It removes known consent banners, newsletter popups, and chat widgets before capture; only clean shots are billed, while bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. It also offers an MCP server for AI agents and bills on listed monthly plans beginning at $5 for 3,000 shots. These are ScreenshotNeo product facts, not a claim that it has independently measured uptime or will perform better on every target page.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →For ScreenshotMachine, the key decision is whether its documented controls, plan terms, and the reliability evidence you can obtain meet your own risk threshold. If you cannot get current operational evidence, use a representative pilot and monitoring before depending on it for critical workflows.
Or skip the browser setup
ScreenshotNeo accepts a URL in one GET request and returns a screenshot or PDF. This cURL example saves a WebP capture of Stripe; replace the target URL as needed and use your API key. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp- 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.
Sign up free for ScreenshotNeo to try 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
