Website Screenshots: phone + desktop, with a mobile-friendly check

Give it a list of websites. For each one you get screenshots at the device sizes you pick, in one dataset row, plus a quick check of how the page behaves on a phone.

Devices

• phone: 390 x 844 (iPhone 14 size), retina (2x), touch, mobile Safari user agent
• tablet: 820 x 1180, 2x, touch
• desktop: 1440 x 900

First screen by default, or the full scrolling page (fullPage, cut at 12,000 px). JPEG (quality 80) or PNG.

Output (one row per website)

• phoneScreenshot, tabletScreenshot, desktopScreenshot: public image URLs (stored in the run's key-value store)
• screenshots: per device: HTTP status, final URL, page title, load time, page height, horizontal overflow in px
• mobileFriendly (true/false) and mobileIssues in plain words: missing viewport tag (page renders as a shrunken desktop page), or content wider than the phone screen (sideways scrolling)

Each page is opened in a fresh browser context (no cookies carried between sites). Three sites are processed in parallel.

Pricing

Pay per event: one screenshot per image saved. On Free or Starter, each screenshot event costs $0.003; on Scale it costs $0.00225; and on Business or Enterprise it costs $0.0015. The default phone + desktop selection saves two images, so one successfully captured site costs $0.006 on Free or Starter, $0.0045 on Scale, or $0.003 on Business or Enterprise. A site that does not load (DNS error, refused connection, certificate error, timeout before anything renders) returns an error row and is not charged. A page whose server answers with an HTTP error (404, 500 and so on) is still captured so you can see what came back, but is not charged (charged: false on that screenshot).

Schedule it or connect it

Run the same website list on a cadence with Apify Schedules, then use webhooks to react when a run finishes. You can also connect this actor from n8n, Make, or Zapier using Apify's integration documentation. Keep your actor input in the schedule or workflow so each run uses the sites and device choices you intend.

Notes

• Cookie and consent banners are hidden before the capture (hideCookieBanners, on by default). They are never clicked, so no consent is given for you. Age gates are not bypassed: the row says ageGate: true and shows what a first-time visitor sees.
• Public pages only; nothing is clicked and no forms are submitted.
• The mobile-friendly check is a layout check (viewport tag + sideways overflow), not a full Lighthouse audit.

FAQ

Can it capture JavaScript-heavy pages? Yes. The actor opens a public page in a browser and waits for its normal page load plus the configured extra wait. Content that needs a login, a user action, or a long-running background request may still be missing.

What happens to cookie banners? With hideCookieBanners on (the default), common cookie and consent banners are hidden before capture. They are not clicked, so the actor does not give consent on your behalf.

Which sites fail or return free rows? Invalid addresses, unreachable sites, robots.txt refusals, private or reserved addresses, bot or checkout interstitials, and HTTP-error pages return an error or uncharged screenshot instead of a paid screenshot event.

Can I use it on any page? Use only public pages you are allowed to access. The actor does not log in, click through gates, submit forms, or bypass access controls.

Example row (real run, full page, phone + desktop)

{
  "url": "https://zingermans.com/",
  "httpStatus": 200,
  "mobileFriendly": true,
  "mobileIssues": [],
  "phoneScreenshot": "https://api.apify.com/v2/key-value-stores/.../records/zingermans-com-phone.jpg",
  "desktopScreenshot": "https://api.apify.com/v2/key-value-stores/.../records/zingermans-com-desktop.jpg",
  "screenshots": [
    { "device": "phone", "width": 390, "loadMs": 2149, "pageHeightPx": 4266, "horizontalOverflowPx": 0, "hasViewportMeta": true },
    { "device": "desktop", "width": 1440, "loadMs": 3902, "pageHeightPx": 1902, "horizontalOverflowPx": 0, "hasViewportMeta": true }
  ]
}