Website Screenshot Capture
Last updated November 18, 2026
Capture website screenshots from a list of URLs. Each page opens in a Chromium browser and comes back as a PNG or JPEG link, with the final URL, HTTP status, title, and image size in one row. Full page or window, any width, wait options, hide selectors. Blocked pages are free.
Install
npx @mambalabsdev/mcp-website-screenshot-captureEvery tool here also runs hosted, with no install at all, through Apify's MCP endpoint.
Features
- One row per URL with the image link, final URL, HTTP status, and title.
- Full page up to 16,000 pixels tall, or the window only, at any width.
- PNG or JPEG, wait options, scroll first, and CSS selectors to hide.
- A page that refuses the browser is a free row.
- Pay per event: Screenshot at $0.016.
Input
urlsarrayoptionalPages to capture, each starting with http:// or https://. A bare domain such as example.com gets https:// added. From Clay, put the column inside a one item list.
full_pagestringoptionalyes captures the whole scrollable page, up to 16,000 pixels tall. no (default) captures the visible window only.
viewport_widthstringoptionalBrowser window width, 320 to 3840. Default 1280.
viewport_heightstringoptionalBrowser window height, 240 to 2160. Default 800. With Full page on, the image is as tall as the page.
formatstringoptionalpng (default) or jpeg. JPEG files are smaller.
jpeg_qualitystringoptional1 to 100, used for jpeg only. Default 80.
wait_untilstringoptionalWhen the page counts as loaded. load (default): the page and its images loaded. domcontentloaded: the HTML is parsed, faster. networkidle: no network traffic for 0.5 s, best for pages that load content late.
delay_msstringoptionalExtra wait after the page loads and before the capture, 0 to 20000. Default 0.
scroll_to_bottomstringoptionalyes scrolls down the page before the capture so images that load on scroll appear, then returns to the top. Default no.
hide_selectorsarrayoptionalElements to hide before the capture, for example a cookie banner or a chat widget: #cookie-banner, .chat-widget.
block_trackersstringoptionalyes (default) skips analytics, ad, and session replay scripts and video or audio files, which draw nothing you need in the image and make pages slower. no loads everything, so ads appear.
timeout_secondsstringoptionalLongest wait for one page to load, 10 to 120. Default 60. A page still loading at this point is captured as it stands and marked partial.
max_charge_usdstringoptionalOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.
proxy_modestringoptionalauto (default): pages load through the Apify proxy pool. none: pages load straight from the Apify server. A reliability setting only; it does not change what you pay.
Output schema
{
"row_type": "string",
"url": "string",
"input_url": "string",
"final_url": "string",
"http_status": "integer",
"page_title": "string",
"screenshot_url": "string",
"screenshot_key": "string",
"image_format": "string",
"image_width": "integer",
"image_height": "integer",
"image_bytes": "integer",
"full_page": "boolean",
"viewport": "string",
"load_ms": "integer",
"row_status": "string",
"error_reason": "string",
"billable_events_json": "string",
"scraped_at": "string"
}Pricing
| Event | Free plan price |
|---|---|
| Screenshot | $0.016 |
| Full page screenshot | $0.023 |
| Actor Start | $0.013 |
Pay per event on the Apify platform. Paid Apify plans pay less per event. No subscription, no seat license.
On the Apify free plan the actor stops at $1.50 of charges a month, about 94 screenshots. Any paid Apify plan removes the cap.
Limits
- Pages behind a login, a captcha, or a bot protection service are not captured. They come back as free blocked rows.
- Full page images stop at 16,000 pixels tall.
- Pages load in a US or other proxy pool location chosen by Apify; there is no country choice, so a site that changes by country shows the version for that address.
- With block_trackers on, ad slots render empty and videos show no frame.
- Images use a device scale of 1 (no retina doubling).
- Heavy pages can take 30 to 60 s each at the default 1024 MB, and 3 pages load at a time (2 in full page mode). Raise the run memory for more parallel pages (up to 4); the run start event is charged once per GB.
- Pages that keep loading content forever never reach networkidle; use load or domcontentloaded with an extra wait for those.
- Run storage expires with your plan's retention period, so the image links do too.