Website Screenshot API: Screenshot URL, Full Page & PDF avatar

Website Screenshot API: Screenshot URL, Full Page & PDF

Pricing

from $0.60 / 1,000 screenshots

Go to Apify Store
Website Screenshot API: Screenshot URL, Full Page & PDF

Website Screenshot API: Screenshot URL, Full Page & PDF

Website screenshot API for bulk URLs: screenshot a URL or full page, or one element, as PNG, JPEG or PDF. Desktop, tablet and mobile sizes, cookie banners hidden, robots.txt respected. Failed URLs are never charged.

Pricing

from $0.60 / 1,000 screenshots

Rating

0.0

(0)

Developer

Altronite

Altronite

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

19 days ago

Last modified

Features

Limited permissions

Share

A website screenshot API and tool for batches of URLs: screenshot a URL, take a full page screenshot, or turn a webpage to image (PNG or JPEG) or PDF. Capture the visible screen, the full scrolling page or one element by CSS selector, at desktop, laptop, tablet or mobile size. A URL that can't be captured becomes an error row with the reason, is never charged, and doesn't stop the run.

Input: a list of URLs. Output: desktop and mobile PNG screenshots, plus an uncharged error row for a 404 page

One link in, one screenshot row out

Quick start

Paste this into the Input tab (JSON view) and press Start. One page, one PNG:

{ "urls": ["https://example.com"], "fullPage": true }

Open the Output tab: each row links to the stored image through screenshotUrl.

More recipes:

{ "urls": ["https://example.com", "https://example.org"], "format": "pdf" }
{ "urls": ["https://example.com"], "device": "mobile", "format": "jpeg", "quality": 80 }
{ "urls": ["https://example.com"], "selector": "p" }
{ "urls": ["https://example.com/pricing"], "fullPage": true, "waitUntil": "networkidle", "waitForSelector": "h1", "delayMs": 1000 }
{ "urls": ["https://example.com"], "device": "tablet", "darkMode": true }

(One JSON object per run; the lines above are separate examples.)

Who it's for

  • QA and front-end teams: check mobile and desktop layouts across many pages in one run, or capture a single component with selector.
  • SEO and marketing: snapshot your own and competitors' public landing and pricing pages.
  • Monitoring and archiving: schedule runs for a dated visual record, as images or PDFs.
  • AI agents and LLM pipelines: give a model an image of a page; every row has a status field to branch on.

What you get

One dataset row per non-blank URL when the input contains at least one valid URL. The file is saved in the run's key-value store and screenshotUrl links to it.

{
"status": "ok",
"url": "https://example.com",
"finalUrl": "https://example.com/",
"httpStatus": 200,
"title": "Example Domain",
"screenshotUrl": "https://api.apify.com/v2/key-value-stores/<store-id>/records/screenshot-0000-327c3fda87ce.png",
"storageKey": "screenshot-0000-327c3fda87ce.png",
"format": "png",
"device": "desktop",
"viewportWidth": 1920,
"viewportHeight": 1080,
"fullPage": true,
"bytes": 74188,
"takenAt": "2026-10-21T10:15:37+00:00"
}

finalUrl is the address after redirects; title is cut at 300 characters. Viewport sizes are CSS pixels, not file dimensions. fullPage records the requested option even when element capture or PDF ignores it. bytes is the stored file size. takenAt is the UTC row creation time.

Every row has url, status and takenAt. Uncharged error rows also have error (at most 500 characters), input and scrapedAt (same time as takenAt). Rejected HTTP pages and bot checks also have httpStatus.

{ "status": "error", "url": "https://example.com/missing", "httpStatus": 404, "error": "The page answered 404", "input": "https://example.com/missing", "takenAt": "2026-10-21T10:12:04+00:00", "scrapedAt": "2026-10-21T10:12:04+00:00" }

Use it from code or an AI agent

Run this actor with the Apify API, the Apify Python or JavaScript clients, or as a tool through the Apify MCP server. Pass the same input JSON through any of these. Inspect status on each row; for ok rows fetch screenshotUrl, and error rows explain failed captures.

Input

Only urls is required.

FieldDefaultWhat it does
urls["https://apify.com"]Pages to capture, up to 1,000. A missing scheme becomes https://. Invalid entries become uncharged error rows.
devicedesktopdesktop 1920x1080, laptop 1366x768, tablet 810x1080 at 2x, mobile 390x844 at 3x, or custom.
viewportWidth, viewportHeight1280, 800Used only when device is custom (200 to 3840 by 200 to 2160, at 1x).
fullPagefalseCapture the whole scrolling page. Ignored for selector and for PDF.
selectornoneCSS selector; only that element is captured (PNG or JPEG). Not found gives an uncharged error row.
formatpngpng, jpeg or pdf (browser print engine).
quality80JPEG quality, 1 to 100.
waitUntilloadload, domcontentloaded or networkidle.
waitForSelectornoneCSS selector that must become visible before capture.
delayMs0Extra wait after load, up to 30,000 ms.
hideCookieBannerstrueHides common consent pop-ups with CSS; nothing is clicked.
darkModefalseAsks the page for prefers-color-scheme: dark.
respectRobotsTxttrueSkips URLs the site's robots.txt disallows.
timeoutSecs45Per step (navigation, selector wait, capture): 5 to 180.
maxConcurrency3Pages at once, 1 to 7. Memory defaults to 1 GB and supports up to 4,096 MB; lower this if a run runs out of memory.
chargeHttpErrorsfalseCapture and charge pages answering 400 or higher. Detected bot checks stay uncharged.
scrollToLoadtrueScroll up to 20 steps or about 5 s before PNG or JPEG capture. PDF does not scroll.

Pricing

Pay per event. You pay for two things:

EventPriceWhen
screenshot$0.0006 per delivered screenshot or PDFeach ok row
apify-actor-start$0.004 per runonce per run, one event per GB of memory with a 1 GB minimum

Examples:

  • 100 URLs, all captured: 100 x $0.0006 + $0.004 = $0.064.
  • 1,000 URLs: 1,000 x $0.0006 + $0.004 = $0.604.
  • 100 URLs where 20 fail: 80 x $0.0006 + $0.004 = $0.052. Failed URLs are never charged.
  • Same 100 URLs at 4 GB memory: the start fee is 4 x $0.004 = $0.016, so $0.076 in total.

Not charged: error rows (failed loads after the retry, robots.txt skips, invalid URLs, a selector or waitForSelector that is not found, HTTP 4xx/5xx pages unless chargeHttpErrors is on, detected bot checks). A URL listed twice is captured and charged twice. Prices were read from the Store on 21 Oct 2026; the Pricing tab is the source of truth.

Reliability

  • One bad URL never fails the run. Any failure becomes an error row with the reason.
  • Navigation and screenshot/PDF browser errors or timeouts are retried once, after a short random pause in a fresh browser context. Missing selector or waitForSelector elements, HTTP rejections, bot checks and robots skips are uncharged and not retried.
  • Timeouts apply per step. timeoutSecs limits page loading, waiting for waitForSelector, and taking the image, each separately. Robots fetching has a 10 s timeout; scrolling takes about 5 s at most, and delayMs adds up to 30 s. These are not a total per-URL deadline.
  • Chinese, Japanese, Korean and emoji fonts are installed, so text doesn't render as empty boxes.
  • Invalid input (for example, no valid URL at all) stops the run at the start with a message saying what to fix. Nothing is charged.

Use cases

  1. QA teams validating responsive layouts: A QA engineer submits a list of product page URLs with device: "mobile" and reviews the PNG files in the dataset to spot overflow, broken components, or text clipping across a batch.

  2. SEO analysts tracking competitor pricing pages: An SEO specialist schedules weekly runs capturing competitors' pricing pages as PDFs, building a dated visual record that shows when plans or promotions changed.

  3. AI pipeline developers feeding pages to a vision model: A developer sends URLs through the synchronous API, checks each row's status field, and fetches screenshotUrl for successful captures to pass as images to a multimodal LLM.

  4. Web designers building client portfolios: A designer captures client sites at desktop and tablet viewports, uses the element selector to grab just the hero section, and uses the JPEG outputs in their portfolio.

  5. Marketing teams monitoring their own landing pages: A marketing team captures their landing pages weekly, comparing the downloaded images across runs to spot unintended layout shifts or broken images.

  6. Compliance officers archiving public disclosures: A compliance officer captures regulatory disclosure pages as PDFs on a schedule, downloading each file to keep a dated visual record for audits.

FAQ

How do I take a full page screenshot of a website? Set fullPage to true. The actor scrolls the page first so lazy-loaded images appear (scrollToLoad, on by default), then saves the whole scrolling page as one image.

How do I screenshot many URLs at once? Put up to 1,000 URLs in urls and run once. You get one row per URL with a link to its file, and a URL that fails becomes an uncharged error row without stopping the run.

Can it save a webpage as a PDF? Yes. Set format to pdf to get one PDF per URL using the site's print styles. For more PDF options (paper size, margins, page numbers, merging into one file) see URL to PDF under Related tools.

Can AI agents call it? Yes, through the Apify API or as a tool via Apify's MCP server. Check status on each row, then fetch screenshotUrl.

Does it respect robots.txt? Yes, by default. Before capturing a URL, it reads that site's robots.txt (cached per origin) and skips URLs disallowed for all user agents (User-agent: *). A robots.txt that returns any 4xx status or cannot be reached counts as "allowed". One that returns a server error (5xx) counts as "disallow everything". Rules use longest-match precedence, * wildcards and $ end anchors; Allow wins ties. If a redirect lands on a different host, that final address is checked before capture, after the redirected request has already happened. Only wildcard-agent groups are used. Turn respectRobotsTxt off only for pages you have the right to capture.

Does it get past logins, paywalls or bot protection? No. It never logs in, uses no proxy and doesn't evade bot protection. Recognized Cloudflare-style bot checks become uncharged errors. Other protections may not be recognized; login and paywall pages that answer with a success status can be captured and charged.

How are cookie banners hidden? With CSS only; nothing is clicked or accepted. It targets common consent-manager containers and "cookie-consent" patterns. Custom pop-ups may still show.

Why are some images missing further down a full-page shot? The default scrollToLoad pass helps load images before PNG/JPEG capture. Its 20-step / about 5 s bound cannot cover every very long page or slow image. Add delayMs, or disable scrolling if it triggers unwanted behavior. PDFs do not scroll.

Troubleshooting

You see in errorCauseFix
"The page answered 404" (or another 4xx/5xx)The site returned an error statusFix the link. To capture error pages anyway, set chargeHttpErrors to true (they are then charged).
"The site showed a bot check (Cloudflare) instead of the page"A bot-protection page was detectedNot bypassed by this actor and never charged. Try again later or use a different page.
"page did not finish loading within 45s" or "navigation failed: ..."Slow or unreachable page; retried once alreadyRaise timeoutSecs, or set waitUntil to domcontentloaded.
"selector not found on the page: ..."selector matches nothing at capture timeCheck the selector; add waitForSelector or delayMs for late content. Not retried, not charged.
"waitForSelector '...' did not become visible within Ns"The element never became visibleCheck the selector, or raise timeoutSecs.
"skipped: robots.txt disallows this URL ..."The site's robots.txt blocks the URLSet respectRobotsTxt to false only for pages you have the right to capture.
"not a web URL (expected http:// or https:// and a host name)"Entry is not a web linkFix the entry; only http and https are accepted.
Run fails with "urls: no valid web URL given"Every entry was invalidProvide at least one valid URL. Nothing is charged.
Images missing low on a long pageScroll pass (20 steps, about 5 s) did not reach themKeep scrollToLoad on, add delayMs, or use pdf for very tall pages.
Run slow or out of memory with many parallel pagesEach parallel page needs browser memoryLower maxConcurrency or raise the run memory.

Limits

  • Up to 1,000 URLs per run, http and https only.
  • PDFs are produced by the browser print engine using the site's print styles, so they can differ from the on-screen look. fullPage and selector don't apply to PDFs.
  • Extremely tall pages may hit browser image-size limits. Try pdf for those.
  • No WebP output, raw-HTML input, custom cookies or headers, proxies or geo-targeting.
  • darkMode changes only sites that support a dark colour scheme.

Support

Is a page not capturing correctly? Open an issue on the Issues tab with the URL and your input.