Clean website screenshots, in one API call

POST to /v1/screenshot with `{ "url": "https://example.com" }` and your key as `Authorization: Bearer sk_live_...`. The response body is the image bytes (content-type: image/png) — save it to a file, upload it to storage, or stream it straight to your user. One call, one image, no polling.

Yes. Set `"fullPage": true` and APIScreenshot scrolls and stitches the entire scrollable page, not just what fits in the viewport. Leave it off (or false) to capture just the current viewport. You can also pass a CSS `selector` to capture a single element instead.

No — every screenshot is clean and presentation-ready by default. Before each capture APIScreenshot automatically removes cookie banners, consent popups and overlays: it clicks the "reject all" / "decline" button on the common consent-management platforms (OneTrust, Cookiebot, Quantcast, Didomi, Usercentrics, TrustArc, Osano, CookieYes, Complianz and more), hides a curated list of cookie/consent/overlay elements, and lifts any scroll-lock the banner added, so your screenshot shows the page, not the pop-up. A page-health guard reverts the clean-up and captures the original if hiding ever left the page near-empty, so you never get a blank image. You can pass `hideSelectors` to remove your own extra elements, `"blockAds": true` to also drop common ad slots, or `"blockCookieBanners": false` if you ever want banners left in. Honest caveats: on "consent-or-pay" paywalls the wall is visually hidden, not legally consented to; and heavily bot-protected sites (aggressive CAPTCHAs / fingerprinting) are out of scope for now, though a stealth/proxy tier is on the roadmap.

Yes. Instead of `url`, send a `html` string and APIScreenshot renders exactly that markup in a real browser engine, then returns the screenshot. It is ideal for receipts, social/OG images, email previews and any HTML you generate on the fly — no need to host a page first.

Output is PNG (lossless, the default), or JPEG or WebP with a quality setting when you want smaller files — WebP gives the best size-for-quality on the web. You control the capture with `viewport` (width and height for desktop, tablet or mobile) and `deviceScaleFactor` (set 2 or 3 for crisp retina images).

No. By default each screenshot is rendered transiently and the bytes are streamed straight back to you; nothing is persisted on our side. Optional R2-backed hosting with signed URLs is on the roadmap for when you want us to host the image for you, but until you opt in, we keep nothing.

Yes — APIScreenshot ships a drop-in MCP (Model Context Protocol) server. Point Claude, or any MCP-capable client, at it and the agent gets a native `screenshot` tool: it can capture any web page or rendered HTML as part of a workflow, no glue code required.

One screenshot = one credit. Each screenshot is one render of browser time, so usage is metered per screenshot. Cached results and failed requests are never billed. Each plan includes a monthly bucket of screenshots; when you reach it, requests are hard-capped (HTTP 402) rather than billed for overage — upgrade to a larger plan to keep going.