How to use
- Type a cron expression in the box above. Standard 5-field expressions (
minute hour day month weekday), 6-field expressions with a leading seconds field, and macros such as@dailyare supported. - A plain-language sentence appears right below. For example,
*/15 9-18 * * 1-5reads “Every 15 minutes, between 09:00 and 18:59, Monday through Friday”. - Pick a time zone to see the next 10 run times in that zone’s wall-clock time, with the time remaining. Times that do not exist because of a daylight saving jump are skipped.
- The field breakdown table shows what each field expanded to. The builder at the bottom has preset buttons that fill in common schedules.
Fields and special characters
| Position | Field | Allowed values | Names |
|---|---|---|---|
| (optional) | Second | 0–59 | none |
| 1 | Minute | 0–59 | none |
| 2 | Hour | 0–23 | none |
| 3 | Day of month | 1–31 | none |
| 4 | Month | 1–12 | JAN–DEC |
| 5 | Day of week | 0–7 (0 and 7 are Sunday) | SUN–SAT |
| Character | Meaning | Example |
|---|---|---|
* |
Every value | * * * * * every minute |
, |
List | 0,30 * * * * at minute 0 and 30 of every hour |
- |
Range | 0 9 * * 1-5 Monday to Friday |
/ |
Step | */15 * * * * every 15 minutes; 5/20 starts at minute 5 and steps by 20 (5, 25, 45) |
Names are case-insensitive, so mon-fri and MON-FRI are the same.
Common examples
| Expression | Meaning |
|---|---|
* * * * * |
Every minute |
*/5 * * * * |
Every 5 minutes |
0 * * * * |
Every hour, on the hour |
0 0 * * * |
Every day at 00:00 |
0 9 * * 1-5 |
At 09:00, Monday through Friday |
30 2 * * 0 |
At 02:30, every Sunday |
0 0 1 * * |
At 00:00, on day 1 of the month |
0 0 1 1 * |
At 00:00 on January 1 |
0 */6 * * * |
Every day at 00:00, 06:00, 12:00 and 18:00 |
0 9-17 * * 1-5 |
On the hour, between 09:00 and 17:59, Monday through Friday |
@yearly and @annually equal 0 0 1 1 *, @monthly is 0 0 1 * *, @weekly is 0 0 * * 0, @daily and @midnight are 0 0 * * *, and @hourly is 0 * * * *. @reboot is a special entry that runs once when the system starts, so it has no next run time.
Day of month and day of week together
When both the day-of-month and day-of-week fields are something other than *, a run happens if either one matches, not only when both do (the Vixie cron rule). 0 0 13 * 5 means “the 13th, or any Friday”, not “Friday the 13th”. Calculated in UTC after 2026-10-07 10:07 UTC, it runs on 2026-10-09 (Friday), 2026-10-13 (the 13th), 2026-10-16 (Friday) and 2026-10-23 (Friday). If one of the two fields is *, only the other one applies. This tool follows the same rule when it calculates.
Server time zones and syntax differences
- Cron runs in the time zone of the server or container. In environments that run on UTC, such as Docker containers or GitHub Actions schedules,
0 9 * * *fires at 09:00 UTC, which is 18:00 in Seoul. As a check,0 9 * * *calculated for Asia/Seoul right after 09:00 KST on 2026-10-07 next runs at 2026-10-08 00:00 UTC. - In regions with daylight saving time, a job scheduled for a time that does not exist (for example 02:30 on the second Sunday of March in New York) may not run that day. When a time occurs twice, this tool counts only the earlier one.
- Quartz and Spring
@Scheduleduse 6 fields with a leading seconds field (Quartz adds an optional year) and support?,L,Wand#. This tool parses standard cron syntax only, so those characters are reported as errors. A 6-field expression is read with the first field as seconds.
For converting times, try the Timestamp Converter and the Time Zone Converter. To test text patterns use the Regex Tester, and for file permissions see the chmod Calculator.
The expression you type is processed only in your browser and is never sent to a server.