How to Screenshot a Website in n8n
n8n has no native screenshot or HTML-to-image node, and running headless Chromium inside your instance is fragile. There are two real ways to render a page in a workflow: the Verified Rendex node or a raw HTTP Request node. Here’s which to use, and why.
Last updated: August 2026
The two approaches
Rendex community node
RecommendedA dedicated Rendex node with a Screenshot resource. Add it on n8n Cloud in one click, pick a credential, choose Capture, and pipe the binary result into Drive, Slack, or Gmail. Renders HTML, a URL, or Markdown to PNG/JPEG/WebP/PDF, supports batch and async, ships a Watch page-change trigger, and is usable as an AI Agent tool.
Best for: almost everyone.
HTTP Request node
Call a rendering API directly from n8n’s built-in HTTP Request node. You set the URL, the Authorization header, the JSON body, and the response format yourself, then decode the binary by hand. No community-node install required.
Best for: locked-down instances that forbid community nodes, or hitting an endpoint the node doesn’t expose.
Node vs HTTP Request, side by side
| Rendex node | HTTP Request node | |
|---|---|---|
| Setup | One-click add on n8n Cloud | Manual request config |
| Auth | Credential picker, tested on save | Hand-set Bearer header |
| Binary output | Native n8n binary, ready to use | Decode base64 yourself |
| HTML / Markdown → image or PDF | Build the JSON body by hand | |
| Batch, async + webhooks | Wire polling / callbacks manually | |
| Rendex Watch (page-change trigger) | ||
| Usable as an AI Agent tool | ||
| Works on a no-community-nodes instance | ||
| Hit an endpoint the node doesn't expose |
Both call the same Rendex API and bill the same render credits — the difference is how much plumbing you own.
Screenshot a URL with the Rendex node
- 1. On n8n Cloud, search “Rendex” in the nodes panel and add it (one click). On self-hosted, install
n8n-nodes-rendexfrom Settings → Community Nodes. - 2. Add a Rendex API credential and paste your
rdx_key — n8n verifies it on save. - 3. Set Resource Screenshot, Operation Capture, Source URL, and Format PNG.
- 4. Wire the binary output into any node — Google Drive, Slack, Gmail, or an HTTP call.
Full walkthrough on the n8n setup guide, and ready-made flows on the n8n integration page.
Frequently asked questions
- How do I take a screenshot of a website in n8n?
- The simplest way is the Verified Rendex community node. On n8n Cloud, search "Rendex" in the nodes panel, add it in one click, pick Screenshot then Capture, set the source to a URL, and the rendered PNG arrives as binary data ready for the next node. No headless browser, no Code node. Alternatively, you can call a rendering API from a raw HTTP Request node, but you handle the request, auth, and binary decoding yourself.
- Does n8n have a built-in screenshot node?
- No. n8n has no native screenshot or HTML-to-image node, and running headless Chromium inside your n8n instance is fragile and resource-heavy. The Rendex community node fills that gap by rendering on Rendex's edge and returning the file as binary data.
- Can I just use the HTTP Request node instead of a community node?
- Yes. Any rendering API is reachable from n8n's HTTP Request node, and it's the right choice on a locked-down instance that forbids community nodes, or when you want to hit an endpoint the node doesn't expose. The trade-off is manual setup: you configure the URL, headers, auth, and response format yourself, and decode binary output by hand. The Rendex node does all of that for you and is usable as an AI Agent tool.
- Is the Rendex n8n node free?
- The node itself is free and open. Rendering usage runs on your Rendex plan, which starts free at 100 renders/month with no credit card.
- Does the Rendex node work on n8n Cloud?
- Yes. Rendex is a Verified Community Node on n8n Cloud — it appears in the in-app nodes panel and installs in one click, instance-wide. It also installs on self-hosted n8n from Settings then Community Nodes.
Render a page in n8n in under a minute
Verified on n8n Cloud. One-click add, one credential, binary output. Start free with 100 renders a month.
Related Use Cases
See how Rendex solves specific rendering problems.
Render Images & PDFs Inside Your n8n Workflows
Drop the official Rendex node into any n8n workflow to turn HTML into images, screenshot live URLs, render Markdown to a PDF, or mint a hosted og:image link. The output flows straight into Gmail, S3, Slack, or any downstream node — no Function-node glue. The same node can even schedule a page-change Watch that fires back into n8n when a page moves.
Give Your AI Agent Eyes on the Web
Rendex ships a Model Context Protocol (MCP) server built from day one for AI agents. Claude, ChatGPT, Cursor, and Windsurf can capture screenshots, generate PDFs, and render HTML — as native tools.
Render HTML Charts, Tables & Reports to PNG from Your Backend
Generate report deliverables server-side: send your HTML chart or financial table, get back a crisp 2× PNG, and drop it straight into the PDF or report your app already produces. One HTTP call from any language — no Chromium to install, no browser fleet to keep alive.
Explore More Comparisons
See how Rendex compares across the screenshot API landscape.