Skip to main content
ScreenshotAPI renders a URL in a browser and returns a downloadable capture with metadata. Use it for website previews, reporting, visual monitoring, or tools that need to inspect a web page. You choose the viewport, output format, page readiness rules, and content controls. The REST API handles queued execution and returns either the finished capture or a job you can track.

Make your first capture

Create an API key, submit a URL, and download the result.

Understand the response

Handle finished captures, accepted jobs, and structured errors.

Capture a full page

Configure scrolling, resolution, and capture diagnostics.

Run captures in the background

Track queued work without holding an HTTP connection open.

​
Choose your integration

The hosted REST API base URL is https://api.screenshotapi.tech. The examples include this address directly; only SCREENSHOTAPI_API_KEY needs your private value. The documentation domain is a separate site and does not accept capture requests.

​
What to expect

  • Image formats are PNG, JPEG, and WebP. PDF captures preserve the rendered appearance of the page.
  • A successful capture includes dimensions, byte size, final URL, timing, and an artifact URL.
  • A request can remain queued after the HTTP response. Treat 202 Accepted as a job handle and wait for its terminal result.
  • Failed captures release their reserved credits. Credit cost depends on the requested output.
  • Public API captures require public network destinations. Target access restrictions and bot challenges can still prevent a capture.
Continue with the quickstart, then add idempotency and webhooks when your workflow needs reliable background execution. For AI workflows, connect the hosted MCP service or request page text with your capture. You can grant a dedicated integration only the permissions it needs.