REST API · Chromium rendering · Optional AI vision

Website screenshot API built for automation

Turn any public URL into a browser-accurate image with one POST request. Poll, webhook, or download when rendering finishes—then optionally run AI vision on the result.

Get API access View endpoints

Output formats

PNG, JPG, WEBP

3 presets

Devices

desktop, iPhone 15, iPad

1–2

Credits

1 standard · 2 with AI vision

Live capture request

https://screenshotor.com/api/v1/screenshot

URL accepted

https://example.com

Screenshot rendered

1440 x 900 webp

AI screenshot summary

Pricing and page state extracted

POST /api/v1/screenshot
{
  "url": "https://example.com",
  "format": "webp",
  "fullPage": true,
  "aiVision": true,
  "webhookUrl": "https://app.example/hook"
}

REST JSON

Webhooks

AI vision

Capture completed

AI summary stored

Webhook delivered

API surface

Core Screenshotor API endpoints

Create a screenshot, poll status, download the asset, list recent jobs, and read usage from a small, predictable endpoint set.

Get your API key Read API docs

POSTX-Api-Key

/v1/screenshot

Create a screenshot job. Returns 202 for queued jobs, 200 for cache hits or sync captures.

GETX-Api-Key

/v1/screenshot/{id}

Read job status and metadata for one screenshot owned by the API key user.

GETX-Api-Key

/v1/screenshot/{id}/download

Create or return the public temporary download URL for a completed screenshot.

GETX-Api-Key

/v1/screenshots?limit=20&offset=0

List recent screenshots for the authenticated user.

GETX-Api-Key

/v1/usage

Read monthly usage, quota, remaining captures, and daily breakdown.

Use cases

Screenshot API use cases

Teams use Screenshotor when they need reliable browser rendering without operating Chromium infrastructure—monitoring, QA, AI extraction, and internal tooling.

Uptime and visual monitoring

Schedule captures of dashboards, status pages, and checkout flows. Compare renders over time or alert when a page no longer matches expectations.

QA, staging, and release checks

Snapshot staging builds with fixed viewport, device presets, and cookie-banner handling so QA reviews reflect what real users see.

AI screenshot analysis

Send a prompt with aiVision to summarize pricing tables, classify page state, or extract visible text from the finished PNG, JPG, or WEBP capture.

Reports, CRMs, and internal tools

Attach fresh thumbnails to tickets, client reports, or admin panels without running your own headless browser fleet.

Workflow

How the screen capture API works

Submit, validate, render, and deliver finished screenshot assets through a queue-friendly automation flow.

Open dashboard

Request

Send a URL with viewport, device, output format, banner blocking, and AI screenshot options.

Validate

DNS and network checks protect the browser before a website screenshot job begins.

Render

A pooled Chromium worker captures the page as an image with repeatable settings.

Deliver

Poll for status or receive a webhook, then use the returned download URL in your app.

Competitor articles

Compare Screenshotor with other screenshot APIs

Published comparison pages cover integration style, automation fit, webhooks, capture delivery, and AI screenshot workflows.

View all comparisons

Screenshotor vs ScreenshotOne

Hosted screenshot rendering platform with a broad option surface, signed public links, PDF rendering, webhooks, S3 upload, HTML rendering, caching, and stealth-related controls.

Read article

Screenshotor vs Screenshotlayer

APILayer screenshot API with URL-parameter captures, full-height screenshots, viewport controls, TTL caching, CDN delivery, WebP, Retina/2x support, and S3/FTP export on higher plans.

Read article

Screenshotor vs ScreenshotAPI

Screenshot automation API advertising full-page captures, PDF/video/GIF output, bulk and scheduled screenshots, cookie/ad blocking, authenticated pages, BYOB storage, no-code integrations, and text/HTML extraction.

Read article

Screenshotor vs Screenshot Machine

Website screenshot and web-to-PDF API with transparent fresh-screenshot pricing, cached impressions, custom error images, full-length captures, and JPG/PNG/GIF image output.

Read article

Screenshotor vs Screenshotbase

Real-time screenshot JSON REST API with SDKs, responsive/full-page/element captures, custom CSS/JavaScript, cookies and headers, custom proxies, S3 upload, webhooks, and managed-service positioning.

Read article

Screenshotor vs Thum.io

Real-time website snapshot API built around embeddable image URLs, streaming/animated initial renders, high-volume screenshot hits, mobile emulation, and thumbnail-style delivery.

Read article

Production ready

Screenshotor features without browser fleet maintenance

From one-off website screenshots to recurring site screenshot API jobs, Screenshotor keeps capture, storage, and AI processing predictable.

One screenshot API endpoint for viewport, full-page, and mobile captures
PNG, JPG, and WEBP output for screen capture API workflows
SSRF-aware URL validation before the browser reaches the target site
Cookies, dark mode, banner handling, custom user agents, and device presets
Webhook callbacks, polling, usage tracking, and direct download URLs
Optional AI screenshot prompts powered by OpenRouter vision models

Free

100 credits

Test Screenshotor and ship a small proof of concept.

Select

Starter

2,500 credits

For internal tools, QA tasks, and lightweight automations.

Select

Pro

$29

10,000 credits

For recurring screen capture API usage across product teams.

Select

Scale

$99

50,000 credits

For high-volume site screenshot API jobs with predictable pricing.

Select

FAQ

Screenshotor API FAQ

Answers about credits, formats, webhooks, banner blocking, and how Screenshotor compares to other screenshot APIs.

What is a website screenshot API?

A website screenshot API accepts a URL and returns a rendered image of the page. Screenshotor uses Chromium, so JavaScript, modern CSS, and client-side layouts are included in the capture—not just static HTML.

How do credits and pricing work?

Standard captures use 1 credit; captures with AI vision enabled use 2 credits. Public plans include 100 free credits, then Starter ($9 / 2,500), Pro ($29 / 10,000), and Scale ($99 / 50,000) per month.

Can I capture full-page and mobile screenshots?

Yes. Set fullPage for scroll captures, pick desktop/iPhone/iPad presets, or set custom width and height between 100 and 5000 pixels. Output formats are PNG, JPG, and WEBP.

Do you support webhooks and async jobs?

Yes. POST /v1/screenshot can queue work; send webhookUrl to receive a callback when the job completes. You can also poll GET /v1/screenshot/{id} until status is done.

How long are download URLs available?

Completed screenshots return a temporary download URL (typically valid about 48 hours with default storage). Call GET /v1/screenshot/{id}/download if you need a fresh link.

Can Screenshotor handle cookie consent banners?

Yes. Enable bannerBlocking per request with hide, reject, or accept modes, plus optional CSS selectors for stubborn consent UI before capture.

How does Screenshotor compare to ScreenshotOne or URL-thumbnail APIs?

Screenshotor is optimized for backend jobs, webhooks, dashboard history, and optional AI vision—not public signed GET thumbnail URLs. See our comparison hub for fact-checked pricing and feature notes.