# Website Screenshot API: Mobile Check, Phone and Desktop (`weio/website-screenshot-phone-desktop`) Actor

Bulk phone, tablet and desktop screenshots of URLs you supply (full-page or first-screen; PNG/JPEG), with a mobile-friendly layout check: viewport tag, sideways overflow, HTTP status and load time. Schedule selected sites; each row provides public screenshot URLs for QA or change-review workflows.

- **URL**: https://apify.com/weio/website-screenshot-phone-desktop.md
- **Developed by:** [Weio, Inc.](https://apify.com/weio) (community)
- **Categories:** Developer tools, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 screenshots

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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](https://docs.apify.com/platform/schedules), then use [webhooks](https://docs.apify.com/platform/integrations/webhooks) to react when a run finishes. You can also connect this actor from n8n, Make, or Zapier using Apify's [integration documentation](https://docs.apify.com/platform/integrations). 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)

```json
{
  "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 }
  ]
}
```

# Actor input Schema

## `websites` (type: `array`):

Domains or URLs, one per line (max 1000 per run). A bare domain is opened as https://<domain>/.

## `devices` (type: `array`):

phone = 390x844 (iPhone 14 size, touch, mobile user agent); tablet = 820x1180; desktop = 1440x900. Each device is one screenshot and one charged event.

## `fullPage` (type: `boolean`):

Capture the whole scrolling page instead of the first screen. Very long pages are cut at 12,000 px.

## `format` (type: `string`):

JPEG (quality 80) is much smaller; PNG is lossless.

## `waitMs` (type: `integer`):

Wait after the page loads before the screenshot, for fade-ins and lazy images.

## `hideCookieBanners` (type: `boolean`):

On = cookie/consent banners are hidden before the capture (never clicked: no consent is given). Age gates are not bypassed; the row says ageGate: true.

## Actor input object example

```json
{
  "websites": [
    "zingermans.com"
  ],
  "devices": [
    "phone",
    "desktop"
  ],
  "fullPage": false,
  "format": "jpeg",
  "waitMs": 1500,
  "hideCookieBanners": true
}
```

# Actor output Schema

## `siteRows` (type: `string`):

The default dataset with one row per website.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "websites": [
        "zingermans.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("weio/website-screenshot-phone-desktop").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "websites": ["zingermans.com"] }

# Run the Actor and wait for it to finish
run = client.actor("weio/website-screenshot-phone-desktop").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "websites": [
    "zingermans.com"
  ]
}' |
apify call weio/website-screenshot-phone-desktop --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,weio/website-screenshot-phone-desktop"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1fgQj3RT4i7VzIlj1/builds/cfqdogx9RlwwXFrNW/openapi.json