Website Screenshot & URL to PDF – Bulk Full Page avatar

Website Screenshot & URL to PDF – Bulk Full Page

Pricing

from $2.50 / 1,000 screenshots

Go to Apify Store
Website Screenshot & URL to PDF – Bulk Full Page

Website Screenshot & URL to PDF – Bulk Full Page

Bulk website screenshots and URL to PDF in one run. Full page or viewport PNG, JPEG or WebP, mobile and tablet views, dark mode, cookie pop-ups hidden. Pay only for successful captures.

Pricing

from $2.50 / 1,000 screenshots

Rating

0.0

(0)

Developer

Kiwi Tools

Kiwi Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Features

Limited permissions

Share

Website Screenshot & URL to PDF – Bulk Full Page Screenshots

Take full page website screenshots or convert URLs to PDF in bulk: paste up to 1,000 links, click Start, and download one PNG, JPEG, WebP or PDF file per page. Mobile and tablet views, dark mode, single-element capture and automatic hiding of cookie pop-ups are built in, and you pay only for files that were actually produced (US$2.50 per 1,000 screenshots, US$3 per 1,000 PDFs).

Try it in one click: the form is prefilled with two public pages, so pressing Start produces two desktop PNG screenshots in under a minute for less than one cent.

What you can use it for

  • Bulk screenshots of a URL list for audits, directories, link previews and thumbnails
  • Full page screenshot archives and before/after records of your own sites or landing pages
  • URL to PDF: save articles, docs, invoices or reports as print-ready PDFs (A4, Letter and more)
  • Responsive checks: how pages look on phones, tablets, laptops and desktops
  • Dark mode screenshots for sites that support a dark theme
  • AI and vision workflows: feed page images to multimodal models, or let an AI agent call this Actor as a tool

Features

  • Bulk: up to 1,000 URLs per run, captured in parallel
  • Formats: PNG (lossless), JPEG and WebP (adjustable quality), or PDF (A4, Letter, Legal, A3, Tabloid; portrait or landscape)
  • Devices: Desktop 1920×1080, Laptop 1366×768, Tablet 768×1024 @2x, phone presets 390×844 @3x and 412×915 @2.625x, or any custom width × height × pixel ratio
  • Full page or just one element (CSS selector), e.g. a chart, a pricing table or a product card
  • Lazy images: optional scroll-through before capturing so lazy-loaded images appear
  • Cookie pop-ups hidden with a built-in ruleset for common consent tools (the overlay is hidden; no consent choice is made)
  • Hide anything else (chat bubbles, promo bars) with your own CSS selectors
  • Dark mode for sites that support it
  • Wait options: load, domcontentloaded or networkidle, plus an extra delay
  • Safe by design: only public http(s) addresses are captured; local, private-network and file: addresses are refused, including after redirects
  • Optional ZIP with all files, and an optional proxy

How it compares

This ActorA typical basic screenshot tool
URLs per runUp to 1,000, in parallelOften one URL per run
OutputPNG, JPEG, WebP and PDFUsually PNG or JPEG only
Full page and single elementBothOften viewport only
Phone and tablet presets, custom pixel ratioYesOften desktop only
Dark modeYesRarely
Cookie pop-upsHidden automaticallyOften visible in the shot
Failed or blocked URLsFree, with a plain-English errorOften still billed
Spending limitRespected before every captureVaries
One row per URL with a direct file linkYesVaries

How to use it

  1. Paste your URLs into URLs (one per line).
  2. Choose an Output format and a Device.
  3. Optionally switch on Full page, set an Element selector, or tweak the loading options.
  4. Click Start. Each file appears in the run's key-value store, and the dataset lists every URL with a direct link to its file.

Example: bulk full page mobile screenshots

{
"urls": ["https://example.com", "https://example.org"],
"format": "jpeg",
"quality": 80,
"device": "iphone",
"fullPage": true,
"scrollToBottom": true
}

Example: URL to PDF

{
"urls": ["https://example.com/blog/post-1", "https://example.com/blog/post-2"],
"format": "pdf",
"pdfFormat": "A4",
"pdfPrintBackground": true
}

Example: capture one element

{
"urls": ["https://example.com/dashboard"],
"format": "png",
"selector": "#sales-chart",
"device": "laptop"
}

Example: dark mode WebP at a custom size

{
"urls": ["https://example.com"],
"format": "webp",
"device": "custom",
"width": 1440,
"height": 900,
"deviceScaleFactor": 2,
"darkMode": true,
"hideSelectors": [".chat-widget", "#promo-bar"]
}

Use it from your code, an AI agent or a no-code tool

Replace <YOUR_API_TOKEN> with your token from Apify Console → Settings → API & Integrations.

HTTP API (one call, waits for the results):

curl -X POST "https://api.apify.com/v2/acts/kiwitools~website-screenshot-pdf/run-sync-get-dataset-items" \
-H "Authorization: Bearer <YOUR_API_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"urls": ["https://example.com"], "format": "png", "fullPage": true}'

Python (pip install apify-client):

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("kiwitools/website-screenshot-pdf").call(
run_input={"urls": ["https://example.com", "https://example.org"], "format": "pdf"}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["url"], item["ok"], item["fileUrl"])

JavaScript / Node.js (npm install apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('kiwitools/website-screenshot-pdf').call({
urls: ['https://example.com', 'https://example.org'],
format: 'png',
device: 'iphone',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => console.log(item.url, item.fileUrl));

No-code and AI tools: run it from Make, Zapier or n8n with Apify's official integrations (Make, Zapier, n8n), give it to an AI agent through the Apify MCP server, or run it on a timetable with schedules and get notified with webhooks. See also the Python client and JavaScript client docs.

Input

FieldTypeDefaultDescription
urlsarray of strings(required)Public URLs to capture, max 1,000. https:// is added if missing.
formatpng · jpeg · webp · pdfpngOutput format.
qualityinteger 1–10085JPEG/WebP quality.
devicedesktop · laptop · tablet · iphone · android · customdesktopViewport preset.
width, heightinteger1280, 800Custom viewport in CSS px (only with custom).
deviceScaleFactornumber 0.5–31Custom pixel ratio (only with custom).
fullPagebooleanfalseCapture the whole page height (capped, see Limits).
selectorstring–Capture only the first element matching this CSS selector (images only).
waitUntilload · domcontentloaded · networkidleloadWhen the page counts as loaded.
delayMsinteger 0–300000Extra wait before capturing.
scrollToBottombooleanfalseScroll through the page first to trigger lazy images.
hideCookieBannersbooleantrueHide common cookie/consent pop-ups.
hideSelectorsarray of strings–Extra CSS selectors to hide.
darkModebooleanfalseRequest the site's dark theme (prefers-color-scheme: dark).
pdfFormatA4 · Letter · Legal · A3 · TabloidA4PDF paper size.
pdfLandscapebooleanfalseLandscape PDF.
pdfPrintBackgroundbooleantrueInclude background colours and images in PDFs.
pdfUseScreenMediabooleanfalseUse on-screen styles instead of the print stylesheet.
timeoutSecsinteger 5–18060Time limit per URL.
maxConcurrencyinteger 1–103Pages captured in parallel (about 1 GB memory per 2 pages).
skipHttpErrorsbooleantrueDon't capture or charge for pages answering HTTP 4xx/5xx.
zipOutputbooleanfalseAlso store ALL_CAPTURES.zip with every file (free).
proxyproxy settingsoffOptional proxy. Proxy traffic is billed by the platform separately.

Output

Files go to the run's default key-value store, named like shot-0001-example-com.png or pdf-0002-example-org-pricing.pdf.

Dataset: one row per URL (index is the position in your input list):

{
"index": 0,
"url": "https://example.com",
"finalUrl": "https://example.com/",
"httpStatus": 200,
"title": "Example Domain",
"fileKey": "shot-0001-example-com.png",
"fileUrl": "https://api.apify.com/v2/key-value-stores/<storeId>/records/shot-0001-example-com.png",
"format": "png",
"width": 1920,
"height": 1080,
"pages": null,
"bytes": 80185,
"truncated": false,
"captureMethod": "viewport",
"capturedAt": "2026-10-18T09:51:45.619Z",
"charged": true,
"blockedRequests": 0,
"durationMs": 1240,
"ok": true,
"error": null
}

Failed rows have "ok": false, "charged": false and a plain-English error such as Timed out after 60 s, Page returned HTTP 404 or Rejected URL: Address 10.0.0.1 is not a public IP.

Pricing

This Actor uses pay-per-event pricing. You are charged only after a file has been saved:

EventPriceWhen it is charged
screenshotUS$0.0025 per image (US$2.50 per 1,000)A PNG, JPEG or WebP file was saved
pdfUS$0.003 per PDF (US$3.00 per 1,000)A PDF file was saved
Actor startsmall platform start feeOnce per run
  • Not charged: URLs that fail, time out, are refused by the safety check, return an HTTP error (with skipHttpErrors on), or are skipped.
  • Spending limit: set Maximum cost per run in the run options. The Actor checks it before every capture and stops cleanly when the limit is reached; the remaining URLs are listed as skipped (not charged).
  • The price already includes the compute the capture needs. Optional proxy traffic is billed separately by the platform.
  • You can try it on the Apify Free plan; charges are taken from your plan's monthly usage credit.

Limits and good to know

  • Page height is capped at 20,000 CSS px (and 32,000 device pixels; 16,383 px for WebP, a format limit). Taller pages are cut at the cap and marked "truncated": true.
  • On a few very heavy pages the browser's one-shot full-page capture stalls; the Actor then reloads the page and stitches viewport tiles together ("captureMethod": "stitched"). Fixed headers appear once at the top.
  • No logins: the Actor does not accept cookies, sessions or passwords, so pages behind a login can't be captured.
  • Cookie pop-ups are hidden, not answered. Some sites redirect to a separate consent page instead of showing a pop-up; that page is what gets captured.
  • Some sites block automated browsers or show a CAPTCHA. The Actor does not try to bypass such protections.
  • PDFs use the browser's print engine, so sites with a print stylesheet look different from the screen; switch on pdfUseScreenMedia to use screen styles.

Responsible use

Only submit URLs you have the right to capture, and respect the terms of the websites you capture and any copyright in their content. This Actor visits each URL once, like a normal browser; it does not crawl links. It is an independent tool and is not affiliated with or endorsed by any website it captures.

FAQ

How much does it cost? US$0.0025 per saved screenshot (US$2.50 per 1,000) and US$0.003 per saved PDF (US$3 per 1,000), plus a tiny platform start fee per run. Failed, blocked and skipped URLs are free. You can try it on the Apify Free plan using its monthly usage credit.

Can I take a full page screenshot of a long page? Yes. Switch on Full page. Pages up to 20,000 CSS px tall are captured whole; taller pages are cut at the cap and marked "truncated": true.

How do I take bulk screenshots of many URLs? Paste up to 1,000 URLs, one per line, or pass them as the urls array through the API. Use several runs or a schedule for bigger lists.

Can I convert a URL to PDF? Yes. Set Output format to PDF and pick the paper size and orientation. Switch on PDF uses screen styles if the site's print layout looks wrong.

Can I take mobile screenshots? Yes. Choose a phone or tablet preset, or a custom width, height and pixel ratio.

Why did a URL fail with "Rejected URL"? The safety check only allows public internet addresses. localhost, private networks (10.x, 192.168.x, etc.), cloud metadata addresses and file: links are always refused.

Can it capture pages behind a login? No. The Actor does not accept cookies, sessions or passwords, and it does not bypass CAPTCHAs or bot protection.

Can I call it from my own code or an AI agent? Yes. Use the API snippets above, the official integrations, or the Apify MCP server. The input schema describes every option.

Where are my files, and are they public? Files live in your run's key-value store and follow your storage settings and retention, like any other run output. Each dataset row links to its file, and the optional ZIP bundles them all.

Something went wrong. How do I get help? Open an issue on the Issues tab of this Actor with the run ID and the URL that failed.