Time/Numbers
Cron Parser
Parse a cron expression (5 or 6 fields, including @-shortcuts) — a plain-language schedule description and next run times in a chosen time zone.
A cron expression is a compact five- or six-field schedule format (minute, hour, day of month, month, day of week, sometimes seconds) that's hard to read at a glance. This tool translates it into plain language and lists the next run times in your chosen timezone.
How to use it
- Paste a cron expression (e.g. 0 3 * * * or a shorthand like @daily) and a plain-language schedule description appears instantly.
- The list of upcoming runs shows exact dates and times in your chosen timezone — handy for checking whether a job collides with another.
- Both 5-field cron expressions (standard Unix cron) and 6-field ones with seconds (Quartz and similar schedulers) are supported.
Common uses
- Checking a job's schedule before deploying — confirming the cron expression really runs the script when intended.
- Debugging a job that fires more or less often than expected.
- Building a new cron schedule without looking up the syntax reference every time.
Things to keep in mind
In classic cron, the day-of-month and day-of-week fields combine with OR rather than AND when neither is "*" — a frequent cause of unexpected extra runs.
The server running cron may be set to a different timezone than the one you're assuming — always confirm which timezone the schedule is interpreted in.
Article about this tool: Cron expressions: how to decode a task schedule
Frequently asked questions
How does a 6-field cron expression differ from a 5-field one?
Standard cron uses 5 fields (minute, hour, day of month, month, day of week). Some schedulers add a sixth seconds field at the start of the expression — the tool recognizes both formats automatically.
What do shortcuts like @daily mean?
They're convenient aliases for common schedules: @daily corresponds to "0 0 * * *" (midnight every day), @hourly to "0 * * * *", and @weekly, @monthly, and @yearly work similarly.
In which timezone are the upcoming runs calculated?
In whichever one is selected in the "Timezone" field. The same cron expression gives a different absolute run time depending on the timezone, so make sure to specify the one your scheduler actually runs in.
Does daylight saving time affect when a job runs?
Yes, if the scheduled time falls on a nonexistent or repeated hour during the clock change. For critical jobs, it's more reliable to schedule outside the typical transition window or explicitly use UTC.
Why did an expression with both day-of-month and day-of-week fields specified run when I expected only one match?
In classic cron, these two fields are combined with OR rather than AND when neither is an asterisk — the job runs as soon as either condition matches, even if the other doesn't.