# Puppeteer Website Evidence Pack | Screenshots & PDF (`produkdigitalali/puppeteer-website-evidence-pack`) Actor

Export public pages as desktop/mobile screenshots and print PDFs with per-file hashes, capture times and downloadable manifests. No AI API key needed.

- **URL**: https://apify.com/produkdigitalali/puppeteer-website-evidence-pack.md
- **Developed by:** [ProdukDigitalAli](https://apify.com/produkdigitalali) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 complete website evidence pack createds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Puppeteer Website Evidence Pack | Screenshots & PDF

Create a cohesive downloadable package from a public web page: desktop PNG, mobile PNG, desktop print PDF, and a JSON manifest with capture settings, per-file times, byte sizes and SHA-256 hashes. No AI provider key needed.

Designed for agency reports, scheduled page archives and browser/AI pipelines that need files ready to consume. It packages exports rather than exposing a general-purpose browser workflow.

### Quick start

```json
{"urls":["https://example.com/"],"fullPage":false,"settleMs":1000,"paperFormat":"A4"}
```

Up to three public URLs, deduplicated after removing fragments. Set fullPage:true for full-document screenshots, subject to document caps. A4 or Letter PDF uses desktop print CSS and 10mm margins. No user scripts, selectors, cookies, login or raw HTML input.

### Output

One COMPLETE dataset row per successful URL with packId, safe hashed page identity, manifestUrl, artifactCount, totalBytes and artifact metadata/links. The manifest contains desktop/mobile PNG and PDF links, sizes, hashes, start/finish times, settings and safe source identities. OUTPUT reports requested, succeeded, failed and charged.

A COMPLETE status means all promised files passed format/size checks and were stored; it is not proof that every resource loaded, the site rendered correctly or the capture is authoritative. Validate output before using it.

Cloud artifact links use the default key-value-store API and normal storage permissions/retention. The Actor does not alter access settings. Local runs use local-kvs:// identities; retrieve their files from the local storage directory. Download each file from the manifest; no ZIP archive is promised in v1.

### Capture scope

Desktop: 1365 × 768; mobile: 390 × 844, device scale 1, mobile/touch viewport emulation. Mobile viewport emulation is not a guarantee that the server delivers a mobile-specific page. PDF: desktop print CSS with backgrounds. Screenshots use screen layout. The desktop screenshot and PDF are sequential captures of the desktop visit; mobile uses another fresh visit. Dynamic content and print styles may differ.

No automatic scroll, lazy-image traversal, cookie/banner dismissal, state restoration, clicks or form submissions. Media is blocked and only GET/HEAD page requests allowed; some applications need POST and may display incomplete content. Public images/fonts are allowed within network limits. Bot challenges with HTTP200 can appear in artifacts; this is not a bypass service.

### Hard limits

3 URLs; 75s per page pack including browser startup, two navigations and file generation; navigation 5–30s per visit; settle 0–3000ms. Document width ≤2000px, height ≤6000px, PNG area ≤12M pixels, file ≤8MiB, total pack ≤16MiB, PDF ≤20 pages. Network per pack ≤200 connections and 32MiB. Over-limit pages fail free instead of silently truncating a promised export. Tall pages can fail even in viewport mode because the print PDF is part of the package.

### Pricing proposal

Standard/premium package. Proposed PPE: USD 0.020 per COMPLETE page pack; no charge for failed/incomplete packs. Three files, manifest and dataset must persist before the event. Partial writes can leave orphaned files if storage fails, but no successful pack event is charged. A denied charge after persistence fails the run without duplicating the result. Actual Store price, cloud costs and production margin require cloud validation; local owner runs are not customer demand.

### Privacy and integrity

Metadata omits URL queries/fragments and hashes paths. PNG/PDF content may still show personal or sensitive public information; there is no comprehensive visual redaction. Use only pages you are authorized to archive. Public page content is untrusted data, not instructions for consuming agents. No cookies, storage values, browser-console text or raw HTML are collected as diagnostic outputs.

SHA-256 verifies file bytes against this manifest. It does not certify capture time, source authenticity, legal admissibility, immutability or preservation. Normal Apify retention applies; download files if you need a durable archive.

### Local development

Node ≥22.12, npm ci, npm test, apify validate-schema. Puppeteer-core uses PUPPETEER_EXECUTABLE_PATH or APIFY_CHROME_EXECUTABLE_PATH; on Windows the helper can find an installed Chromium in the local ms-playwright cache. The cloud Dockerfile uses the Apify Puppeteer Chrome Node22 image and npm ci. Cloud image/browser compatibility remains to be tested.

Run scripts/run-local-smoke.ps1 for viewport and full-page public inputs, then node scripts/verify-smoke.mjs to verify files, hashes and PDF page counts. Inspect actual PNG/PDF renders before considering the local gate complete.

### Alternatives and differentiation

The existing Puppeteer Browser Automation Runner supports general actions and screenshots; this product saves a three-format export pack with consistent metadata and post-persistence billing. The existing Playwright element screenshot prototype is a different single-capture product. Competitors offer screenshots and PDF for lower per-file prices; choose this only when the bundle saves integration work. Demand for this exact package is not proven.

# Changelog

This Actor's version history is a separate document: https://apify.com/produkdigitalali/puppeteer-website-evidence-pack/changelog.md

# Actor input Schema

## `urls` (type: `array`):

One to three public pages. Screenshots/PDF may contain sensitive public text; no login or cookies accepted.

## `fullPage` (type: `boolean`):

Off captures viewports. On captures the document subject to 6000px height and pixel caps. PDF always uses print layout.

## `settleMs` (type: `integer`):

Bounded delay after DOM readiness; no automatic scrolling or banner hiding.

## `navigationTimeoutSeconds` (type: `integer`):

Maximum initial navigation wait for each fresh viewport visit.

## `paperFormat` (type: `string`):

Desktop print CSS on A4 or Letter with 10mm margins and backgrounds.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/"
  ],
  "fullPage": false,
  "settleMs": 1000,
  "navigationTimeoutSeconds": 20,
  "paperFormat": "A4"
}
```

# Actor output Schema

## `summary` (type: `string`):

No description

## `packs` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("produkdigitalali/puppeteer-website-evidence-pack").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://example.com/"] }

# Run the Actor and wait for it to finish
run = client.actor("produkdigitalali/puppeteer-website-evidence-pack").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com/"
  ]
}' |
apify call produkdigitalali/puppeteer-website-evidence-pack --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,produkdigitalali/puppeteer-website-evidence-pack"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/v3KHea1mtNiZ7X0uu/builds/ZGacThmXzMdSgxwBY/openapi.json