How to Skip Weekends in a Recurring Website Screenshot Job

To skip weekend captures, configure the recurring screenshot job to run Monday through Friday. In a scheduler that accepts compatible five-field cron expressions, use 0 9 * * 1-5 for one run each weekday at 09:00. Check the scheduler’s cron dialect and timezone before saving: cron syntax and daylight-saving behavior can differ between services.

1. Set the job to run on weekdays

Open the screenshot job’s schedule settings.
If it has a days-of-week selector, choose Monday, Tuesday, Wednesday, Thursday, and Friday. Leave Saturday and Sunday unselected.
If it accepts a compatible five-field cron expression, set the day-of-week field to 1-5. For a daily 09:00 capture, enter 0 9 * * 1-5.
Set the intended timezone. Confirm how the service handles daylight-saving changes if the capture must stay at a consistent local time.
Save the schedule and check the displayed next run, if available. Confirm it falls on the weekday you expect.

Hosted tools may offer weekday selection or weekday timeslots. For example, PagePixels documents selecting weekdays, and Stillio documents weekday timeslots. Their interfaces and available schedule controls are specific to those services.

2. Understand the cron expression

A common five-field cron expression has this order:

minute hour day-of-month month day-of-week

In 0 9 * * 1-5:

Field	Value	Meaning
Minute	`0`	At minute zero
Hour	`9`	At 09:00
Day of month	`*`	Any day of the month
Month	`*`	Any month
Day of week	`1-5`	Monday through Friday in the cron dialect used by this example

Cron implementations do not all use the same field count or conventions. Some accept a seconds field or special syntax; weekday numbering can also vary. Use the syntax documented by your scheduler instead of assuming that an expression will transfer unchanged.

Common weekday schedules

Goal	Example for a compatible five-field cron scheduler
One capture at 09:00 each weekday	`0 9 * * 1-5`
Capture every 30 minutes during the 09:00–17:00 hour range on weekdays	`/30 9-17 * 1-5`
Run at 08:30 each weekday	`30 8 * * 1-5`

ScreenshotAPI.net documents */30 9-17 * * 1-5 as a weekday business-hours example. Confirm whether your scheduler treats the ending hour as inclusive and whether it interprets times in the timezone you selected. ScreenshotAPI.net’s schedule guide describes its cron setup; its example does not guarantee identical behavior in every scheduler.

3. Schedule a self-managed screenshot job

If your screenshot capture is a script you control, put the capture command behind a scheduler that supports weekday restrictions. For a Unix-like system using a compatible crontab, edit the crontab and add a line such as:

0 9 * * 1-5 /usr/local/bin/capture-website.sh

This runs the script at 09:00 Monday through Friday according to the cron service’s timezone and dialect. Replace the script path with the actual executable path, and ensure the script has permission to run. The schedule triggers the script; it does not itself create a screenshot. Your script must perform the capture and handle output, errors, and logging.

If the hosted screenshot service has no weekday selector and no compatible cron option, use its documented scheduling controls or trigger captures from a scheduler that supports weekdays. A daily interval does not automatically skip weekends.

4. Verify the schedule before relying on it

Days: Confirm the selected days are Monday through Friday, or confirm the cron day-of-week field means those days in this scheduler.
Timezone: Check the schedule timezone and daylight-saving rules. A 09:00 schedule is meaningful only relative to a timezone.
Cadence: Decide whether you need one capture per weekday or repeated captures during a weekday window.
Next run: Inspect the next scheduled time when the service provides it. Check again near a weekend boundary if possible.
Operations: Know how to pause or resume the job if the schedule is wrong.

Recurring screenshot services may expose timezone and cadence controls alongside the schedule. See Allscreenshots’ recurring schedule guide and the PagePixels scheduling tutorial for examples of service-specific controls.

5. Troubleshoot missed or unexpected weekend captures

Symptom	Likely cause	What to check
A screenshot still runs on Saturday or Sunday	The schedule is still set to daily, the weekday field was not applied, or this scheduler uses a different weekday numbering convention.	Reopen the saved schedule, inspect the day selector or cron documentation, and check the next run shown by the service.
No screenshots run on Monday	The cron dialect’s weekday numbering differs from the assumed convention, or the scheduler evaluates the job in another timezone.	Check the service’s field order, weekday numbering, timezone, and next-run preview.
The capture happens at the wrong local time	The schedule uses a different timezone or daylight-saving rule than expected.	Set the intended timezone in the job settings and confirm the service’s daylight-saving behavior.
The job runs more often than intended	The minute or hour fields express a repeated cadence, or the scheduler interprets an hour range differently.	Compare each cron field with the scheduler’s documentation. Use a single-hour expression for one daily run.
The schedule is rejected	The service expects a different cron format, field count, or interface.	Use the scheduler’s own documented format or choose its weekday controls if available.
The schedule looks right but no image is produced	The scheduler may have triggered the job while the capture itself failed, or the script may not be executable or may use an invalid path.	Check the job’s run history and script logs, then verify the capture command separately.

6. Reliability, performance, and cost considerations

Skipping weekends reduces the number of scheduled capture attempts compared with running every day. It does not by itself guarantee a successful capture: a scheduled run can still encounter a failed page load, timeout, or other capture problem. Check run history or logs when the result matters, and make sure your workflow can distinguish a missed run from a failed capture.

For repeated weekday captures, estimate the number of runs before choosing a service plan or setting a budget. One capture per weekday is about five scheduled runs per ordinary week; a schedule that runs every 30 minutes can create many more. Actual totals depend on the calendar, schedule window, and service billing rules. Read the chosen provider’s pricing and capture billing documentation rather than assuming every scheduled attempt is billed the same way.

7. Common questions

Does “weekdays” always mean Monday through Friday?

Usually that is the intended meaning, but confirm how the scheduler defines weekdays and which timezone it uses. Regional workweeks and service-specific conventions can differ.

Will a weekday cron schedule run at the same local time all year?

That depends on the scheduler’s timezone and daylight-saving handling. Check its documentation and next-run preview for the time of year when the offset changes.

Can I stop weekend runs without changing the capture itself?

Yes. The schedule controls when the capture is triggered; weekday selection does not require changing the target website or screenshot settings.

Or skip the browser setup

If you need screenshots from a script, ScreenshotNeo can capture a URL with one API request. This example saves the response as a WebP file:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

See the ScreenshotNeo API documentation for request options. To make it recurring on weekdays, schedule this request with your scheduler using a weekday rule such as 0 9 * * 1-5, after confirming that scheduler’s cron dialect and timezone. ScreenshotNeo is a website screenshot API and MCP server for developers, made by Yorker Media. The API request captures a URL; the weekday schedule is configured in your scheduler.

ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify page verdict and billing status in headers. Its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Learn more at ScreenshotNeo.