Screenshot API FAQ

A Screenshot API is a hosted service that accepts a URL or raw HTML and returns an image (PNG, JPEG, WebP) or PDF of that page as rendered in a real headless browser. You call a single HTTP endpoint instead of running and maintaining a fleet of Chrome instances yourself.

Modern Screenshot APIs go well beyond basic captures: they support full-page screenshots, visual diffs between two URLs, PDF export, structured content extraction, and MCP tools that AI agents can invoke directly.

Read full answer

Pass the full_page=true parameter to the Screenshot API endpoint. The service scrolls the entire document, stitches the frames, and returns a single tall image. With SnapshotFlow:

GET https://api.snapshotflow.com/screenshot?url=https://example.com&full_page=true

You can also control viewport width, set a wait condition, and choose the output format.

Read full answer

Yes. Leading Screenshot APIs run a real Chromium-based headless browser, so React, Vue, Angular, and Svelte apps render exactly as they do for a real user. To guarantee the page is fully hydrated before capture, pass a wait condition:

• A CSS selector — waits until that element appears in the DOM
• A DOM event like networkidle
• A fixed delay in milliseconds
• A custom JavaScript expression that resolves to true

Read full answer

Three pricing models dominate: per screenshot (monthly bucket + overage), per second of compute, and a self-host license for unlimited renders on your own hardware.

• At 10,000 shots/month: typically $20–$49/month
• At 100,000 shots/month: typically $49–$199/month
• SnapshotFlow free tier: 200 screenshots/month, no credit card required

Read full answer

Yes, and it is one of the most popular use cases. Call a /diff endpoint with two URLs (or a baseline image and a live URL). The API renders both, runs pixel-level comparison via pixelmatch, and returns a diff PNG plus a numeric score.

SnapshotFlow's built-in /diff endpoint replaces Percy, BackstopJS, or custom Playwright snapshot runners with one CI-ready HTTP call.

Read full answer

Managed APIs render from the vendor's network and cannot reach internal hosts by default. For public authenticated pages, pass session cookies, HTTP Basic auth headers, or a signed URL in your request. For pages behind a VPN or firewall, deploy a self-hosted Screenshot API inside your own infrastructure.

SnapshotFlow ships an official Docker image that runs identically on-premises, letting you capture internal dashboards, staging environments, and private apps without exposing credentials to a third party.

Read full answer

Look for a Screenshot API that ships a Model Context Protocol (MCP) server or WebMCP tools. MCP lets AI agents like Claude or Cursor call screenshot(), visual_diff(), and extract_content() as native tools — without scraping or screen recording.

SnapshotFlow provides both a Remote MCP endpoint and WebMCP tools exposed via navigator.modelContext, making it the most agent-ready Screenshot API in 2026.

Read full answer