What it does
ScreenshotOne is a hosted browser-rendering API that returns screenshots and other requested output, not a local API-testing client. Applications send a URL and rendering options to its `/take` endpoint, then receive binary image data or another configured format. The service supports full-page captures, viewport choices, and controls for page appearance, while its provider operates the browser infrastructure. It is useful for generating preview images, report captures, or visual assets from a web page without managing a browser fleet.
Request a capture and use the response
The getting-started docs show a first GET request to https://api.screenshotone.com/take with a target URL and access key. The API also accepts POST requests with JSON options in the body. Choose HTTPS, supply the key using a documented method such as the X-Access-Key header, and specify the output options your application needs. The response is binary data with a content type matching the requested format, so a server can save it as an image or pass it to another part of a rendering pipeline.
A realistic example is an application creating a preview card for a user-submitted public page. Set the page URL, viewport, and image format, then store the returned bytes with the card. The product site documents full-page screenshots and customization such as dark mode, hiding page elements, and blocking common ads or cookie banners. These capabilities are described by the vendor; no target page was submitted for this record.
Keep keys and request size in mind
An account and API key are required to start. The documentation warns that plain HTTP does not encrypt keys, headers, cookies, or other sensitive request data, and says to use HTTPS. Although the key can be supplied in more than one request location, the X-Access-Key header keeps the key out of the URL.
The pricing page lists 100 screenshots per month at no charge and paid subscription tiers. The free allowance is suited to a small integration check, while expected request volume and extra usage should be reviewed before scaling. POST request bodies are limited to 100 MiB; for larger HTML or Markdown input, the docs recommend hosting the content and passing its URL instead.
Strengths
- Returns rendered image data from a single HTTP API request, without requiring the application to operate its own browser fleet.
- The documented options include full-page capture and adjustments to viewport and page appearance.
- A free monthly screenshot allowance is available for an initial integration.
Watch out for
- A POST request body cannot exceed 100 MiB; larger HTML or Markdown must be hosted separately and referenced by URL.
- Requests require an account key, which should be sent over HTTPS and kept out of public client code.
Best for
- Generating page previews and visual assets in a backend workflow
- Capturing full-page or customized renderings without maintaining browser infrastructure
- Producing screenshot output for reports or visual review processes
Sources
- Website Screenshot API for Developers and AI Agents - ScreenshotOne (Oct 25, 2026)
- Getting Started | ScreenshotOne Docs (Oct 25, 2026)
- Website Screenshot API Pricing and Plans - ScreenshotOne (Oct 25, 2026)