Confirm the time zone
Cron expressions usually do not include a time zone. Check whether your server, hosting platform, or scheduler runs in UTC or local time.
Build cron expressions visually without memorizing syntax. Set minutes, hours, days, months, and weekdays, then see the human-readable schedule and next run times.
At every minute of every hour of every day of every month.
Enter values to see next run times.
| Field | Range | Special |
|---|---|---|
| Minute | 0-59 | * , - / |
| Hour | 0-23 | * , - / |
| Day | 1-31 | * , - / |
| Month | 1-12 | * , - / |
| Day of Week | 0-6 (Sun=0) | * , - / |
* = any value
, = list: 1,3,5
- = range: 1-5
/ = step: */5 means every 5
0 * * * *Every hour at minute 0
0 9 * * 1-5Weekdays at 9:00 AM
*/5 * * * *Every 5 minutes
0 0 1 * *First day of every month at midnight
0 8,12,18 * * *At 8 AM, 12 PM, and 6 PM daily
0 0 * * 0Every Sunday at midnight
Cron expressions usually do not include a time zone. Check whether your server, hosting platform, or scheduler runs in UTC or local time.
Cron implementations differ in how they combine day-of-month and day-of-week fields. Test expressions that use both fields.
Expressions such as */1 * * * * run every minute. Make sure your task can safely run that often before deploying it.
Some schedulers skip missed runs during downtime, while others catch up later. Know how your platform handles failures and restarts.
Traditional cron uses five fields and does not include seconds. Some platforms add a sixth seconds field, so always check the scheduler documentation.
It means every 15 units for that field. In the minute field, */15 usually means at minute 0, 15, 30, and 45.
Different cron libraries may use different time zones, seconds-field support, or day-of-week rules. Use this generator for quick checks and verify platform-specific behavior before deployment.
Build schedules visually. No sign-up, no limits, no registration.
Explore All Tools