THE TOOLBOX / SCHEDULING & DEVOPS
Schedules,
without the guesswork.
Understand any five-field cron expression in plain English and preview its next 5 execution times across UTC and IANA time zones.
THE DETAILS
POSIX 5-field crontab syntax, IANA time zones, and scheduler semantics.
1. Step-by-Step Workflow
Enter a five-field cron schedule (such as */15 9-17 * * 1-5), specify an IANA time zone (e.g., UTC or Asia/Dhaka), and optionally set a reference start time. Click Explain schedule to read the human-friendly summary and inspect the next 5 execution timestamps in both UTC and your target zone.
2. Five-Field Crontab Syntax Rules
Each field accepts wildcards (*), exact numbers, inclusive ranges (9-17), comma-separated lists (1,15), and step intervals (*/5). In the day-of-month and day-of-week fields, */1 is normalized to *.
3. Time Zones & DST Warnings
GitHub Actions and Cloudflare Cron Triggers evaluate schedules strictly in UTC, whereas Linux crontab and Kubernetes CronJob (with timeZone set) use local IANA zones. Always test your schedule against the exact zone your target runner uses.
4. Local Execution & Related Tools
Schedule evaluation runs inside a background Web Worker in your browser. Need to convert individual Unix epoch timestamps, validate Kubernetes YAML manifests, or calculate chmod permissions for cron scripts? Try the Timestamp converter, YAML ↔ TOML converter, and Chmod calculator.
Five-Field Cron Syntax & Examples Matrix
| Cron Expression | Plain-English Meaning | Typical Use Case |
|---|
*/5 * * * * | Every 5 minutes | Health checks & queue polling |
0 0 * * * | At 00:00 (midnight) every day | Daily log rotation & database backups |
*/15 9-17 * * 1-5 | Every 15 min, 09:00–17:59, Mon–Fri | Business-hours sync jobs |
0 3 1 * * | At 03:00 on day 1 of every month | Monthly billing & invoice rollups |
Common Cron Scheduling Pitfalls
Omitting Minute Zero (Running Every Minute!)
Writing * 2 * * * instead of 0 2 * * * runs the job 60 times (every minute between 02:00 and 02:59) rather than once at 02:00.
Restricting Both Day-of-Month and Day-of-Week
In standard cron, 0 9 15 * 1 runs on the 15th of the month or every Monday, not "Monday the 15th". Keep one of the two day fields set to *.
End-of-Month Days (29, 30, 31)
Scheduling a job on day 31 skips February, April, June, September, and November entirely. Schedule on the 1st of the month at 00:00 when every month must run.
Percent (%) Characters in Crontab Commands
In Linux /etc/crontab files, unescaped % characters in the command portion are converted into newlines by the cron daemon. Escape them as \%.
Frequently Asked Questions
What are the 5 fields in a standard POSIX cron expression?
In left-to-right order, the 5 fields represent Minute (0–59), Hour (0–23), Day of Month (1–31), Month (1–12), and Day of Week (0–7, where both 0 and 7 represent Sunday).
Why does this helper require either day-of-month or day-of-week to be *?
In standard Vixie/POSIX cron, specifying both a restricted day-of-month and a restricted day-of-week uses a logical OR (running when either matches) rather than a logical AND, which frequently surprises developers. Requiring * in one of those two fields prevents accidental schedule misconfigurations.
How do Daylight Saving Time (DST) clock changes affect cron schedules?
If a job is scheduled inside a spring-forward DST gap (such as 02:30 in America/New_York) or a fall-back overlap (01:30), different cron daemons (Vixie cron, systemd timers, Kubernetes CronJobs, GitHub Actions) handle the jump differently—some skip the run, while others run once or twice.
Does this tool support 6-field Quartz or seconds-based cron strings?
No. This tool strictly validates 5-field numeric cron expressions (minute through day-of-week) used by Linux crontab, Kubernetes CronJobs, GitHub Actions, and Cloudflare Workers Cron Triggers.
Are my cron expressions or schedule previews processed locally?
Yes. Schedule parsing, plain-English translation, and upcoming timestamp calculations run inside a local browser Web Worker with zero network requests.