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

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

---

📤 Output

Each URL produces one dataset item:

{
  "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 screenshotUrls 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. 🔄