Complete Website Screenshot Tool — Automated Website Crawler

A simple Actor that crawls a website and captures screenshots of its pages. It starts from a single URL, collects internal links, and generates screenshots for each page up to a configurable limit. Screenshots are stored in Key-Value Store, while metadata about each page can be saved in a Dataset.

Apex Crawler – Screenshotter

Use cases

• Capture screenshots of an entire website for documentation or QA.
• Generate visual snapshots of pages for monitoring or archiving.
• Crawl a site and collect screenshots for design reviews or compliance checks.

🚀 How to use

1. Open the Actor in Apify Console.
2. Enter the website you want to capture in Start URL.
3. Adjust optional settings such as page limit, screenshot format, or proxy.
4. Click Run.

The Actor will crawl the site and generate screenshots of the pages it discovers.

⚙️ Input

The Actor accepts the following configuration:

• startUrl (string, required)
  The website to begin crawling from. Default: https://example.com.

• maxPages (integer, default: 500)
  Maximum number of pages the Actor will process during the crawl.

• viewportWidth (integer, default: 1920)
  Browser viewport width used when capturing screenshots.

• viewportHeight (integer, default: 1080)
  Currently unused. Viewport-based screenshots are still in development.

• fullPageScreenshot (boolean, default: true)
  Capture the entire scrollable page instead of only the visible viewport.

• screenshotFormat (string, default: jpeg)
  Image format for screenshots:

  • jpeg – smaller files (recommended)
  • webp – modern format with better compression
  • png – highest quality but larger files

• pageLoadDelay (integer, default: 30)
  Number of seconds to wait for the page to fully load before taking the screenshot.

• proxyConfig (object)
  Optional proxy configuration to avoid IP blocks during large crawls. Apify Proxy can be enabled by default.

📦 Storage

Key-Value Store – stores the generated screenshot images.

Screenshots themselves are stored in Key-Value Store, while metadata such as page URLs and screenshot references are stored in the Dataset.

Example screenshot filename generated by the Actor:

https://example.com/blog/page1 

url: https://example.com/

viewport:  1920w x 1080h (full screenshots ignore height)

pagepath: blog/page1

screenshotFormat: jpeg (default)

{hostname/url}_{viewportWidth}w{viewportHeight}h_blog_page1-screenshot.jpeg
example_com_1920w1080h_iphone-screenshot.jpeg

The filename includes the hostname, viewport size, and page path so screenshots are organized and easy to identify.

Storage layout:

• Key-Value Store → screenshot image files
• Dataset → structured metadata about each screenshot (WIP)

This separation keeps the actual image files and their structured metadata organized and easy to export.

Output (WIP)

The Actor stores results in two places:

• Key-Value Store – stores the generated screenshot image files.
• Dataset – stores structured metadata about each screenshot.

Example dataset record:

{ "url": "https://example.com", "screenshotKey": "screenshots/page_1.jpeg" }

More Features

Elizaga Applied AI Labs LLC is welcoming new clients and requesting feature requests. If you need a custom built solution OR if you need this run on your machine locally, reach out at: https://www.linkedin.com/company/elizaga-applied-ai-labs or sales-affiliate@elizaga.dev . God bless you!

Notes

• The Actor crawls internal links from the starting URL.
• The number of processed pages is limited by maxPages.
• Using proxies can help avoid IP blocks during large crawls. (WIP)