# Full-Load Screenshot (`caleno/full-load-screenshot`) Actor

Full-page screenshots that wait for every image, font and lazy-loaded element to render — no more blank or half-loaded images.

- **URL**: https://apify.com/caleno/full-load-screenshot.md
- **Developed by:** [Caleno](https://apify.com/caleno) (community)
- **Categories:** Automation, Developer tools, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $50.00 / 1,000 screenshot per urls

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Full-Load Screenshot 📸

**Full-page website screenshots that actually wait for every image, font and lazy-loaded element to render — no more blank or half-loaded pages.**

Most screenshot tools fire the camera too early: hero images are still blank, lazy-loaded pictures never appear, fonts pop in a moment later, and animated sections show up empty. **Full-Load Screenshot** fixes that. It fully loads the page first — every image, `srcset`, `<picture>`, CSS background, web font and scroll-revealed section — and only then captures a pixel-perfect screenshot.

***

### ✨ What it does

- 🖼️ **Waits for every image to load** — lazy-loaded, `srcset`, `<picture>`, CSS backgrounds and late-injected images included. Reports exactly how many images rendered.
- 📜 **Full-page or viewport** capture at any resolution (retina / HiDPI supported).
- 🍪 **Removes cookie / consent banners** so they don't cover your content (works with the common consent tools, iframes and shadow DOM).
- 🧩 **Per-section screenshots** (optional) — a separate image for each section: header, hero, forms, content blocks and footer. Works on any page layout.
- 🎬 **Reveals scroll animations** so no section is left blank, and gives videos a visible frame.
- 🗂️ **PNG or JPEG** output, with public image URLs you can use straight away.

***

### 🎯 Use cases

- Visual QA and change monitoring for websites and landing pages
- Portfolio / gallery thumbnails of client sites
- Archiving pages exactly as they render
- Feeding pixel-perfect screenshots into design, AI or reporting pipelines
- Grabbing individual sections (hero, pricing, footer) as separate assets

***

### 📥 Input

| Field | Description |
|-------|-------------|
| **URLs** | One or more page URLs to capture. |
| **Full page** | Capture the whole scrollable page, or just the viewport. |
| **Viewport width / height** | Browser size (default 1440×900). |
| **Pixel density** | 1 = normal, 2 = retina (sharper, larger files). |
| **Image format** | PNG (lossless) or JPEG (smaller). |
| **Remove cookie / consent banners** | Automatically dismiss cookie popups (default on). |
| **Per-section screenshots** | Also capture each page section as its own image. |
| **Extra settle time** | Extra wait for slow animations or late scripts. |
| **Proxy** | Optional proxy configuration. |

#### Example input

```json
{
  "urls": ["https://example.com/"],
  "fullPage": true,
  "format": "png",
  "removeCookieBanners": true,
  "sectionScreenshots": false
}
```

***

### 📤 Output

Each URL produces one dataset item:

```json
{
  "url": "https://example.com/",
  "screenshotUrl": "https://api.apify.com/v2/key-value-stores/.../records/screenshot-001-example.com.png",
  "imagesLoaded": 42,
  "imagesTotal": 42,
  "allImagesLoaded": true,
  "pageWidth": 1440,
  "pageHeight": 5230,
  "format": "png",
  "loadSeconds": 6.4,
  "sectionsCount": 8,
  "sections": [
    { "label": "header", "screenshotUrl": "...", "width": 1440, "height": 66 },
    { "label": "hero",   "screenshotUrl": "...", "width": 1440, "height": 720 }
  ]
}
```

The screenshots are stored in the run's key-value store and the returned `screenshotUrl`s open directly in a browser.

***

### ⚙️ How it works

The actor opens the page in a real Chromium browser, forces lazy images to load, scrolls the full height to trigger every lazy loader, waits until all images are decoded and fonts are ready, snaps scroll-reveal animations to their final state, and then captures the screenshot. That is why the result has no blank or half-loaded images.

***

### 💳 Pricing

Simple **pay per URL**: one flat price per page, no matter how many images it contains or how many sections you capture — the full-page screenshot and every section image are all included. Failed URLs are free.

***

### ❓ Notes

- Company logos and stylized graphics are images, not text — screenshots capture them exactly as shown.
- Extremely tall pages fall back to a safe capture mode automatically.

Questions or a feature request? Open an issue on the actor page — the actor is actively maintained. 🔄

# Actor input Schema

## `urls` (type: `array`):

One or more page URLs to capture. Each URL is fully loaded (all images, fonts and lazy content) before the screenshot is taken.

## `captureMode` (type: `string`):

📄 Full page = one screenshot of the whole page. 🖥️ Visible area = only the first screen (viewport). 🧩 Full page + sections = the whole page PLUS a separate image for each section (header, hero, forms, blocks, footer).

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

PNG for lossless quality, JPEG for smaller files.

## `removeCookieBanners` (type: `boolean`):

Automatically dismiss the cookie/consent popup on every site so it doesn't cover your content — handles the common consent tools, iframes and shadow DOM.

## `viewportWidth` (type: `integer`):

Browser width. 1440 matches a typical desktop.

## `viewportHeight` (type: `integer`):

Browser height (used before the page is scrolled).

## `deviceScaleFactor` (type: `integer`):

1 = normal, 2 = retina / high-resolution (sharper, larger files).

## `jpegQuality` (type: `integer`):

Only used when the format is JPEG (1–100).

## `waitAfterLoadSecs` (type: `integer`):

Extra wait after everything has loaded, for slow animations or late scripts.

## `sectionSelectors` (type: `array`):

Only for the 🧩 Full page + sections mode: extra CSS selectors to capture as their own section screenshots (e.g. .pricing-table).

## `maxSecondsPerUrl` (type: `integer`):

Hard time limit for a single page. A URL that exceeds this is skipped (and never charged).

## `startUrls` (type: `array`):

Alternative URL input in the standard Apify request-list format. Useful when chaining this actor to another actor's output.

## `proxyConfiguration` (type: `object`):

Optional proxy configuration for downloading pages (e.g. for geo-specific content).

## Actor input object example

```json
{
  "urls": [
    "https://en.wikipedia.org/wiki/Cat"
  ],
  "captureMode": "fullpage",
  "format": "png",
  "removeCookieBanners": true,
  "viewportWidth": 1440,
  "viewportHeight": 900,
  "deviceScaleFactor": 1,
  "jpegQuality": 85,
  "waitAfterLoadSecs": 1,
  "maxSecondsPerUrl": 120,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "urls": [
        "https://en.wikipedia.org/wiki/Cat"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("caleno/full-load-screenshot").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 = { "urls": ["https://en.wikipedia.org/wiki/Cat"] }

# Run the Actor and wait for it to finish
run = client.actor("caleno/full-load-screenshot").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 '{
  "urls": [
    "https://en.wikipedia.org/wiki/Cat"
  ]
}' |
apify call caleno/full-load-screenshot --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,caleno/full-load-screenshot"
        }
    }
}

```

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/ah038lL9Bz1Lng1sr/builds/LDAdmpcXD7b3OwklZ/openapi.json