To create website screenshot thumbnails in n8n, use an HTTP Request node to send a page URL to a browser screenshot service, then save or pass its image response to the next node. n8n orchestrates the workflow; the browser service renders the page and returns the screenshot. Browserless documents this pattern for n8n, including binary-image and base64 response handling.
Build a basic screenshot workflow
- Add a trigger. Start with a Manual Trigger while you build and test. Later, replace it or add a Schedule Trigger, Webhook, or content-event trigger to capture pages automatically.
- Add an HTTP Request node. Set the method to
POSTand the URL tohttps://production-sfo.browserless.io/screenshot. Add a query parameter namedtokenand supply your Browserless API token using an n8n credential rather than embedding it in a shareable workflow. - Set the body to JSON. Send the target page URL and screenshot options. For example:
{ "url": "https://example.com", "options": { "fullPage": false, "type": "webp" } }Browserless documents PNG, JPEG, and WebP output; PNG is the default, and the example uses
fullPageandtypeinsideoptions. Consult its Screenshot API reference for supported options. If sending inline HTML instead of a URL, do not include a URL in the same request. - Choose how n8n handles the response. For a normal file handoff, configure the HTTP Request node to receive the image as binary/download data. Use base64 only when a following node needs JSON or text; it is larger and less convenient for ordinary file handling. Browserless’s n8n guide describes both approaches.
- Send the image to its destination. Connect a storage, upload, or forwarding node and map the binary output from the HTTP Request node. Test with a page you can access and confirm the downstream file opens as the expected format.
Choose thumbnail framing and output
Viewport capture or full page
For a conventional thumbnail, capture the initial viewport by setting fullPage to false. This keeps the result focused on the page’s first screen. Set it to true when the entire page is the intended preview; the resulting image can be much taller than a typical thumbnail, so check whether the destination will resize or crop it.
As an Amazon Associate I earn from qualifying purchases.
Image format
Choose PNG when you want the documented default, or select JPEG or WebP using the documented type option. Check what the destination accepts and whether your workflow expects the corresponding file format. Browserless’s screenshot example demonstrates writing the raw response bytes directly to an image file.
Page readiness
A page that has not finished rendering can produce a blank or incomplete capture, especially when content loads dynamically. Browserless advises waiting for elements to load before capturing. Use the endpoint’s documented wait-related options as appropriate for the target page, and avoid assuming that a successful HTTP response means all visible content has finished loading. See the BrowserQL screenshots guide.
#1 Best Overall
Keep the workflow reliable and manageable
- Protect the token. Store it in n8n Credentials or protected environment configuration; do not leave it in a workflow template that may be shared.
- Allow for slow pages. Set a suitable HTTP Request timeout and retry policy. A retry can help with a transient slow load, but it will not fix a consistently inaccessible page or an insufficient wait for dynamic content.
- Choose a nearby endpoint. Browserless documents regional endpoints in SFO, London, and Amsterdam. Select one close to the n8n workflow to reduce network distance; this is a configuration choice, not a guarantee of capture time.
- Plan binary retention. If workflows create many or large images, consider where n8n stores binary data and how long it retains it. n8n documents S3-backed external binary storage for eligible self-hosted Enterprise deployments; an S3 lifecycle configuration is needed to remove old files. See n8n external binary storage.
Choose an integration route
| Route | Best fit | Trade-off |
|---|---|---|
| ScreenshotNeo API | A direct screenshot API call or a way to avoid setting up browser capture yourself. | Use its documented API request and options; see ScreenshotNeo docs. |
| HTTP Request node with Browserless REST API | A straightforward n8n workflow with direct control over request settings. | You configure the endpoint, token, response handling, and suitable waits. This is the path in the official Browserless n8n guide. |
| Browserless community node | Users who prefer a dedicated node interface. | It is a community integration; check compatibility and maintenance against your n8n version in the public repository. |
| BrowserQL or Function API | Workflows needing more involved browser interactions or custom browser-side JavaScript. | Offers a more specialized setup than a basic screenshot request; Browserless covers screenshots in its BrowserQL guide. |
A plain HTTP fetch in n8n does not render a browser page by itself. For a website screenshot, use a browser service or an API that performs the capture.
Troubleshoot common failures
The response is not a usable image
Check that the endpoint, POST method, JSON body, and token query parameter are configured correctly. Also confirm that the node is set to handle an image response as binary/download data rather than treating raw image bytes as ordinary text.
Rank #2
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
The screenshot is blank or missing dynamic content
The page may still be loading when the capture runs. Add or adjust a documented wait for the relevant element or page state, then test again. Browserless specifically warns that capturing before elements load can produce blank or incomplete screenshots.
Free tools Windows power users keep installed
One-click scans. No signup required.
The workflow times out on slower pages
Increase the HTTP Request timeout to fit the page and capture operation, and use retry logic for transient failures. If the problem recurs on the same page, check whether the page is reachable from the selected region and whether your readiness condition can complete.
Downstream nodes cannot find the image
Inspect the HTTP Request node’s output and map its binary property into the next node. If the next step only accepts JSON, use the documented base64 response approach and pass the encoded image as a string rather than mapping binary data into a text field.
Binary storage grows unexpectedly
Review workflow executions and binary retention. For eligible self-hosted Enterprise deployments, n8n supports external S3 storage; configure a lifecycle rule on the bucket if old files should be removed automatically.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo can capture a page through one GET request. See the API documentation for request options. This cURL example saves a WebP response:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpWith ScreenshotNeo, cookie banners are accepted and removed along with known consent platforms, newsletter popups, and chat widgets before the shot; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Learn about ScreenshotNeo or sign up free for 1,000 screenshots a month, with no card.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
