Paste a cron expression. See when it really runs.
Five fields separated by spaces: minute, hour, day of month, month and day of week. 0 9 * * 1-5 means minute 0 of hour 9, any day of the month, any month, Monday to Friday: 09:00 on weekdays.
* is every value, 1,15 is a list, 9-17 is a range, and */15 is a step: every 15th value from the start. They combine, so 0-30/10 means minutes 0, 10, 20 and 30.
When both day of month and day of week are set, cron runs when either one matches: the 13th of every month, and every Friday. If one of the two starts with *, both have to match.
The server's own time zone, which is often UTC. Pick it in the tool and every run is also shown in your local time, so 09:00 on the server is not mistaken for 09:00 where you are.
In this tool, a time skipped when clocks jump forward does not run that day, and a time that happens twice runs once. Cron daemons differ here: Vixie cron, for one, runs skipped jobs right after the jump. If a job sits in that hour, check yours or use UTC.
No. Every expression is read and worked out inside this browser tab, and it isn't sent or saved anywhere.