New: Monitors. Watch any website for changes

Backed by

Combinator

Screenshot {API}

Capture pixel-perfect website screenshots from any URL with one call.

Choose viewport dimensions or full-page capture, wait for dynamic content, handle popups, select a light or dark color scheme, and control cache freshness.

No card required

View Documentation

What You Get

Each API call returns a high-quality screenshot hosted on our CDN.

Full-page or viewport

Capture entire page or visible area

Capture controls

Set wait time, popup cleanup, theme, and cache age

Custom viewport

Capture responsive layouts at a width and height you choose

CDN-hosted

Ready-to-use image URLs delivered globally

How It Works

We use headless Chrome to render websites pixel-perfectly.

— step 01 —

Send a URL

With optional viewport, full-page, wait, popup, and theme controls

— step 02 —

Headless Chrome renders

Full JavaScript support, animations, and dynamic content

— step 03 —

Image processed

Optimized and uploaded to our global CDN

— step 04 —

URL returned

Clean, high-quality image ready for immediate use

API Response

Extracted screenshot for context.dev

GET /v1/web/screenshot?domain=context.dev

Try in API Playground

{
  "status": "ok",
  "domain": "context.dev",
  "screenshot": "https://media.context.dev/5b4c4859-3777-41b0-9597-5d55a7e02f31.jpg",
  "screenshotType": "viewport",
  "width": 1920,
  "height": 1080,
  "code": 200
}

Frequently asked questions

Common questions about the Context.dev Screenshot API.

Am I billed for failed requests?

No. You are not billed for failed requests or requests where we are blocked (rarely happens). Credits are only consumed on successful responses.

Can the screenshot API capture full-page screenshots?

Yes. The default is a viewport capture. Set fullScreenshot=true to capture the full scrollable page. screenshotType is returned in the response; it is not a request parameter.

Can I choose the image format or quality?

The public request does not currently expose format or quality parameters. Use the returned screenshot URL, or enable zero data retention to receive the documented in-memory data URL behavior.

Can I use the screenshot API for OG images and link previews?

Yes — that's a common use case. Generate OG images for blog posts, link previews for chat apps, thumbnail cards for marketplaces, and dashboard tiles for monitoring. The CDN URLs are stable, so cache aggressively at the edge.

How do I take a screenshot of a website with the API?

Send a GET request to /v1/web/screenshot?domain=<target>, or use directUrl for an exact page. The API renders the page, captures it, and returns the image location plus the capture type and dimensions when available.

Does the API support mobile emulation?

Specify custom viewport width and height to exercise responsive layouts. The public request does not expose named device presets or a device-pixel-ratio control.

How is this a Urlbox / ApiFlash / ScreenshotOne alternative?

Same single-call ergonomics — pass URL, get image. But Context.dev bundles the Screenshot API with the rest of the brand-data stack (logos, colors, web scraping, NAICS/SIC) on a single API key. Pricing is per-call with a real free tier; OG-image-style flows often need only the free tier.

Is the screenshot API free?

Yes — work-email signups get 500 API credits at 30 req/min, enough for 500 one-credit screenshot calls; free-email signups get 250 credits at 10 req/min. A single API key also unlocks Logo, Colors, Fonts, web scraping, sitemaps, NAICS/SIC, and the rest of the Context.dev stack.