Automate website screenshots for monitoring, QA and evidence

Create repeatable screenshots of pricing, products or landing pages with identical viewport, wait and scrolling settings, ready for change comparison or run documentation.

Open the Actor View the input

The first button is an affiliate link. We may receive a commission if you purchase an eligible plan, at no extra cost to you.

Direct answer

How do you generate consistent screenshots across many web pages?

Provide a URL list, choose format, viewport and loading condition, then decide whether to scroll to the bottom. Website Screenshot Generator stores the files in the key-value store for download or downstream workflows.

A screenshot proves what the browser received at that moment, not the site's intent. Keep date, URL, configuration and run ID for context.

Actor: apify/screenshot-url
Published pricing: pay per platform usage
Total Users: 6,9K
Check: August 20, 2026

Actor used

Screenshot Url

Built by Apify. It was selected for adoption, practical utility and a use case not previously covered by FlujoDato.

Check the official listing

3.8 / 520 reviews

6,9Ktotal users

905monthly users

172bookmarks

Public listing signals checked August 20, 2026; they can change.

Copy-ready setup

Capture product and pricing pages with one viewport

{
  "urls": [
    "https://example.com/pricing",
    "https://example.com/product"
  ],
  "format": "png",
  "waitUntil": "networkidle2",
  "delay": 2000,
  "viewportWidth": 1440,
  "scrollToBottom": true,
  "delayAfterScrolling": 2500,
  "selectorsToHide": [
    ".cookie-banner",
    ".chat-widget"
  ],
  "proxy": {
    "useApifyProxy": true
  }
}

01
Fix the viewport
Use one width so visual comparisons remain consistent.
02
Wait for real loading
Try networkidle2 and a short delay on dynamic sites.
03
Hide noise
Remove banners or chat widgets only when they are not part of the evidence.
04
Schedule and retain
Save files with date and URL to build history.

Output and controls

Fields you should review

Field	Use	Check
`PNG / PDF`	Final visual file	Review resolution and full-page coverage
`URL`	Identify the source	Retain the canonical URL
`Run ID`	Audit the execution	Connect it to date and configuration
`viewportWidth`	Repeat framing	Do not mix mobile and desktop
`Key-value store`	Access the file	Set retention or external copy

Cost

Variable cost based on time and resources

The Actor is listed as pay per usage. More waiting, scrolling, resolution and dynamic content use more compute; validate two URLs first.

Component	Published pricing	Check
apify/screenshot-url	pay per platform usage	Confirm current Apify pricing before running at volume.
Recommended pilot	Minimum input	Review quality before scaling

Added value

Problems it helps solve

Evidence

Document a page with reproducible date and configuration.

Visual QA

Check changes after a deployment.

Competitors

Build a history of public prices, messaging and design.

FAQ

Before you automate

Can it capture full pages?

Yes. Enable scrolling and allow enough time for lazy-loaded content.

What about cookie banners?

You can hide them with selectors, but keep them when they are part of what you need to document.

Is the output in the Dataset?

The primary file is stored in the key-value store rather than as a conventional Dataset row.

Visual monitoring

Test two URLs before scheduling

Tune wait, scroll and viewport until the screenshot is stable and repeatable.

Try the Actor