CronMint · parse · explain · next runs
A cron line,
read back to you.
Before it runs.
Paste a 5-field or 6-field cron expression and get it back in plain English or Korean, the next 10 runs in the timezone you choose, and a crontab or GitHub Actions snippet of the same schedule — parsed and projected in this tab, never on a server.
Expression
minute hour day month weekdayField editor
click a value to set it—
Presets
twelve lines that cover most jobsTake it with you
same schedule, ready to pasteHow this reads a line
POSIX first, edges stated01Fields, ranges and steps
Each field is a list of numbers, names, ranges and steps: 1,15, mon-fri, 9-17, */5 and 20/15 all parse. A field that is * (or ?) is unrestricted — the difference matters for the next note.
| Field | Range |
|---|---|
| Minute | 0–59 |
| Hour | 0–23 |
| Day of month | 1–31 |
| Month | 1–12 / JAN–DEC |
| Weekday | 0–7 / SUN–SAT |
| Second (6-field) | 0–59 |
02Two day rules, one tie
In Vixie cron, if day of month and weekday are both restricted, the job runs when either matches — 0 0 1 * 1 fires on the 1st and on every Monday. Leave one as * and only the other applies. Quartz refuses that line instead unless one of the two is ?; this tool follows crontab and states which rule it used.
03Timezones are the usual bug
crontab has no timezone field: it fires in the server's local time, which is UTC on most containers and runners. GitHub Actions schedules also default to UTC and now accept an optional timezone: key; the shortest interval there is 5 minutes. Each run below is shown in your chosen zone with its UTC equivalent, so the line you paste says the hour you meant.