Website Screenshot & PDF Archive Generator avatar

Website Screenshot & PDF Archive Generator

Pricing

$3.00 / 1,000 captures

Go to Apify Store
Website Screenshot & PDF Archive Generator

Website Screenshot & PDF Archive Generator

Capture full-page website screenshots or PDFs and build a weekly competitor page archive with Apify Schedules. Get dated file links and hashes, with stable capture settings. $3 per 1,000 successful captures; failed captures are not billed.

Pricing

$3.00 / 1,000 captures

Rating

0.0

(0)

Developer

Erzia

Erzia

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Categories

Features

Limited permissions

Share

Weekly competitor page archive and visual monitoring

Save competitors' pricing, landing and product pages every week, then compare the dated images across runs. Each dataset row includes capturedAt, the file's sha256, and a download link. Download the files with the dataset manifest for a long-term archive; Apify retention settings still apply.

Create an Actor task with your competitor URLs, then add it to Apify Schedules. For example, choose UTC and cron 0 9 * * 1 to capture every Monday at 09:00 UTC. Reuse the same device, format, selectors and input each week. No schedule is created by this example.

At $3 per 1,000 successful captures, 20 pages weekly × 4 weeks = 80 captures/month = $0.24 in capture charges, with no start fee. A month with five scheduled Mondays costs 100 × $0.003 = $0.30. Any separately applicable Apify plan, storage or integration fees depend on your account.

Capture full-page screenshots or PDFs of any list of URLs in one run. Choose desktop, laptop, tablet or mobile, hide cookie banners and pop-ups, wait for the content you need. You pay only for successful captures: $3 per 1,000.

What it's for

  • Weekly competitor archive: schedule captures of competitors' pricing pages, landing pages or your own site.
  • Archiving and compliance: keep dated PDFs or images of pages, terms and ads as evidence.
  • QA and design review: check how pages look on mobile, tablet and desktop in one run.
  • Reports and previews: generate thumbnails for link previews, catalogs or client reports.

Quick start: a weekly page archive

  1. Add one public page URL, choose desktop PNG and keep fullPage and stableCapture enabled.
  2. Run and inspect ok, fileUrl, capturedAt and stabilizationNotes. Download the file and export the dataset manifest.
  3. Save the checked configuration as a task. In Apify Schedules, add the task, select UTC and use 0 9 * * 1 for Mondays at 09:00. Enable the schedule and verify its next run.
{
"urls": [{"url": "https://apify.com/pricing"}],
"device": "desktop",
"format": "png",
"fullPage": true,
"stableCapture": true,
"delaySeconds": 1
}

For a PDF task, change format to pdf; PDFs always include the full page. Saving a task does not create a schedule. Visual comparison and permanent file storage are separate steps.

How it works

  1. Add URLs (paste or upload a file).
  2. Pick a device (desktop 1920×1080, laptop 1366×768, tablet, mobile) and a format (png, jpeg or pdf).
  3. Optional: capture the full page, wait for a CSS selector, add a delay for animations, or hide elements such as cookie banners (#cookie-banner, .popup).
  4. Run. Every capture is saved to the run's key-value store, and the dataset gets a row with a direct file link.

stableCapture defaults to true: CSS animations and transitions are disabled with an injected stylesheet, the Actor waits for document.fonts.ready within the configured timeout, and scrolls to the top. Each device has a fixed deviceScaleFactor (desktop/laptop/tablet: 1; mobile: 2). Optional maskSelectors paint dynamic elements black while preserving their layout, for both images and PDFs. hideSelectors remove elements from layout instead. Set stableCapture: false to disable the animation/font/scroll steps.

Stabilization is best effort: failed styles, font waits or scrolling do not fail a capture. If CSP blocks an injected stylesheet, the Actor tries the same rules through element style attributes; unsupported or blocked rules are skipped. This fallback cannot style pseudo-elements. CSP remains enforced. Any degraded step is reported in stabilizationNotes, and successful captures are billed as usual.

These settings reduce visual noise. They do not freeze JavaScript timers, video, live data or third-party content. PDF metadata can also affect file hashes. A different hash means the file bytes changed; it does not necessarily mean the visible page changed.

On a timeout or network error from page.goto, navigation is retried once using waitUntil: "domcontentloaded" and 1.5 times the configured timeout. HTTP failures, selector failures and screenshot/storage errors are not retried. HTTP 4xx/5xx pages are reported as failed and are not billed. For HTTP 403/429/503, captcha, cloudflare or access denied in the title/body identifies a block page. This is a heuristic; it does not bypass protection or guarantee detection of every challenge.

The dataset view shows image previews, so you can scan results at a glance and export the list to Excel, CSV or JSON.

Output

FieldExampleMeaning
urlhttps://example.comURL you provided
oktrueCapture succeeded
status200HTTP status of the page
finalUrlhttps://example.com/URL after redirects
titleExample DomainPage title
format, devicepng, desktopCapture settings
sizeBytes18211File size
fileUrlhttps://api.apify.com/v2/key-value-stores/.../records/screenshot-1Direct link to the file
errornullWhy a capture failed
attempts1Navigation attempts, either 1 or 2
errorTypenullFailure class: timeout, dns, http_4xx, http_5xx, blocked_or_captcha, other; null on success
stabilizationpartialfull when all stabilization steps completed, partial when a step failed, fell back or was not reached, off when stableCapture: false; independent of capture success
stabilizationNotes["csp_blocked_stylesheet"]Short notes about degraded steps; empty array if none. Optional mask/hide failures are also reported when stabilization is off
capturedAt2026-11-08T09:00:00.000ZUTC capture timestamp (failure timestamp on failed rows)
sha256<64 lowercase hex characters>SHA-256 of the exact stored file bytes; null on failure

Illustrative selected fields only. Store/file identifiers and the zero hash are placeholders, not downloadable output or measured data.

{
"url": "https://apify.com/pricing",
"ok": true,
"status": 200,
"format": "png",
"device": "desktop",
"fileUrl": "https://api.apify.com/v2/key-value-stores/ILLUSTRATIVE_STORE/records/ILLUSTRATIVE_FILE",
"capturedAt": "2026-11-09T09:00:00.000Z",
"sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"error": null,
"stabilization": "full",
"stabilizationNotes": []
}

Pricing

Pay per event, no subscription and no start fee:

EventPrice
Successful screenshot or PDF$0.003 ($3 per 1,000)

Failed pages are not billed. Examples: 20 competitor pages captured weekly over four weeks = 80 captures = $0.24; one-off capture of 1,000 product pages = $3.00.

Input example

{
"urls": [{ "url": "https://apify.com/pricing" }],
"device": "mobile",
"format": "png",
"fullPage": true,
"hideSelectors": ["#cookiebanner"],
"stableCapture": true,
"maskSelectors": [".live-clock", ".rotating-banner"],
"waitForSelector": "main",
"delaySeconds": 1
}

FAQ

Can I get a PDF instead of an image? Yes, set format to pdf. PDFs always include the full page.

How long are files kept? Files live in the run's key-value store and follow your Apify data retention settings. Download or move them to your storage if you need them longer.

Can it capture pages behind a login or CAPTCHA? No. It does not log in, solve CAPTCHAs or bypass bot protection. Pages that block automated browsers may fail or show their block page.

Can I run it on a schedule? Yes. Save a task and configure Apify Schedules separately. For long-term archives, download each fileUrl and export the dataset manifest before retention expires. API, webhooks or automation integrations can support a separate transfer workflow; no Drive upload, Slack notification or visual-change alert is configured by this Actor.

Monitor new Google Play reviews daily with a separate app-review workflow. Google Play Reviews & App Data Scraper.

API access

Use the Actor API examples to pass explicit input and retrieve results. UI prefills are not API inputs.

Use with AI agents

Connect an MCP-compatible client to https://mcp.apify.com?tools=actors,erzia/website-screenshot. Inspect Actor details and pricing before running. Pass the full quick-start input explicitly. Read the dataset after the run; starting an Actor does not create a recurring schedule. Authentication and any task/schedule setup are separate. Guide: https://docs.apify.com/mcp

Support

Open an issue on the Issues tab with the run link, affected URL, device, format and selector settings. Include stabilizationNotes for inconsistent captures.