How to Capture Website Screenshots in Clay
Capture live websites or historical pages in Clay with ScreenshotAPI.net and the Wayback Machine, then automate clean screenshots with ScreenshotNeo.
Direct answer: Clay documents two screenshot workflows. For current pages, copy Clay’s screenshot template, connect a Clay table to ScreenshotAPI.net through an HTTP API column, add the URLs, and run the table. For historical pages, copy Clay’s Wayback Machine template; it finds archived versions at six-month intervals up to two years ago and returns archive URLs and screenshots.
Use the live workflow when you need a current view of a supplied URL. Use the Wayback workflow when you need to compare how a page looked in the past. Clay’s Chrome extraction and Clip to Clay tools save or extract page data; they are separate from screenshot generation.
1. Capture current website screenshots in Clay
Step 1: Copy the screenshot template
Open Clay’s screenshot template directory and copy the website screenshot template into a workspace. New users are prompted to create a free Clay account. The template provides a table structure for URLs and an HTTP API column.
Step 2: Create the screenshot API connection
- Create a ScreenshotAPI.net account if you do not already have one.
- Copy the API key from that service.
- Open the template’s HTTP API column and paste the key where the template requests it.
- Keep the URL field mapped to the column that contains the page address.
Clay’s tutorial describes ScreenshotAPI.net as free and says plans start at $9 per month. That is a dated vendor claim in the tutorial, not a verified current price; check the provider before budgeting.
Step 3: Add the URLs
Put one fully qualified URL in each row, including https://. For a company list, create a URL column from company names or LinkedIn profiles, then review the generated addresses before sending them to the screenshot column. A bad URL produces a bad capture regardless of the API.
Step 4: Run the HTTP API column
Run the column for a sample row first. Confirm that the result is an image URL or image value, then run the remaining rows. Save the returned value in a separate column if you need to pass screenshots to later Clay steps.
What this live workflow is useful for
- Competitor and market-page reviews
- Campaign and landing-page tracking
- Fit and targeting research
- Error reports that include a visual record
- Content and design reference collection
- Evidence collection for an internal review process
A screenshot records what was rendered at capture time. It does not, by itself, prove that a site meets a legal or compliance requirement.
2. Capture historical website screenshots with Clay’s Wayback template
Step 1: Copy the Wayback Machine template
Copy Clay’s Wayback Machine template into your workspace. Enter a homepage, pricing page, product page, or another public URL.
Step 2: Let the archive lookup finish
The documented template looks for archived versions approximately six, twelve, eighteen, and twenty-four months earlier. It returns archive URLs and screenshots when those snapshots exist. Archive coverage is not guaranteed for every date or page.
Step 3: Wait before summarizing
Clay’s instructions call out a 40-second delay while Archive.org loads screenshots. Wait for the screenshot fields to complete before running the Claygent summary. Running the summary early can leave it without the visual data it needs.
Step 4: Review the comparison
The template describes summaries of changes in pricing, positioning, and messaging. You can edit or add timestamps when you need a different historical range. Treat each result as an archived snapshot: a page may have changed between captures, or an archive may have missing assets.
3. Live pages versus archived pages
| Question | Live screenshot workflow | Wayback workflow |
|---|---|---|
| What page age? | Current version at the supplied URL | Archived versions, typically six-month intervals up to 24 months in the template |
| Main dependency | Clay account plus ScreenshotAPI.net account and API key | Archived availability through the Wayback Machine |
| Input | URLs in a Clay table | A page URL and requested historical range |
| Timing | Depends on the HTTP API request and page load | Clay documents a 40-second screenshot delay |
| Best for | Current monitoring and list-based capture | Historical comparison and change review |
4. Building a reliable Clay table
- Normalize URLs: Store canonical HTTPS URLs and remove accidental whitespace.
- Validate a sample: Run five or fewer rows before processing a large list.
- Keep source columns: Preserve the company name, source URL, final URL, capture result, and error text.
- Separate retries: Retry failed rows after checking the URL instead of rerunning every successful row.
- Record capture time: Current screenshots become stale; a timestamp makes later comparisons meaningful.
- Expect dynamic content: Cookie dialogs, login walls, bot checks, and client-rendered sections can change what appears in a capture.
5. Common errors and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Every row fails authentication | The API key is missing, pasted into the wrong field, or revoked. | Re-enter the key in the HTTP API column and test one row. |
| Only some rows fail | Those URLs are malformed, redirect differently, or are unavailable. | Open the exact URL in a browser, normalize it, and retry only failed rows. |
| Blank or partial image | The page depends on JavaScript, loads slowly, or blocks automated requests. | Check the provider’s rendering options and retry after the page is reachable. Do not assume a blank image proves the page is blank. |
| Historical screenshot is missing | Archive.org has no snapshot near the requested date or did not save required assets. | Try another timestamp or use the nearest available archive URL. |
| Claygent summary misses visual changes | The summary ran before screenshot fields finished. | Wait for the documented capture delay and run the summary afterward. |
| Wrong company page captured | A generated URL from a name or LinkedIn profile resolved to an unrelated domain. | Review and approve the URL column before running the screenshot column. |
| Rate or usage limit reached | The provider account limit was exceeded. | Process in smaller batches, remove duplicate URLs, and check the provider’s current plan. |
6. Performance, reliability, and cost considerations
Performance
Large tables take longer because each row requires a page load and image response. Start with a small sample, then process batches. Historical captures have the explicit 40-second delay documented by Clay. Current-page timing varies with redirects, JavaScript, images, and the provider’s queue.
Reliability
Record failures separately and retry them after inspection. A screenshot can differ between runs because of personalization, geolocation, experiments, consent state, or content loaded after the initial HTML. Archived pages add another dependency: the requested snapshot and its assets must exist.
Cost
Clay usage and the screenshot provider’s usage are separate concerns. The tutorial’s $9/month ScreenshotAPI.net starting price may be stale, so verify current plans. Avoid duplicate captures and test your table mapping before running a large list.
7. When Clay’s other page tools are the right choice
Use Clay for Chrome when the goal is extracting structured data from an individual page or list. Use Clip to Clay when the goal is saving an entire webpage into a Clay table. Use the screenshot templates when you need a visual rendering. Clay documents ZenRows as a web-scraping integration with URL input, JavaScript rendering, HTML output fields, proxy country, and anti-bot settings; that documentation presents it as an extraction option, not as the screenshot workflow described here.
8. Or skip the browser setup
For a direct screenshot API, ScreenshotNeo accepts one GET request and returns a PNG, JPEG, WebP, or PDF. The API can capture full pages, a CSS-selected element, a device preset or custom viewport, dark mode, retina output, and pages that need a wait condition. It also supports custom CSS and JavaScript, clicks, hidden selectors, blocked requests, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, webhooks, bulk capture, and a usage API.
Before the capture, ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo API documentation for the complete option list.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes 1,000 screenshots a month free with no card. Paid plans start at $5 for 3,000 shots, and every feature is available on every plan. Create a free ScreenshotNeo account.
9. FAQ
Can Clay screenshot a list of company websites?
Yes. Put the website URLs in a Clay table and run the ScreenshotAPI.net HTTP API column. Clay’s tutorial suggests generating a URL column from company names or LinkedIn profiles, followed by a review of the results.
How far back does the Wayback template look?
The documented template checks six, twelve, eighteen, and twenty-four months earlier. You can edit or add timestamps for another range, subject to archive availability.
Why does the historical workflow take so long?
Clay documents a 40-second delay while Archive.org loads screenshots. Wait for those fields before running a summary.
Does a screenshot prove regulatory compliance?
No. It is visual evidence of a rendered page at a point in time. Compliance conclusions require the applicable policy, records, and review process.
Can I use Clip to Clay for screenshots?
Clip to Clay saves entire webpages to Clay tables. Clay documents it separately from the screenshot API workflow, so use the screenshot template when you need rendered image files.
