What does Screenshot & PDF — Reliable Full-Page Capture return?

It returns 13 documented output fields: url, status, httpStatus, key, screenshotUrl, format, fullPage, width, height, deviceScaleFactor, bytes and tookMs. Each field declares its type, a description of what it holds, and an example value. The remaining 1 are listed in the output schema below.

What input does Screenshot & PDF — Reliable Full-Page Capture require?

urls is required. A further 12 inputs are optional. The full input schema, with types and defaults, is below.

Does Screenshot & PDF — Reliable Full-Page Capture need an API key or login?

No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.

How do I run Screenshot & PDF — Reliable Full-Page Capture?

It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.

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.

Screenshot & PDF — Reliable Full-Page Capture returns 13 documented output fields, including url, status, httpStatus, key and screenshotUrl. Every field carries a declared type, a written description and an example value. 50 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription

13: Output fields
13: Inputs
50: Runs
2026-10-16: Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

Field	Type	What it holds	Example
url	stringnull	The URL this row describes.	https://example.com/pricing
status	stringnull	Outcome recorded for this row.	ok
httpStatus	integernull	HTTP status code returned by the request.	200
key	stringnull	Key this record is stored or deduplicated under.	<key>
screenshotUrl	stringnull	Link to a screenshot captured for this record.	<screenshotUrl>
format	stringnull	Format of this record.	<format>
fullPage	booleannull	Full Page as recorded for this row.	true
width	numbernull	Width in pixels.	0
height	numbernull	Height in pixels.	0
deviceScaleFactor	numbernull	Device Scale Factor as recorded for this row.	0
bytes	integernull	Size in bytes.	0
tookMs	integernull	Time the operation took, in milliseconds.	0
error	stringnull	Why this row failed, when it did. Null on success.	<error>

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "url": "https://example.com/pricing",
  "status": "ok",
  "httpStatus": 200,
  "key": "<key>",
  "screenshotUrl": "<screenshotUrl>",
  "format": "<format>",
  "fullPage": true,
  "width": 0
}

03 — input

What you give it

Input	Type	Description
urls	arrayrequired	Pages to capture, one per line (with or without https://).
format	stringoptional	png (lossless), jpeg (smaller), or pdf (whole page).
fullPage	booleanoptional	Capture the entire scrollable page (on) or just the viewport (off). PDF is always full page.
device	stringoptional	Preset viewport: desktop, laptop, tablet, mobile. Overridden by explicit width/height.
width	integeroptional	Custom viewport width in px (1–5000). Overrides the device preset.
height	integeroptional	Custom viewport height in px (1–5000).
deviceScaleFactor	integeroptional	2 or 3 gives crisp HiDPI/retina images at the cost of larger files.
quality	integeroptional	1–100, only for jpeg.
waitForSelector	stringoptional	Wait until this CSS selector appears before capturing (e.g. '#main'). Failing to find it is reported as a failed capture, not a blank image.
waitMs	integeroptional	Additional wait before capture, for animations or late content (max 30000).
hideCookieBanners	booleanoptional	Hide common cookie/consent overlays before capturing.
useProxy	booleanoptional	Route through a proxy for sites that block datacenter IPs.
maxItems	integeroptional	Hard limit on captures. Strictly enforced — never charged beyond it.

04 — run

Run Screenshot & PDF on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

Also in developer tools, automation

05 — questions

Asked before running it

13 of 13 fields described

What does Screenshot & PDF — Reliable Full-Page Capture return?: It returns 13 documented output fields: url, status, httpStatus, key, screenshotUrl, format, fullPage, width, height, deviceScaleFactor, bytes and tookMs. Each field declares its type, a description of what it holds, and an example value. The remaining 1 are listed in the output schema below.
What input does Screenshot & PDF — Reliable Full-Page Capture require?: urls is required. A further 12 inputs are optional. The full input schema, with types and defaults, is below.
Does Screenshot & PDF — Reliable Full-Page Capture need an API key or login?: No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
How do I run Screenshot & PDF — Reliable Full-Page Capture?: It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.