Screenshot & PDF — Reliable Full-Page Capture

Capture full-page or viewport screenshots (PNG/JPEG) and PDFs of any URL — retina, wait-for-selector, cookie-banner hiding, and a per-URL success/failure report. No silent broken images.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Returns one clean, structured row per result. Every row reports its own status so you never get a silent blank.

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "urls": [
    {
      "url": "https://example.com"
    }
  ],
  "format": "png",
  "fullPage": true,
  "device": "desktop",
  "deviceScaleFactor": 2,
  "hideCookieBanners": true,
  "useProxy": false
}

Sample output

[
{
  "result": "example",
  "status": "ok",
  "scrapedAt": "2026-09-03T09:00:00.000Z"
}
]

Typical uses

• Visual monitoring / archiving — schedule daily captures of key pages.
• Thumbnails & previews — retina PNGs for link cards or dashboards.
• PDF snapshots — full-page PDFs of articles, invoices, or receipts.
• QA / design review — capture the same page at desktop and mobile widths.

Pricing

$2.00 / 1,000 results ($0.002 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Screenshot & PDF — Reliable Full-Page Capture declares all 13 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Screenshot & PDF include url, status, httpStatus, key, screenshotUrl and format.
• Screenshot & PDF needs no API key, login or account of any kind before its first run.
• Every one of Screenshot & PDF's 13 inputs is optional, so it runs with no configuration at all.
• Screenshot & PDF documents httpStatus as: HTTP status code returned by the request.
• Every number published about Screenshot & PDF is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Screenshot & PDF is filed under developer tools and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• Screenshot & PDF reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.