Website Screenshot Generator: URL to PNG, JPEG or WEBP

Capture a public web page as a PNG, JPEG or WEBP image: any viewport size, full page, retina scaling, optional cookie-banner hiding.

What it does

Capture a public web page as a PNG, JPEG or WEBP image: any viewport size, full page, retina scaling, optional cookie-banner hiding. It runs in seconds, needs no login and no API key of your own, and can process up to 1000 items in one run (batch mode).

Examples:

• Inline page (no network): 640x360 PNG: {"url": "data:text/html,<h1>v&oslash;iddo</h1>", "width": 640, "height": 360}
• Full-page WEBP of a public site: {"url": "https://example.com", "full_page": true, "format": "webp", "quality": 80, "block_cookie_banners": true}

Input

Field	Type	Required	Description
url	string	yes	Public http(s) URL (robots.txt is honoured), or an inline data:text/html URL
width	integer	no	Viewport width in CSS px
height	integer	no	Viewport height in CSS px
full_page	boolean	no	Capture the whole scrollable page (capped at 16384 CSS px / 50 megapixels)
format	select	no	File format of the result. Allowed: png, jpeg, jpg, webp.
quality	integer	no	jpeg / webp quality
delay_ms	integer	no	Extra wait after load, before the shot
device_scale_factor	string	no	Pixel density (2 = retina) (a number)
block_cookie_banners	boolean	no	Hide common cookie-consent dialogs (best effort)
items	array	no	Optional. A list of input objects with the same fields as above; every object is processed in its own right and the top-level fields act as shared defaults. Leave empty to process the single input above (up to 1000 items per run).

Example input:

{
  "url": "https://example.com"
}

Output

Each processed item adds one row to the dataset with file_url (a link to the generated file in the run's key-value store), filename, mime, bytes, credits and ms. The file itself is stored under the key shown in file_key. A failed item adds a row with error and status instead; the run fails only when every item failed.

Limits

• Up to 30 seconds per item.
• Input size up to 120,000 bytes per item.
• URLs must be public http(s) addresses; private and local addresses are refused, robots.txt is respected where pages are fetched.
• No logins, no captcha solving, no personal-data lookups.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Pricing

You pay per successfully processed item (the current price is on the Pricing tab). A failed item is not charged.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/url-screenshot").call(run_input={"url": "https://example.com"})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/url-screenshot').call({"url": "https://example.com"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~url-screenshot/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/url-screenshot",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account or an API key?

No key of your own. You only need an Apify account to start the actor.

How many items can one run process?

One item from the fields above, or up to 1,000 in items (batch mode). Each item becomes one row in the dataset.

How am I charged?

Per successfully processed item, at the price on the Pricing tab for your Apify plan. A failed item is not charged, the platform usage of the run is included, and your spending limit for a run is always respected.

Where are the results?

Every row links to its file (file_url) in the run's key-value store; the rows themselves export as JSON, CSV or Excel from the Output tab or the API.

Can I run it on a schedule or from another tool?

Yes. Save the input as a task and schedule it in the Apify Console, or start it from Make, Zapier, n8n, a webhook or the API calls above.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link, or write to data@voiddo.com.

Other ways to use it

The same engine is also available as an API at https://data.voiddo.com and as browser tools at https://utils.voiddo.com.

Support

Questions or a case that does not work: data@voiddo.com. We answer within one business day.