To take scheduled website screenshots with Browserless, pair a recurring trigger—such as Schedule by Zapier—with an HTTP POST to Browserless’s /screenshot endpoint. Include the page URL, capture options and API token; then save or forward the returned image. Browserless’s hourly Zapier example is just a sample cadence, not a recommendation for every monitoring job.
How the scheduled capture works
Browserless performs the browser capture, but a separate scheduler starts it on a recurring basis. Browserless documents a Zapier workflow using Schedule by Zapier as the trigger and Webhooks by Zapier to POST to its screenshot endpoint. The endpoint returns image data, which can be passed to a later step such as an email attachment.
As an Amazon Associate I earn from qualifying purchases.
For a simple recurring screenshot, the flow is:
- Store a Browserless API token in the automation platform’s credential or secret field when available.
- Set a recurrence that fits the monitoring purpose.
- POST the target URL and screenshot options to Browserless.
- Save or route the binary image response, then inspect a real run.
Browserless’s Zapier guide uses an hourly schedule as its example. Choose a different interval if hourly capture is unnecessary or unsuitable for the site and workload. The current plan limits and pricing are not established here.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Configure Browserless in Zapier
1. Add the schedule trigger
Create a Zap with Schedule by Zapier as the trigger and choose the recurrence you need. The trigger—not the screenshot endpoint—controls when the capture repeats.
#1 Best Overall
2. Add a webhook POST
Add Webhooks by Zapier and choose the POST action. Configure the Browserless screenshot endpoint, include your token as a query-string parameter, and send a JSON body with the page URL and options. Browserless’s example requests PNG, full-page capture, and a 1440 × 1000 viewport.
Keep the token private. Do not place a live token in a public workflow, shared example, or page URL that other people can see.
3. Handle the image response
The REST endpoint returns image bytes, with PNG as the default and other documented formats available. Before adding a delivery step, confirm how Zapier exposes the binary response in your account and workflow. Browserless’s guide shows Gmail as an optional next step for attaching the resulting file.
Free tools Windows power users keep installed
One-click scans. No signup required.
4. Verify the first run
Open the saved image and check that it shows the intended page, viewport or full-page extent, loaded content, and expected capture time. An HTTP response alone does not prove that the screenshot contains the content you wanted.
Choose options for a reliable capture
- Full page: Set
options.fullPagetotruewhen you need more than the visible viewport. - Format: The REST screenshot documentation lists PNG, JPEG, and WebP. JPEG quality matters when selecting JPEG; BrowserQL’s reference says its quality value does not apply to PNG. Do not assume a setting described for BrowserQL applies identically to the REST endpoint.
- Viewport: Set viewport dimensions when consistent layout matters. The Zapier example uses 1440 × 1000; use dimensions appropriate to your page.
- Lazy-loaded content: Set
scrollPage: trueto trigger content that loads as the page is scrolled. Combine it with full-page capture if you need the entire page, then verify the output. - Asynchronous rendering: Use the documented wait settings—such as waiting for an event, function, selector, or timeout—or navigation options when the page needs time to render. Navigation completion does not necessarily mean every widget or data-dependent element is ready.
- Element or region capture: The REST API documents a top-level selector option and fixed clipping with
options.clipwhen you need a particular target rather than the whole page.
Browserless’s BrowserQL screenshot reference gives a default screenshot timeout of 30 seconds. That default is specific to the cited BrowserQL surface; do not assume it is the REST endpoint’s timeout or applies to every account configuration.
Troubleshoot missing or blocked content
Blank or white screenshot
A blank capture can mean the site did not render usable content before capture or that automation was blocked. Check the response and image, then adjust waiting or navigation settings if the page is still loading.
CAPTCHA or access-denied page
Browserless identifies CAPTCHA and access-denied pages as signs that a site may be blocking automation. Its screenshot documentation points to the /unblock API for anti-bot cases, but using it does not guarantee access to a particular site.
Lazy content or elements are missing
Content loaded only after scrolling may not appear if the page was captured too soon. Try scrollPage: true and an appropriate wait, then inspect the image. For a specific element, wait for its selector when supported by the chosen API surface.
Automation step cannot attach or save the image
The screenshot response is binary image data, not ordinary JSON describing an image. Check how the webhook action exposes the response and select the resulting file or binary field in the next step. The exact field mapping depends on the automation platform’s interface.
Rank #4
When a REST call is enough—and when it is not
Browserless describes its REST APIs as suitable for a single browser task without managing browser infrastructure. A scheduled webhook POST is therefore a practical shape when each run only needs a capture. If a workflow must interact with the page before taking the image, Browserless’s screenshot example also demonstrates connecting with Puppeteer or Playwright. Those approaches add browser-automation code and are not required for the basic scheduled POST.
Browserless identifies its OpenAPI reference as version 2.56.7; that is a documentation version, not a guarantee that every deployed instance uses the same version. Refer to the current endpoint documentation for the exact request details available to your account.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesOr skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. Its one-call GET request returns an image or PDF; for example, this cURL command saves a WebP screenshot of a page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes cookie banners, popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month—no card required.
Frequently Asked Questions
Can Browserless take screenshots automatically every hour?
Yes. Browserless’s Zapier documentation uses an hourly schedule as an example. The scheduler controls the interval, so hourly capture is optional rather than a required Browserless setting.
Does a successful screenshot request guarantee the intended page was captured?
No. A response can contain a blank page, CAPTCHA, access-denied screen, or incomplete content. Inspect the returned image and configure waits or scrolling where the page requires them.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
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.
