Overview
The Capture Website Screenshot block takes a screenshot of any webpage and returns a hosted image URL. Use it for visual documentation, competitor monitoring, design reviews, or feeding images to AI for visual analysis.
Configuration
URL
Enter the URL of the webpage to capture. This field supports placeholders for dynamic URLs.
Examples:
- Static URL:
https://example.com/landing-page
- From search results:
{{step_1.output.organic[0].link}}
- From sitemap:
{{current}}
Screenshot Type
Choose how much of the page to capture.
| Type | Description | Best For |
|---|
| Full Page | Captures the entire scrollable page from top to bottom | Complete page documentation, long-form content |
| Viewport | Captures only the visible area (above the fold) | Hero sections, initial load appearance, faster capture |
Default: Full Page
Wait Time (Optional)
Time to wait before capturing the screenshot, in milliseconds.
Use wait time when:
- Page has animations that need to complete
- Content loads dynamically after initial page load
- Lazy-loaded images need time to appear
- JavaScript renders content after page load
Examples:
| Wait Time | Use Case |
|---|
| 1000 (1 second) | Simple animations |
| 2000 (2 seconds) | Dynamic content loading |
| 5000 (5 seconds) | Heavy JavaScript applications |
Start without wait time. Add it only if screenshots are missing expected content.
Output
The block returns a URL string pointing to the captured screenshot image.
Output Example
https://storage.example.com/screenshots/screenshot_a1b2c3d4.png
Accessing the Screenshot
Get screenshot URL:
Use in HTML:
<img src="{{step_n.output}}" alt="Screenshot" />
Use in Markdown:

Using Screenshots with AI
Screenshots can be passed to LLM blocks that support vision capabilities for visual analysis.
Example prompt for LLM block:
Analyze this website screenshot and describe:
1. The overall design style
2. Key visual elements
3. Call-to-action placement
4. Color scheme used
Screenshot: {{step_2.output}}
Best Practices
- Use Viewport for faster captures when you only need above-the-fold content
- Add wait time for JavaScript-heavy sites that load content dynamically
- Combine with Loop block to capture screenshots of multiple pages
- Use Full Page for complete documentation of long pages
- Test on a single URL before running bulk screenshot workflows
Common Use Cases
| Use Case | Configuration Tips |
|---|
| Competitor monitoring | Full Page, capture landing pages weekly |
| Design documentation | Full Page, capture before/after changes |
| Visual regression | Viewport, compare hero sections over time |
| Content archiving | Full Page, save visual record of pages |
| AI visual analysis | Viewport or Full Page, pass to vision-capable LLM |
| Social proof collection | Viewport, capture testimonial sections |
Example Workflow: Competitor Visual Analysis
Capture and analyze competitor landing pages:
-
Google Sheets Block: Read list of competitor URLs
-
Loop Block: Process each URL
-
Capture Website Screenshot Block:
- URL:
{{current.url}}
- Type: Viewport
- Wait Time: 2000
-
LLM Block: Analyze screenshot for design patterns
-
Google Sheets Block: Store URL, screenshot link, and analysis
Example Workflow: Page Archive
Create visual archives of your website pages:
-
Get URLs from Sitemap Block: Extract all page URLs
-
Loop Block: Process each URL
-
Capture Website Screenshot Block:
- URL:
{{current}}
- Type: Full Page
-
Google Sheets Block: Log URL and screenshot URL with timestamp
Troubleshooting
| Issue | Cause | Solution |
|---|
| Missing content | Page loads dynamically | Add wait time (2000-5000ms) |
| Blank screenshot | Page blocked or requires auth | Check if page is publicly accessible |
| Partial content | Lazy loading not triggered | Increase wait time |
| Timeout error | Page too slow to load | Simplify URL or check site availability |
| Wrong content | Dynamic URL not resolved | Verify placeholder syntax |
What’s Next
Now that you understand the Capture Website Screenshot block: