PocketPlay
中文
Cron Expression Parser
Translate any cron expression into plain English, see the next 10 run times in your timezone, and build one field by field.
Meaning
Presets
Next 10 runs
| # | Local time in the selected zone | From now |
|---|
No run time found in the next 4 years — the expression may never match (for example February 30).
Field by field
| Field | Value | Allowed | Expands to |
|---|
Visual builder
How to use the cron parser
- Type or paste a cron expression — or hit a preset, or assemble one in the visual builder below.
- Read the plain-English meaning, then check the next ten run times; switch the timezone if your server does not run on your local clock.
- Use the field table to confirm exactly which minutes, hours, days and weekdays the expression expands to before you commit it to a crontab.
FAQ
Which cron dialect is supported?
Standard five-field Vixie cron (minute hour day-of-month month day-of-week) and the six-field Quartz/Spring style with a leading seconds field. Inside a field you can use *, lists (1,15), ranges (1-5), steps (*/10, 5-20/3), month and weekday names (JAN, MON), ?, L and L-3 for the end of the month, 5L for the last Friday and 5#2 for the second Friday.
Why do day-of-month and day-of-week both fire?
Classic cron ORs them: if both fields are restricted, the job runs when either matches. 0 0 1 * MON therefore runs on the 1st and on every Monday. Leave one of them as * to get AND-style behaviour.
Are the run times timezone-correct?
Yes. Times are computed against the wall clock of the timezone you pick, including daylight saving jumps, so a 09:00 job stays at 09:00 across a DST change. Everything is calculated in your browser — the expression is never uploaded.