Screenshot Saver

Capture public or authorized web pages as PNG, JPEG, or PDF artifacts. The Actor uses an ordinary headless Chrome session, supports multiple URLs, full-page or element capture, custom viewports and mobile presets, waits, cookies, headers, basic auth, resource blocking, CSS/JavaScript injection, and optional click or hide selectors.

Example input

{
  "urls": [{"url": "https://example.com"}],
  "format": "png",
  "fullPage": true,
  "windowWidth": 1440,
  "windowHeight": 900,
  "waitUntil": "networkidle2"
}

The urls array is required and accepts at most 100 distinct public HTTP(S) URLs per run. Exact duplicates are removed while preserving input order. Localhost, private/link-local/reserved IP ranges, embedded URL credentials, and non-HTTP protocols are rejected before Chrome starts. Use captureSelector to capture one PNG/JPEG element, or mobileEmulation to use a device preset. PDF output captures a page document and cannot be combined with captureSelector.

Example output

Dataset metadata points to the binary artifact in the key-value store:

{
  "timestamp": "2026-08-17T00:00:00.000Z",
  "recordType": "screenshot",
  "found": true,
  "dataAvailable": true,
  "startUrl": "https://example.com",
  "url": "https://example.com/",
  "screenshotUrl": "https://api.apify.com/v2/key-value-stores/STORE/records/screenshot_example",
  "screenshotKey": "screenshot_example",
  "format": "png",
  "contentType": "image/png",
  "artifactSizeBytes": 18452,
  "captureMode": "page",
  "statusCode": 200,
  "pageTitle": "Example Domain",
  "error": false
}

Storage

• Binary PNG, JPEG, or PDF artifacts are stored under individual keys in the default key-value store.
• Metadata rows are written to the default dataset.
• Successful rows use recordType: screenshot, found: true, and dataAvailable: true; failed-request artifacts are explicit diagnostics and never count as successful captures.
• The OUTPUT key-value store record contains recordType runSummary on completion or runDiagnostic on failure.
• Failed navigation requests may still produce a fallback PNG screenshot with error true.

Limits and cost

• URLs are processed sequentially with one crawler worker.
• Navigation can wait up to 120 seconds and request handling up to 180 seconds.
• Large full-page screenshots and PDFs consume more memory and storage than viewport PNGs.
• Apify browser compute, key-value storage, and dataset charges, if applicable to the selected account plan, depend on URL count and artifact size.

FAQ

Does it upload artifacts to an external cloud provider?

No. Screenshot and PDF binaries are stored in the Actor's default Apify key-value store, and their public record URLs are included in dataset rows.

Can I capture authenticated pages?

Only when you are authorized. The input supports HTTP basic auth, cookies, and headers; do not submit credentials or session tokens for pages you do not control.

What happens if navigation fails?

The crawler may preserve a fallback PNG as a diagnostic row with recordType: diagnostic, found: false, dataAvailable: false, and error: true. A run with no successful captures fails so downstream automation cannot mistake an error page for a valid screenshot.

Disclaimer

Use this Actor only for public pages or pages you are authorized to access. Treat injected JavaScript, cookies, headers, and credentials as sensitive. The Actor does not bypass authentication, CAPTCHAs, access controls, or rate limits.