Verified node on n8n
SnapRender for n8n
SnapRender for n8n is a verified community node that turns any public web page into a PNG, JPEG, WebP or PDF file inside a workflow, reads pages as Markdown for AI steps, and captures up to 50 pages in one batch. Install it from the nodes panel on n8n Cloud or self-hosted, add your API key once, and send the files to Google Drive, Gmail, Slack or any other node.
200 free captures a monthNo cardn8n Cloud and self-hosted
Sheets to DriveRan end to end
Read URL rows
Google Sheets
Loop over URLs
Loop Over Items
Capture screenshot
SnapRender · Screenshot > Take
Full Page: on · Output: Binary
Captured?
If
-
true
Upload to Drive
Google Drive
falseMark row failed
Edit Fields
Write result to sheet
Google Sheets
What the node does
11 operations in 4 resources. Version 0.2.6 and later group them by resource, as below. Earlier versions show the same operations in one Operation list, under the name in grey.
Screenshot
Pages to image and PDF files
- Take Take Screenshot
- A page to a PNG, JPEG, WebP or PDF file on the item's binary data, ready for Drive, Gmail, Slack or S3. Or a base64 data URI in JSON.
- Create Batch Batch Screenshots
- Up to 50 pages in one job with the same settings. Returns a job ID right away.
- Get Batch Status
- Progress of a batch job and a download link for each page, valid 24 hours.
- Sign URL No capture used
- An expiring link that shows a fresh screenshot of the page when opened, for emails, sheets and chat messages. Creating it is free.
- Check Cache No capture used
- Whether a copy of the page is already cached, and when it expires.
Account
Plan and usage
- Get Usage No capture used
- Captures used and left this month, for a check before a large run.
Content
Pages to text for AI steps
- Extract Extract Content
- The page as Markdown, plain text, HTML, the main article, its links or its metadata. Scope it to a CSS selector or cap its length.
Webhook
Events sent to your URL
- Create Create Webhook No capture used
- Send events to a URL, such as an n8n Webhook node: a finished batch, 80% of the month's captures used, or all of them used.
- Get Many List Webhooks No capture used
- The webhooks on your account, one item each.
- Test Test Webhook No capture used
- A test delivery to check that the receiving workflow works.
- Delete Delete Webhook No capture used
- Removes a webhook by its ID.
Screenshot > Take options
- Format: PNG, JPEG, WebP or PDF
- Full Page: the whole scrollable page
- Device: iPad Pro, iPhone 14, iPhone 15 Pro, MacBook Pro, Pixel 7
- Dark Mode: the page's dark theme where it has one
- Block Ads and Block Cookie Banners: on by default
- Output: a binary file, or a base64 data URI in JSON
- Additional Options: width 320 to 3,840 px, height, delay, quality, CSS selectors to hide or click
- Create Batch and Sign URL take the same capture options.
Install the node and connect your key
You need a SnapRender account (free) and an n8n instance where you are the owner or an admin. Members can use the node once it is installed.
n8n Cloud and self-hosted
From the nodes panel
- On the canvas, open the nodes panel with + or the N key.
- Search SnapRender. It shows under More from the community.
- Open it and select Install. Every member of the instance can then use it.
Self-hosted only
From Settings
- Open Settings > Community Nodes and select Install.
- Enter the package name:
n8n-nodes-snaprender
- Tick the risk notice and select Install. This installs the latest release from npm.
Once per instance
Connect your API key
- Sign up with Google, GitHub or email and copy the key from the API keys page. It starts with
sk_live_. - Add a SnapRender node and choose Create new credential under SnapRender API.
- Paste the key and save. n8n tests it with a usage check.
Workflows we ran end to end
Each one ran with real accounts before it went on this page: real captures, real Drive uploads, real emails and AI answers. The nodes are listed in order, with the settings that matter.
-
8 nodes · 1 capture per URL
Screenshot a Google Sheets list of URLs to Google Drive
Turn a sheet of URLs into full-page screenshots in a Drive folder, with the file link, a status and the time written back next to each URL. Rows that already have a link are skipped, so you can run it again whenever the list grows. Agencies use it for client reports, SEO and QA teams for site audits.
- Tested: Run on a 6-row sheet: 5 pages landed in Drive with their links written back to the right rows, and a domain that does not exist got failed with the reason.
- Manual Trigger Run by hand, or swap in a Schedule Trigger
- Google Sheets Read the URL rows
- Filter Keep rows with a URL and no link yet
- Loop Over Items One URL at a time
- SnapRender Screenshot > Take
- If Captured, or failed with a reason
- Google Drive Upload the PNG
- Google Sheets Write link, status and time to the row
SnapRender: Format PNG, Full Page on, Output Binary, and the node setting On Error set to Continue, so a dead URL writes
failed: reasonto its row and the loop moves on. Sheet header row:url, screenshot_link, status, captured_at. -
8 nodes · 1 capture per page per run: 5 pages a day is about 150 a month
Email a screenshot digest every morning or every Monday
One email with a fresh screenshot of every page you watch: competitor pricing pages each morning, or all your client homepages once a week for the report. You see price, offer and layout changes without opening each site.
- Tested: Run with 3 pages: all 3 arrived in Gmail with a preview image and a download link each. The batch links stay valid for 24 hours, so add a Google Drive step to keep the images.
- Schedule Trigger Every day at 8:00, or every week
- Edit Fields (Set) Your list of up to 50 URLs and the recipient
- SnapRender Screenshot > Create Batch
- Wait 30 seconds
- SnapRender Screenshot > Get Batch Status
- If Finished? If not, back to Wait
- Edit Fields (Set) Build the HTML email
- Gmail Send the digest
Keep the list as an array field, such as
urls, in the first Edit Fields step. Create Batch: URLs (JSON Array) ={{ JSON.stringify($json.urls) }}, Width 1440 and Full Page off. Whole-page images of long pages run tens of thousands of pixels tall and make the email hard to read; link them instead. Failed pages are listed in the email with the reason. -
10 nodes · 3 captures per submission
Keep a PDF record of a page each time a form is sent
When someone accepts your terms, signs up or sends a consent form, keep what the page showed at that moment: a full-page PDF with a SHA-256 fingerprint, a phone screenshot, the page text and a row in Google Sheets. A record-keeping aid for SaaS teams and agencies, not legal advice.
- Tested: Run with a real form post: the PDF and the iPhone PNG landed in Drive, the row was logged, and the SHA-256 in the sheet matched the Drive file byte for byte. A post without page_url got the 400 reply.
- Webhook Your form or backend sends page_url, email and reference
- If No page_url? Answer 400
- SnapRender Screenshot > Take
- Crypto SHA-256 fingerprint of the PDF
- Google Drive Save the PDF
- SnapRender Screenshot > Take
- Google Drive Save the phone screenshot
- SnapRender Content > Extract
- Google Sheets Append the log row
- Respond to Webhook Return the links and the fingerprint
PDF step: Format PDF, Full Page on, Block Ads and Block Cookie Banners off, so the record matches what the visitor saw. Phone step: Device iPhone 15 Pro. Extract: Extraction Type Plain Text.
-
6 nodes · 1 capture per review, plus the AI provider's own charge
Review any page with OpenAI or Claude from one form
Paste a URL into an n8n form and get an AI review of the page as a visitor sees it: visual QA before a launch, a summary of a competitor's offer and pricing, or an answer to your own question. One setting picks OpenAI or Anthropic.
- Tested: Run with both providers (gpt-5 and Claude Sonnet 5.5) and all three review types: visual QA, competitor page summary and a custom question.
- n8n Form Trigger Page URL and review type
- Edit Fields (Set) Pick the provider and the prompt
- SnapRender Screenshot > Take
- Switch OpenAI or Anthropic
- OpenAI or Anthropic Analyze the image
- Form Show the review on the result page
SnapRender: Format JPEG, Width 1440, Height 1800, Quality 80. The analyze node reads the image from the binary property
data. Give reasoning models room: at 1,500 output tokens gpt-5 spent them all on reasoning and returned empty text, so the workflow allows 8,000.
The only setup is an API key
Sign up free, copy the key from your dashboard and paste it into the SnapRender API credential in n8n.
200 captures a month free, no card. Every plan includes the n8n node.
Good to know
How the node behaves inside a workflow, so runs go the way you expect.
The file is in
Screenshot > Take puts the file on the binary property data, nameddatascreenshot.png(or .jpg, .webp, .pdf). Point the Drive, Gmail, Slack or AI node at data.Batches run in the background
Create Batch returns a job ID at once. Loop Wait and Get Batch Status until the status is completed, as in the digest workflow. Each page gets a download link valid for 24 hours.Keep a loop going past errors
Set the node's On Error to Continue and a failed page returns anerrorfield with the reason instead of stopping the run, so an If node can mark it and move on.Errors say what went wrong
Recent versions show SnapRender's own error, such asTARGET_UNREACHABLE: The target website could not be reached, so the execution log tells you what to fix.Free steps
Check Cache, Get Usage, the webhook operations and creating a signed link use no captures. Failed captures are not counted either.Page changes without a timer
SnapRender scheduled captures compare each capture with the last one and sendchange.detectedto a webhook, such as an n8n Webhook node. The Slack guide shows the setup.
SnapRender plans
The node is included in every plan, from free to $9 and up. Each screenshot, extraction or batch page uses one capture.
| Plan | Price a month | Captures a month |
|---|---|---|
| Free | $0 | 200 |
| Starter | $9 | 2,000 |
| Growth | $29 | 10,000 |
| Business | $79 | 50,000 |
| Scale | $199 | 200,000 |
Yearly billing costs ten months of the monthly price. All plans.
Questions
What is the SnapRender n8n node?
SnapRender for n8n is a verified community node, n8n-nodes-snaprender, that adds the SnapRender screenshot API to your workflows. It turns any public web page into a PNG, JPEG, WebP or PDF file on the item's binary data, reads pages as Markdown or text, runs batches of up to 50 pages, creates signed screenshot links and manages webhooks.
Does it work on n8n Cloud?
Yes. n8n verified the node, so it installs from the nodes panel on n8n Cloud and on self-hosted instances: search SnapRender and install it from More from the community. Only instance owners and admins can install nodes; members use them once installed.
Why do my operation names differ from this page?
Version 0.2.6 and later group the operations by resource, such as Screenshot > Take. Earlier versions, and nodes added to a workflow with them, show one Operation list with names such as Take Screenshot. Both run the same calls, and workflows built with either keep working after an update.
Can I use an HTTP Request node instead?
Yes. The node is a shortcut for the REST API, so an HTTP Request node with your key in an X-API-Key header works too. The morning change check guide builds a full workflow that way, with built-in nodes only.
What does it cost?
The node is free and included in every SnapRender plan: Free $0 for 200, Starter $9 for 2,000, Growth $29 for 10,000, Business $79 for 50,000, Scale $199 for 200,000 captures a month. Each screenshot, extraction or batch page uses one capture. Failed captures, cache checks, usage checks, webhook steps and creating a signed link use none. n8n counts its executions separately.
Can a workflow capture pages behind a login?
It captures public pages. If your own site shows a security check instead of the page, one firewall rule lets SnapRender through: see allow SnapRender on your site.
Where does my API key go?
n8n stores it as a SnapRender API credential, encrypted with your instance's key, and the node sends it only to app.snap-render.com. Saving the credential runs a usage check, so a wrong key shows up right away. To revoke access, delete or rotate the key in your dashboard.