Responsive Website Screenshot Generator

Generate clean full-page or viewport screenshots of public websites across desktop, tablet, iPhone, iPad, Pixel, and Galaxy presets. Use the visual form with no browser setup, or automate the same workflow through the Apify API, schedules, and integrations.

Use it for responsive QA, SEO evidence, competitor research, landing-page archives, and automated workflows.

Why use this website screenshot generator?

• Responsive device presets: Capture 10 desktop, tablet, and mobile layouts, including iPhone, iPad, Pixel, and Galaxy targets.
• Lazy-loaded content handling: The Actor scrolls full pages, waits for page height to stabilize, and lets images settle before capture.
• Cleaner screenshots: Cookie and consent alerts are hidden by default. You can also hide overlays or provide custom CSS selectors.
• Flexible capture controls: Choose full-page or viewport-only mode, PNG or JPEG, light or dark color scheme, an extra delay, or a print-ready PDF.
• Download-ready outputs: Get individual artifacts, structured Dataset rows, an optional ZIP archive, and run metadata with warnings and failures.
• Built for automation: Run from Apify Console or connect the Actor to API clients, schedules, webhooks, n8n, Make, Zapier, or Google Sheets workflows.

How to generate responsive website screenshots

1. Add one or more public HTTP or HTTPS URLs.
2. Choose the target devices and capture options. By default, every URL is captured as desktop-1440, tablet, and iphone-15.
3. Start the run, then open an individual artifact or download the ZIP archive.

Each URL-target combination produces one requested artifact. For example, two URLs with the three default targets request six screenshots.

Input example

{
  "startUrls": [
    { "url": "https://apify.com/notarobot" }
  ],
  "targets": ["desktop-1440", "tablet", "iphone-15"],
  "format": "png",
  "fullPage": true,
  "hideCookieAlerts": true,
  "hideOverlays": false,
  "autoDomReady": false,
  "zipOutput": true
}

Output

Every requested artifact creates a Dataset row with status, source URL, target, duration, warnings, and a successful download link. PNG, JPEG, and PDF files are stored individually in the run key-value store.

When zipOutput is enabled, successful artifacts are also packaged with metadata.json. The OUTPUT record summarizes successful, failed, and skipped jobs plus billing counts.

{
  "status": "succeeded",
  "url": "https://apify.com/notarobot",
  "target": "iphone-15",
  "artifactKind": "image",
  "filename": "20260728-120000-01-apify-com-notarobot-iphone-15.png",
  "artifactUrl": "https://api.apify.com/v2/key-value-stores/...",
  "durationMs": 8421,
  "warnings": []
}

Pricing and limits

The Actor uses pay-per-event pricing. A capture event is charged only for a successfully generated artifact; failed and skipped captures are not charged. Enabling autoDomReady adds one extra event per successful artifact because it waits for a quiet DOM period.

A single run can request up to 30 files: startUrls.length * targets.length <= 30. For example, 10 URLs with the three default targets produce 30 requested screenshots. See the Pricing tab for current event prices.

Tips and limitations

• Disable Full page when you only need the initial viewport.
• Enable autoDomReady for JS-heavy pages that continue changing after load.
• Use Hide CSS selectors when automatic cookie or overlay cleanup does not cover a page element.
• Only public HTTP and HTTPS pages are supported. Login-protected pages, aggressive bot protection, and unusually long or continuously loading pages may not capture completely.

FAQ

Which targets and formats are supported?

Choose from 10 desktop, tablet, iPhone, iPad, Pixel, and Galaxy presets. Screenshots can be PNG or JPEG; add print-pdf for PDF output. Successful files can also be downloaded together as a ZIP archive.

Can I automate recurring screenshot runs?

Yes. Use Apify schedules, API clients, webhooks, or no-code integrations to run the same saved configuration repeatedly.

Where can I get help?

Open the Issues tab on this Actor page and include the affected URL, target, and relevant run details.