About this tool
Cron schedules jobs with five fields — minute, hour, day of month, month and day of week — and a short syntax that is easy to get wrong. Type an expression such as 0 9 * * 1-5 and read it in plain words ("At 09:00, Monday to Friday"), check what each field allows and see the next eight run times in your time zone. It understands lists (1,15), ranges (1-5), steps (*/10), month and day names (JAN, MON) and the @hourly, @daily, @weekly, @monthly and @yearly macros, and points at the field with a mistake. When both day fields are set it follows Vixie cron: a day matches if either does.
How to use it
- 1 Type or paste the 5-field cron expression, or pick a preset.
- 2 Read the sentence and the values allowed in each field.
- 3 Check the next run times; servers often run cron in UTC.
- 4 Copy the link to share the schedule.
Frequently asked questions
What do the five fields mean?
In order: minute (0–59), hour (0–23), day of the month (1–31), month (1–12 or JAN–DEC) and day of the week (0–7, where 0 and 7 are Sunday, or SUN–SAT). An asterisk means any value.
Does it support seconds or Quartz syntax?
No: it explains the standard 5-field Unix cron used by crontab, GitHub Actions, Kubernetes CronJobs and most cloud schedulers. Quartz and Spring add a seconds field and symbols such as ? and L.
Why do the run times differ from my server?
The list uses your device’s time zone. Many servers, CI services and cloud schedulers run cron in UTC — 0 9 * * * in UTC is 06:00 in Brasília.
Embed this tool
Add this free tool to your own website — copy the code below. It stays up to date automatically.
Tools for your site →