Bulk Website Screenshot Capture

Capture public HTML pages as desktop and mobile PNGs with a downloadable manifest. Each requested URL, viewport and mode gets a result with the final URL, time, image link and completion status.

Use it for agency reports, landing-page reviews, public website release checks, product-page evidence and multi-location website audits. The same input format works across industries: supply the pages you want to inspect.

Start a capture

{
  "urls": ["https://example.com"],
  "viewports": ["desktop", "mobile"],
  "modes": ["viewport"],
  "wait_ms": 500
}

Input	Options
urls	1–25 public HTML URLs
viewports	desktop (1440 × 900), mobile (390 × 844), or both
modes	viewport, full_page, or both
wait_ms	Additional readiness wait, 0–3,000 milliseconds; default 500

Each viewport/mode combination is a separate capture. One URL with both viewports and both modes requests four captures. A mobile preset uses a mobile viewport and touch context; it is not a claim of testing every physical mobile device.

Output

The default dataset includes a capture row for each combination and a final exports row linking to CAPTURES.json through manifest_url and CAPTURES.csv through csv_manifest_url. Each usable image is stored as a PNG with a download link in image_url.

Use the CSV manifest for recurring agency reports, location reviews or spreadsheet imports. It contains only capture results: one row per requested combination, including duplicates, failures and partial captures. Join on the zero-based input_index, filter status, and use image_url for the saved image. Network counters have separate network_* columns; multiple reasons remain a JSON array in one cell. Missing values remain blank. The UTF-8 CSV includes a byte-order mark for spreadsheet compatibility and prefixes formula-like text with an apostrophe; the JSON manifest preserves original text. Creating the CSV does not add a success event.

Manifest fields include input_index, input_url, final_url, viewport, mode, width, height, page_height, http_status, status, reasons, image_url, fetched_at and elapsed_seconds. Exact duplicate combinations within a run reference the prior capture instead of producing a new success event.

complete indicates that the capture passed the included response, readiness and image checks. partial indicates clipping, resource failures or incomplete readiness; its image may still be useful for review. blank, blocked, timeout, failed, unsupported_content and size-limit statuses explain inputs that did not produce a usable complete image.

Blank and challenge detection are conservative heuristics. A complex challenge page, login form, cookie modal or another obstruction may escape detection. This Actor does not promise a perfect visual interpretation of the page or certify an image as legal evidence.

Pricing unit

One success event is one complete URL × viewport × mode capture. The current rate is shown in the Pricing tab. Desktop plus mobile equals two success units when both complete. Repeated combinations, recognized blank/blocked images, failed requests, timeouts and partial captures do not add success events.

Included scope and limits

• 30 seconds per capture, including page retrieval, readiness and image creation.
• Up to 10,000 pixels of full-page height and 10 MB per PNG. Taller pages are clipped, marked partial and have no success event.
• Full-page mode retains the preset viewport width. Horizontal overflow is reported as partial.
• Up to 100 resource requests and 20 MB of resource data per capture, with a 2 MB cap per resource. Large or resource-heavy pages can be partial.
• Fresh anonymous browser contexts, public HTTP/HTTPS destinations and standard web ports.

The renderer blocks streaming media, downloads, non-GET requests, private destinations, background workers and realtime connections. Cookies or API keys supplied by users, login sessions, user-configured proxies and challenge bypass are unsupported. Interactive applications that require these behaviors may be incomplete. Images retain ordinary popups and cookie notices; the Actor does not click them automatically. Fonts or images that are still loading can make a result partial.

Large batches also remain subject to the platform's run output and request limits. Start with the pages and viewport you actually need, then add another viewport when it serves your reporting or review task.

Repeatable workflows

Save one task per client, campaign, site release or location list. Keep viewport and mode settings stable when comparing captures over time. The manifest can feed a report builder, while the Shopify or WooCommerce catalog tools can supply a list of product-page URLs for capture.

For a source-specific problem, provide its public URL, viewport/mode settings and run ID. Include the returned reason so a partial image is not confused with a completed capture.

Price and run controls

The launch price is $10 per 1,000 completed units ($0.01 per event), as defined above. Check the current Pricing tab before running. Status and duplicate rows do not add this custom event. Set a maximum charge appropriate for your batch; a run stops when its event budget is exhausted. RUN-SUMMARY records actual accepted events and execution totals.

Automatic replay of an interrupted run is disabled to prevent duplicate charges. Keep the available output, then start a new run for a new execution. A later run is a new billable execution. Completed dataset rows and individually saved files remain available when a budget stops a run. Combined exports, manifests, and snapshots assembled at the end may be absent after a budget stop or interruption; use a sufficient run budget when you need those aggregate files. The initial release uses documented input limits and public source access; external source changes can require maintenance.