Check whether a server job will run on Monday at 09:00 UTC or local time before you put it into production.
Never paste production passwords, live JWT access tokens or private customer records.
No uploads, cookies, tracking or third-party scripts. Your input stays in browser memory.
Ready. Enter a test value.
A single timezone assumption can run a data import at the wrong hour. This tool calculates actual upcoming dates for standard five-field Unix cron schedules in either UTC or your device-local timezone, including day-of-month and day-of-week rules.
Enter minute, hour, day of month, month and weekday. Examples: 0 9 * * 1 (Monday at 09:00), */15 9-17 * * 1-5 (weekday quarter-hours). Select UTC for most hosted schedulers if the service documents UTC, or local when your runtime uses local time.
Supports standard numeric Unix cron: asterisk, steps, lists and ranges. It does not accept Quartz seconds, ? or AWS EventBridge syntax. Preview searches up to 370 days; confirm your actual scheduler's timezone, DST interpretation and day-field semantics.
No. Those cron dialects use different numbers of fields and day-of-week rules. This is standard five-field Unix cron only.
This tool follows the common Vixie crontab OR rule when both day fields are restricted; some schedulers use different behavior.
No. They are matching calendar times. A paused server, disabled workflow, DST policy or scheduler configuration can prevent a job.