Website Screenshot – Bulk Full Page PNG, JPEG & PDF avatar

Website Screenshot – Bulk Full Page PNG, JPEG & PDF

Pricing

$3.00 / 1,000 screenshot takens

Go to Apify Store
Website Screenshot – Bulk Full Page PNG, JPEG & PDF

Website Screenshot – Bulk Full Page PNG, JPEG & PDF

Screenshot many URLs at once: full-page or viewport PNG/JPEG or PDF, desktop or mobile, cookie banners hidden. Each image gets a public URL; one dataset row per page with status, final URL, size and errors.

Pricing

$3.00 / 1,000 screenshot takens

Rating

0.0

(0)

Developer

Forever Tools

Forever Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 minutes ago

Last modified

Share

Bulk Website Screenshot (PNG, JPEG, PDF)

Paste a list of URLs and get a screenshot of every page, each with its own public image URL. You can choose full-page or viewport-only, PNG, JPEG or PDF, desktop or mobile, and set a custom viewport, wait strategy and delay. Common cookie consent banners are hidden (best effort) so the page itself is what you see. Runs real Chromium (Playwright).

Use it to: archive or monitor landing pages, check that a redesign rendered correctly across many pages, get competitor page snapshots, add thumbnails to a directory or CMS, make visual QA reports, collect evidence of how a page looked on a date, or save pages as PDFs.

Features

  • Bulk: any number of URLs, captured 3 at a time. If one URL fails, the error goes in its row and the run keeps going.
  • Formats: PNG (lossless), JPEG (quality 85, much smaller), or PDF (screen styles, backgrounds kept, one tall page).
  • Full page or viewport: fullPage scrolls the whole page into one image.
  • Devices: Desktop (viewport default 1280×800, configurable) or Mobile (iPhone-class 390×844 at 3× scale with a touch-enabled mobile user agent).
  • Wait control: load (fast) or networkidle (better for JS-heavy apps), plus an extra delay for animations and lazy-loaded content. If a page never reaches network idle, whatever has rendered is captured and a note is added.
  • Cookie banner hiding (best effort): CSS rules for OneTrust, Cookiebot, Didomi, Quantcast, TrustArc, Usercentrics, Osano, CookieYes, Complianz, iubenda, Sourcepoint, Funding Choices, HubSpot, Klaro, Axeptio, tarteaucitron, Borlabs, Termly and generic cookie-banner/cookie-consent patterns. Banners are hidden, never clicked, so no consent is given on your behalf.

Input

{
"urls": ["https://example.com", "apify.com"],
"format": "png",
"fullPage": true,
"device": "desktop",
"viewportWidth": 1280,
"viewportHeight": 800,
"waitUntil": "load",
"delayMs": 0,
"hideCookieBanners": true,
"timeoutSecs": 45
}

URLs without a scheme get https://. Duplicate URLs are captured only once.

Output (one dataset row per URL)

{
"url": "https://example.com/",
"finalUrl": "https://example.com/",
"status": 200,
"screenshotUrl": "https://api.apify.com/v2/key-value-stores/<storeId>/records/0001-example.com.png",
"width": 1280,
"height": 800,
"bytes": 20874,
"format": "png",
"device": "desktop",
"error": null
}
  • screenshotUrl is a direct link to the file in the run's key-value store. Open it in a browser, embed it, or download it.
  • width/height are in pixels. Mobile images are 3× the CSS size, e.g. 1170 px wide. For PDFs they are the page size in CSS px.
  • status is the HTTP status of the final response. 4xx/5xx pages are still captured and error says HTTP 404, etc.
  • error is set when a page couldn't be loaded (DNS failure, timeout, TLS error...). Those rows have no screenshot. It is also used for the partial-load note.

The Overview table in the Console shows image previews. Export the dataset as CSV, JSON or Excel, or fetch it via the API.

Tips

  • Single-page apps: use waitUntil: "networkidle" or a delayMs of 1000–3000.
  • Very long pages make very large PNGs. Use JPEG, or turn off fullPage.
  • PDFs are one continuous page (height capped at about 19,200 px by Chromium), not split into A4 sheets.
  • Pages behind a login, a CAPTCHA or bot protection may capture as the challenge page.

Limitations

Cookie banner hiding is best effort. Uncommon or custom consent popups may still show. The actor takes whatever the page shows to a fresh, logged-out visitor with no cookies. Respect the terms of the sites you capture.

Support

Open an issue on the actor's Issues tab and include the URL and your input. This actor is maintained with AI assistance and issues are answered asynchronously.

Other actors by the same developer (same flat pay-per-result pricing, no subscription):

Integrations

Run it from the Apify API, a schedule, or no-code tools: the Apify apps for Zapier, Make and n8n can start any public actor ("Run Actor") and read its dataset. AI agents can call it through the Apify MCP server.