How to Automate Scheduled Website Screenshots with ScreenshotAPI
Schedule recurring website screenshots in ScreenshotAPI.net, choose a cron interval, manage jobs safely, and learn when an external capture workflow fits better.
To schedule recurring screenshots with ScreenshotAPI.net, open Query Builder, enter the page URL and capture options, select Schedule Screenshot, then choose a preset or enter a cron expression. Manage the recurring job from Schedule Requests, where the documented controls include Start, Stop, Delete, and View Screenshots.
This guide refers to ScreenshotAPI.net. A separate service at ScreenshotAPI.to has its own HTTP automation guide; its integrations should not be assumed to belong to ScreenshotAPI.net.
Set up a recurring capture
- Sign in to the ScreenshotAPI.net dashboard and open Query Builder.
- Enter the website URL you want captured.
- Choose the capture options appropriate for the page. The vendor’s walkthrough mentions output type and full-page capture as examples.
- Select Schedule Screenshot.
- Choose a preset interval or provide a custom cron expression.
- Save the schedule, then open Schedule Requests to find the recurring job and review its screenshots.
ScreenshotAPI.net describes the feature as capturing screenshots periodically based on a cron job schedule. Its scheduling documentation describes hourly, daily, weekly, and custom intervals.
Choose a cron schedule
ScreenshotAPI.net’s examples use the standard five-field order:
minute hour day-of-month month day-of-week| Schedule | Expression | How to read it |
|---|---|---|
| Every hour | 0 * * * * |
At minute 0 of every hour. |
| Daily at 09:00 | 0 9 * * * |
At minute 0, hour 9, every day. |
| Mondays at 08:00 | 0 8 * * 1 |
At minute 0, hour 8, on weekday 1 (Monday in the vendor’s example). |
| First day of each month at 09:00 | 0 9 1 * * |
At minute 0, hour 9, on day 1 of each month. |
| Every 30 minutes from 09:00 through 17:00 on weekdays | */30 9-17 * * 1-5 |
At minute 0 and 30 during hours 9 through 17, Monday to Friday. |
Timezone caveat: the reviewed ScreenshotAPI.net scheduling material does not establish which timezone governs cron execution. Verify the service’s timezone behavior before relying on a schedule for a local business-hour deadline. Do not infer that the dashboard uses your computer’s timezone.
Choose the interval based on how often the page can meaningfully change. Hourly captures may suit rapidly changing pages; daily or weekly captures may suit slower-moving pages. These are examples, not a guarantee that every target page needs that frequency.
Pause, inspect, and delete jobs safely
- Start: resume or start a recurring job using the documented Schedule Requests control.
- Stop: pause future captures while retaining the existing job history and screenshots, according to the vendor’s guidance.
- View Screenshots: inspect captures associated with the job.
- Delete: permanently remove the job and its related screenshots, according to the vendor’s warning.
If you need to pause a schedule but keep its history, stop it instead of deleting it. Download any images you need to preserve before deleting a job.
Automate downstream handling
The documented ScreenshotAPI.net workflow is managed in its dashboard. A separate guide on ScreenshotAPI.to describes an HTTP automation pattern in which a schedule, webhook, or event triggers a request, and the resulting screenshot can be stored or routed to another step. That guide names Zapier, n8n, Make, and Retool. These are claims about ScreenshotAPI.to, not verified integrations for ScreenshotAPI.net; check the product and account before building around them.
For a custom workflow, the general pattern is: trigger on a schedule, request a capture, then store or route the result. Confirm the selected service’s API, authentication, response format, rate limits, retention, and failure behavior in its own current documentation before implementing it. The reviewed materials do not establish those details for ScreenshotAPI.net.
Or skip the browser setup
If you need a capture endpoint that your own scheduler can call, ScreenshotNeo returns a screenshot or PDF from one GET request. Put that request in a scheduled task you control; the API call itself takes a capture when invoked. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as shot:
shot.write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));These examples make a single capture per invocation; configure the recurring trigger in your scheduler and protect the API key as a secret. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed; response headers report the page verdict and billing status. ScreenshotNeo also has an MCP server so AI agents can take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 screenshots. Create a free ScreenshotNeo account.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The capture runs at an unexpected local time. | The scheduler’s timezone is not established by the reviewed docs, or differs from your assumption. | Check the service’s current timezone setting and confirm execution time with a schedule you can observe before depending on it. |
| No job appears after setup. | The schedule may not have been saved, or you may be looking outside Schedule Requests. | Return to Query Builder, verify the job was created, then inspect Schedule Requests. |
| Captures happen more or less often than expected. | A cron field may be in the wrong position or have an unintended range/step. | Check the five-field order and compare the expression with the vendor’s examples before saving. |
| Old screenshots disappear after cleanup. | Deleting a job permanently removes its related screenshots. | Use Stop to pause future runs while retaining history, and download images before deletion if they must be kept. |
| An automation integration is missing. | Documentation for ScreenshotAPI.to may have been confused with ScreenshotAPI.net. | Confirm the domain and product in the account, then verify integrations in that product’s own documentation. |
| The target page looks incomplete. | The URL or capture options may not fit the page’s needs, or the target may load content dynamically. | Recheck the URL and available capture options in Query Builder. The reviewed material does not specify dynamic-content wait controls, so verify support with the vendor rather than assuming it. |
Reliability, retention, and cost considerations
- Validate before relying on a schedule: inspect an initial capture and verify the cron timing, especially where timezone matters.
- Keep an archive you control: the docs warn that deleting a job removes its associated screenshots. Download important captures before deletion.
- Pick a useful frequency: more frequent captures generate more artifacts to review and retain. Match the interval to how quickly the target changes.
- Check current plan details: the reviewed sources do not establish current ScreenshotAPI.net pricing, plan limits, retention duration, or timezone behavior. Confirm those details directly before estimating cost or promising retention.
- Account for failed runs: the reviewed scheduling pages do not establish retry policy or delivery guarantees. For a critical archive or alert, verify failure handling with the service and keep an independent copy of captures you need.
Frequently asked questions
Can I stop a schedule without deleting its screenshots?
Yes. ScreenshotAPI.net documents Stop as the way to pause future runs. Its guidance warns that deleting a job permanently removes related screenshots.
Does the documented guide say what timezone cron uses?
No timezone is established in the reviewed material. Verify it in the service before scheduling against a local clock.
Are Zapier, n8n, Make, and Retool ScreenshotAPI.net integrations?
The cited automation guide naming those tools belongs to ScreenshotAPI.to. It does not verify integrations for ScreenshotAPI.net.
Can I use ScreenshotNeo for recurring captures?
ScreenshotNeo’s documented API call captures a page when requested. You can invoke it from a scheduler you control; the API is not described here as a built-in recurring-job manager.
