Website Screenshot – Bulk Full-Page PNG, JPEG, WebP & PDF

Capture any number of web pages in one run: full page or just the viewport, as desktop, laptop, tablet or mobile, saved as PNG, JPEG, WebP or PDF. Every result comes with a public link to the file, the page title and the HTTP status, so you can drop the output straight into a spreadsheet, a report or your app.

Cookie banners are hidden, lazy-loaded images are scrolled into view, and pages that fail or are blocked are not charged.

What you get

Field	Description
screenshotUrl	Public link to the PNG/JPEG/WebP image or the PDF
title, statusCode, finalUrl	Page title, HTTP status and the URL after redirects
width, height, fileSizeBytes	Size of the capture
device, format	What was used for this capture
error	Why a page failed (failed pages are free)

The files themselves are stored in the run's key-value store, so you can also download them all at once.

Features

• Bulk: paste 2 URLs or 20,000. Pages are captured in parallel (1–10 at a time).
• Full page or viewport, with a height cap for endless pages.
• Real devices: desktop 1920×1080, laptop 1366×768, iPad, iPhone 14 and Pixel 7 profiles (pixel ratio, touch and mobile user agent), or your own viewport size.
• Clean captures: hides cookie and consent pop-ups from OneTrust, Cookiebot, Usercentrics, Didomi, Quantcast, Termly, Complianz and more (hidden, never accepted). Optional ad and tracker blocking.
• Lazy loading handled: scrolls through the page first so images and sections below the fold render.
• Element screenshots: give a CSS selector such as #pricing to capture one section.
• Dark mode, a wait-for-element option, an extra delay for animations, and a choice of when the page counts as ready.
• PDF export: A4 with backgrounds, ready to print or archive.
• Proxy support for sites that block data-centre traffic or show country-specific content.

Use cases

• Website monitoring and QA: capture your pages on mobile and desktop after every release.
• SEO and agency reports: add screenshots of client and competitor pages to audits.
• Archiving and compliance: keep dated PDFs of landing pages, terms or ads.
• Lead lists and research: add a preview image to every company in a spreadsheet.
• AI agents: call it through the Apify API or MCP server to let an agent "see" a page.

Input example

{
  "urls": ["https://apify.com", "https://www.wikipedia.org"],
  "format": "png",
  "device": "mobile",
  "fullPage": true,
  "hideCookieBanners": true
}

Output example

From a real run (mobile, PNG):

{
  "url": "https://www.wikipedia.org",
  "format": "png",
  "device": "mobile",
  "finalUrl": "https://www.wikipedia.org/",
  "statusCode": 200,
  "title": "Wikipedia",
  "width": 390,
  "height": 1584,
  "screenshotUrl": "https://api.apify.com/v2/key-value-stores/<storeId>/records/00002-www-wikipedia-org.png?signature=<signature>",
  "recordKey": "00002-www-wikipedia-org.png",
  "fileSizeBytes": 679756,
  "takenAt": "2026-10-26T11:03:30Z"
}

Pricing

Pay per event: $4 per 1,000 screenshots (less on higher Apify plans). A PDF counts as one screenshot. Pages that fail, time out or return an HTTP error (for example a 403 bot block) are not charged; you still get the image of what the site showed. You can set a maximum spend per run in the run options; the actor stops cleanly when it is reached.

Tips

• Single-page apps (React, Vue): set Page is ready when to Network idle, or add Wait for element.
• Very long pages: lower Max full-page height to keep files small, or use JPEG/WebP.
• Sites that block bots: turn on Proxy (residential proxies help most).

FAQ

Are screenshots private? Files are stored in your run's key-value store. The screenshotUrl link works for anyone who has it, like most screenshot APIs; don't share it if the page is sensitive.

Does it accept cookie banners? No. Known banners are hidden with CSS; no consent is given on your behalf.

Can I capture pages behind a login? Not in this version.

Something wrong? Open an issue on the actor's Issues tab and it will be fixed.