Screenshot {API}

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

Send a GET request to /v1/screenshot?domain=<target>. The API spins up a headless Chrome instance, renders the page (JavaScript, animations, web fonts, all loaded), captures the image, uploads it to a global CDN, and returns the image URL in JSON. No browser to install, no Puppeteer to maintain.

Yes. By default the API captures the viewport, but full-page mode captures the entire scrollable height as a single image — useful for previewing landing pages, blog posts, or long-form content. Set the screenshotType to "fullPage".

Yes. Specify a custom viewport (width × height) and the API renders the page at that size with the matching device-pixel-ratio. Standard mobile sizes (iPhone, iPad, Pixel) are supported, plus arbitrary breakpoints for QA and responsive testing.

PNG (lossless, larger files, best for UIs and screenshots with text) and JPEG (smaller, lossy, best for photo-heavy pages). Quality is configurable for JPEG. All screenshots are served from a global CDN with stable URLs you can hotlink.

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.

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.

Yes — the free tier covers thousands of monthly screenshots. A single API key also unlocks Logo, Colors, Fonts, web scraping, sitemaps, NAICS/SIC, and the rest of the Context.dev stack.