How to use
- Type or paste the expression, for example 0 9 * * 1-5.
- Read the plain-language description and the value of each field.
- Pick the server's time zone to see the next ten run times as they will actually happen.
- Click an example on the right to start from a common schedule.
Options explained
- Fields
- Five fields — minute, hour, day of month, month, day of week. A sixth field in front adds seconds (used by Spring, Quartz and node-cron).
- Special characters
- * any value; , list (1,15); - range (1-5); / step (*/10 = every 10). Quartz uses ? for "no specific value" in day fields.
- Day of week
- 0 or 7 is Sunday, 1 is Monday. Names like MON-FRI also work.
- Time zone
- Cron runs in the server's time zone, usually UTC on cloud servers. Choosing it here shows when jobs will really fire, including daylight-saving changes.
Common schedules
| Expression | Runs |
|---|---|
* * * * * |
Every minute |
*/15 * * * * |
Every 15 minutes |
0 * * * * |
At the start of every hour |
0 9 * * 1-5 |
09:00 on weekdays |
30 2 * * * |
02:30 every day |
0 0 * * 0 |
Midnight every Sunday |
0 0 1 * * |
Midnight on the 1st of each month |
0 0 1 1 * |
Midnight on 1 January |
Frequently asked questions
What does */5 * * * * mean?
Every 5 minutes — at minute 0, 5, 10 and so on of every hour.
Why did my job run at the wrong hour?
Most often the server runs in UTC while you wrote the schedule in local time. Pick UTC above to see the real run times, or set CRON_TZ / TZ for the job if your scheduler supports it.
How do day of month and day of week combine?
In standard cron, if both are restricted (for example 0 0 1 * 1), the job runs when either matches — on the 1st and on every Monday. Quartz avoids this by requiring ? in one of them.
Does this support Kubernetes CronJob and GitHub Actions schedules?
Yes, both use standard 5-field cron. GitHub Actions evaluates schedules in UTC by default.
Privacy
This tool runs entirely in your browser. Your files and text are processed on your device and are never uploaded to our servers.