To schedule website screenshots with Apify, choose a screenshot Actor, run it once, then create and enable an Apify schedule for that Actor or a reusable task. The schedule controls when the Actor runs; the Actor’s own documentation defines how to provide the URL, viewport, wait conditions, authentication, and screenshot output. Apify’s scheduling guide is the place to start for schedule settings: Actor and task schedules.
Before scheduling: choose and test a screenshot Actor
Apify schedules can start Actors or tasks automatically, but there is no universal screenshot input schema. Find an Actor whose documented capture behavior and output fit your needs, and read its current input schema before setting up automation.
As an Amazon Associate I earn from qualifying purchases.
- Confirm how it accepts the target URL and any required inputs.
- Check whether it captures the viewport or full page, and whether it supports the browser or rendering behavior your page needs.
- Look for documented wait controls, authentication fields, output formats, and storage or retention behavior.
- Review the Actor’s current run options and pricing on its listing. The general Apify scheduling documentation does not establish screenshot-specific settings or costs.
Run the Actor manually with a representative page. Inspect the screenshot, output, and run logs before automating it; this catches incorrect input assumptions and page-specific loading issues early.
Create a reusable task if the configuration will repeat
An Apify task saves an Actor configuration, including input and run options, so you can reuse it in a schedule. Create one after a successful manual run if the same screenshot setup will run repeatedly. See Apify’s Actor tasks documentation for task behavior.
#1 Best Overall
Apify’s schedule guide says an Actor must have been run at least once before it can be scheduled. You can schedule the Actor directly or use a task when you want to reuse a saved configuration.
Create and enable the schedule
- In Apify Console, open the schedules area and create a schedule. The schedule guide describes a visual custom schedule builder as well as cron expressions.
- Add an action to run the selected Actor or task. Provide the Actor’s documented input and any run-option overrides needed for this capture.
- Set the schedule expression and choose the intended timezone. Apify documents timezone settings and daylight-saving shifts; check the displayed upcoming runs to confirm the local times match your expectations.
- Review the configuration and explicitly enable the schedule. Apify’s guide says newly created schedules are disabled by default.
- Check the next scheduled run and, after it executes, inspect its status, logs, and output storage.
For programmatic setup, use Apify’s Manage schedules API documentation. The schedule API supports schedule management and actions for Actors or tasks; the exact request parameters should be taken from the current API reference.
Rank #2
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Set input, timing, and run expectations
Inputs and overrides
A schedule can override Actor input. If no input is supplied, the Actor’s defaults are used; omitted fields in an override are filled from the default input. Do not assume screenshot-specific property names: use the chosen Actor’s schema for the URL, capture mode, waits, credentials, and other settings.
Recommended Free Tools
Timezone and daylight saving
Choose the timezone intentionally rather than assuming the schedule uses the timezone of the person creating it. Apify documents timezone support and daylight-saving shifts. Review the upcoming-run feedback in the schedule builder, especially for schedules tied to a particular local business hour.
Rank #3
Execution timing and intervals
Apify says scheduled events usually fire within one second of their scheduled time, but overload or a server shutting down can delay execution. Treat a schedule as an automation trigger, not a guarantee of exact wall-clock completion.
The schedule guide documents a 10-second minimum interval and says a run scheduled sooner after the previous one will be skipped. Its stated schedule limits are up to 10 Actors and 10 tasks per schedule. These are platform rules that may change; check the current schedule documentation before relying on them.
Rank #4
Builds, logs, and output
An Actor’s numbered builds and tags determine which version runs. Pinning an exact build can reduce surprises from a new version, but it also means you will not receive later build updates automatically. Apify run records include logs, storage, and a terminal status; documented outcomes include success, failure, timeout, and abortion. Use the selected Actor’s own documentation to understand where screenshots are stored and how long its output remains available. See Actor runs and builds.
Troubleshooting scheduled screenshots
- No run starts: Confirm the schedule is enabled, the Actor has been run at least once, and the action points to the intended Actor or task. Check schedule notifications for reported failures to start.
- The screenshot uses unexpected settings: Compare the schedule input and overrides with the Actor’s current schema. Missing override fields fall back to Actor defaults.
- The screenshot is blank or incomplete: Review the Actor’s documented wait controls and capture mode, then compare the run log and stored output. Screenshot-specific fixes depend on the Actor rather than on Apify schedules generally.
- A scheduled run is late or skipped: Allow for timing delays during overload or server shutdown. Check whether the requested interval is below the documented 10-second minimum or occurs sooner than the previous run.
- A run fails or times out: Open its status and logs to locate the failure, then check whether the Actor’s input, page access, authentication, or run options match its documentation.
- Behavior changes after an Actor update: Check which build or tag the run used. Pin a numbered build if you need a stable version, understanding that this forgoes automatic updates.
Or skip the browser setup
If your goal is simply to get screenshots repeatedly without configuring an Actor and browser flow, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Its API accepts a URL, and its documented options include full-page capture, device and viewport settings, wait controls, custom headers and cookies, and asynchronous jobs. See the ScreenshotNeo API documentation for request options.
Best Value
Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status. An MCP server lets AI agents such as Claude and Cursor take screenshots. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Can one Apify schedule run more than one Actor or task?
Apify’s schedule guide documents support for multiple actions, with stated limits of 10 Actors and 10 tasks per schedule; check the current documentation for changes.
Does Apify guarantee a screenshot will be ready at the exact scheduled time?
No. Apify says schedule events usually fire within one second, but overload or server shutdown can delay a run; the screenshot Actor must also finish its capture.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsQuick 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.




