Website Screenshot Generator: Full Page & PDF
Pricing
from $6.00 / 1,000 screenshots
Website Screenshot Generator: Full Page & PDF
Website screenshot API: bulk full-page or viewport screenshots of any URL as PNG/JPEG, or URL to PDF. Desktop, tablet, mobile; cookie banners removed, lazy images loaded. $6 per 1,000 screenshots, $3.50 per 1,000 failed URLs.
Pricing
from $6.00 / 1,000 screenshots
Rating
0.0
(0)
Developer
John Wilkinson
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Features
Share
Website Screenshot Generator: Bulk Full-Page Screenshots & URL to PDF
Take website screenshots in bulk, or convert URLs to PDF. Paste a list of URLs and get full-page or viewport screenshots as PNG or JPEG, or a URL-to-PDF render, on desktop, laptop, tablet, iPhone, or Android viewports, with cookie banners removed. $6 per 1,000 screenshots; failed pages $3.50 per 1,000.
This website screenshot generator works as a bulk URL screenshot tool, a full-page and mobile screenshot taker, a web page to PDF converter and an element screenshot capture (one CSS selector, such as a chart, pricing table, or tweet). Each result has a direct image URL you can download, embed, or pass to an AI agent or LLM vision model, and you can run it from the Apify API, n8n, Make, or Zapier.
It is built for clean captures. Cookie banners and consent popups are dismissed automatically (OneTrust, Cookiebot, Didomi, Usercentrics, Sourcepoint, Quantcast, TrustArc and generic ones). Lazy-loaded images are scrolled into view so the full page renders. Failed pages, DNS errors and HTTP 4xx/5xx pages are charged as failed items ($0.0035).
What it does
- Full-page screenshots of the whole scrollable page, or the visible viewport only.
- Device presets: desktop 1920×1080, laptop 1366×768, tablet (iPad, retina), mobile (iPhone 390×844 @3x), Android (Pixel), or any custom width, height and pixel density.
- PNG, JPEG, or PDF: get several formats in one run, e.g. a PNG plus a PDF of the same page.
- Cookie banner and popup removal: clicks "Accept" in 13 languages, hides known consent platforms, and unlocks pages that a consent wall stops from scrolling.
- Lazy-load handling: scrolls the page before capturing so images and sections below the fold load.
- Element screenshots: capture a single CSS selector, e.g. a chart, pricing table, or tweet.
- Hide elements: remove chat widgets, ads, or sticky headers with CSS selectors.
- Wait controls:
waitUntil(load / networkidle),waitForSelector, and an extra delay for animations. - Dark mode (
prefers-color-scheme: dark) and a custom user agent. - Bulk and fast: one shared headless Chromium, capturing one page per GB of run memory (two at a time at the default 2 GB). Typical pages take 2–10 s.
- Robust: a timeout still captures whatever had loaded (with a warning), one bad URL never fails the run, and each error is readable ("Domain does not resolve", "Page returned HTTP 404"…).
Use cases
- SEO and agency reporting: screenshot client homepages and landing pages every week.
- Visual QA and regression checks on desktop and mobile.
- Archiving and compliance: keep dated PDF or PNG captures of web pages, ads, and terms pages.
- Competitor monitoring: track pricing pages and homepages over time (pair it with an Apify schedule).
- AI agents and LLM vision: give a model "what this page looks like" via the image URL.
- Link previews and thumbnails for directories and dashboards.
Input
| Field | Default | Description |
|---|---|---|
urls | – (the form prefills two sample URLs) | List of URLs: [{ "url": "https://…" }] |
device | desktop | desktop, laptop, tablet, mobile, android, custom |
fullPage | true | Whole page vs. visible viewport |
formats | ["png"] | Any of png, jpeg, pdf |
pdfFormat | A4 | A4, Letter, Legal, A3, Tabloid |
jpegQuality | 80 | JPEG quality 1–100 |
includeHtml | false | Also return the rendered HTML |
dismissCookieBanners | true | Accept or hide cookie/consent popups |
blockTrackers | true | Block analytics, ads, chat widgets and video (faster, cleaner) |
darkMode | false | Emulate dark color scheme |
delayMs | 1000 | Extra wait after load |
waitUntil | load | load, domcontentloaded, networkidle |
waitForSelector | – | Wait for a CSS selector before capturing |
selector | – | Capture only this element |
hideSelectors | – | CSS selectors to hide |
width / height / deviceScaleFactor | preset | Custom viewport |
userAgent | – | Custom User-Agent (advanced) |
proxyConfiguration | off | Optional proxy for geo- or IP-blocked pages: Apify datacenter proxy or your own proxy URLs. Residential proxies are not offered. Traffic is capped at 25 MB per URL |
Example input
{"urls": [{ "url": "https://apify.com" }, { "url": "https://www.bbc.co.uk" }],"device": "mobile","fullPage": true,"formats": ["png", "pdf"]}
Output
Images and PDFs are stored in the run's key-value store. The dataset has one item per URL:
{"url": "https://apify.com","status": "success","screenshotUrl": "https://api.apify.com/v2/key-value-stores/<id>/records/apify.com-mobile-1a2b3c4d5e.png","pdfUrl": "https://api.apify.com/v2/key-value-stores/<id>/records/apify.com-mobile-1a2b3c4d5e.pdf","title": "Apify: Full-stack web scraping and data extraction platform","finalUrl": "https://apify.com/","httpStatus": 200,"pageHeight": 12771,"warnings": [],"error": null}
status is success, http_error (the page answered 4xx/5xx; it is still captured, but billed as a failed URL), error (nothing captured, with a readable error) or skipped (not processed and not charged because the run's maximum charge was reached). A run where no URL could be captured at all finishes as Failed; the error rows are still in the dataset. Run statistics are saved to RUN_SUMMARY in the key-value store.
Use it from code or an AI agent
curl -X POST "https://api.apify.com/v2/acts/jcwilk~website-screenshot/run-sync-get-dataset-items?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"urls":[{"url":"https://example.com"}],"device":"desktop","formats":["png"]}'
The response has the screenshotUrl for each page. The Actor also works as a tool through the Apify MCP server: the input is a flat JSON object with a URL list, so it is easy for LLM agents to call.
Pricing (pay per event)
| Event | Price |
|---|---|
| Actor start (per GB of run memory; default 2 GB = $0.015) | $0.0075 per GB |
| Screenshot (PNG or JPEG) | $0.006 ($6 per 1,000) |
| Page saved as PDF | $0.015 |
| Failed URL (HTTP error, timeout, unreachable) | $0.0035 |
You pay for work done, success or failure. Every URL is charged once: one event per file when it succeeds, or the failed-URL price when it can't be completed. Failed means an error, a timeout, an unreachable site, a selector that isn't on the page, or an HTTP 4xx/5xx page (those are still captured and returned as http_error, but billed as failed). Several formats of one page charge one event per format (PNG + JPEG = $0.012). Duplicate URLs are processed once. The default 2 GB of memory bills two start events ($0.015) per run. One URL costs about $0.021, and 1,000 screenshots in one run about $6.015. Set a maximum cost per run in Apify to cap spend; the run stops cleanly when it is reached. Each URL is capped at 20 s, and very large captures are limited to about 31 megapixels (the pixel density or full-page height is reduced to fit). Platform compute and browser time are included.
FAQ
Is this a ScreenshotOne / Urlbox / screenshotapi.net alternative? For bulk, pay-as-you-go captures without a monthly plan, yes: you call it through the Apify API, MCP server, Make, Zapier or n8n and pay per screenshot (failed pages are billed at a lower price).
Does it remove cookie banners? Yes, by default. It clicks the "Accept" button when it can find one (English, German, French, Spanish, Italian, Portuguese, Dutch, Swedish, Finnish, Polish, Czech, Turkish and Japanese), hides the major consent platforms, and re-enables scrolling. Turn it off with dismissCookieBanners: false if you need the banner in the image.
Which memory should I use? The default 2 GB captures two pages at a time and handles heavy pages such as news sites and GitHub within the 20 s per-URL limit. Lower memory means less CPU: at 1 GB (the minimum), many heavy pages time out and are charged as failed URLs, so use 1 GB only for light pages. If the browser runs out of memory on a page, the Actor retries it once with a smaller capture (height limited to 6,000 px) and adds a warning to the row.
Why is my screenshot cut off at the bottom? Pages taller than 16,384 px are cut to keep files usable, and less at a higher pixel density because captures are limited to about 31 megapixels (the warnings field says so). Use selector to capture one section of a very long page, or run it with fullPage off.
Can it screenshot pages behind a login? No. It captures public pages only.
Can I use a proxy? Yes, optionally: set proxyConfiguration to Apify datacenter proxy or to your own proxy URLs (for example for geo-restricted pages or sites that block our IPs). It is off by default. Residential proxies are not offered, because their traffic would cost far more than a screenshot. Proxied traffic is capped at 25 MB per URL. Proxies are slower: very heavy pages can hit the 20-second per-URL limit and are then charged as a failed URL.
Does it work on sites with bot protection? Most public sites work without a proxy. Sites behind aggressive anti-bot walls (e.g. some Cloudflare challenges) may show the challenge page instead.
How long are image URLs valid? They live in your run's key-value store, so they follow your Apify data retention (unnamed storages are kept for 7 days on the free plan). Download them, or copy them to a named store, to keep them longer.
Can I schedule it? Yes. Use Apify Schedules to capture the same URLs daily or weekly for monitoring and archiving.
Limitations
- Public pages only: no login, cookies or custom headers.
- Videos, canvas animations, and some WebGL content may look different from a real browser.
- A few consent walls that need a choice before any content loads (rare) may still appear.
- Full-page images are limited to 16,384 px in height (less at a higher pixel density). PDF output uses print layout, with background graphics on.