Cron Expression Parser
Paste a cron expression to get a human-readable description and a list of the next scheduled run times.
Every 15 minutes
- 1.Sat Aug 15 2026 13:30:00 GMT+0700 (Indochina Time)
- 2.Sat Aug 15 2026 13:45:00 GMT+0700 (Indochina Time)
- 3.Sat Aug 15 2026 14:00:00 GMT+0700 (Indochina Time)
- 4.Sat Aug 15 2026 14:15:00 GMT+0700 (Indochina Time)
- 5.Sat Aug 15 2026 14:30:00 GMT+0700 (Indochina Time)
About this tool
Cron expressions are compact but notoriously hard to read at a glance — is "*/15 0 * * 1-5" every fifteen minutes, or every fifteen hours? This parser translates a cron expression into a clear, plain-English description and then lists the actual next run times, so you can confirm a schedule does exactly what you intended before it ships to production.
It is aimed at anyone who writes crontab entries, Kubernetes CronJobs, CI schedules, or Spring @Scheduled cron strings. Paste an expression and you immediately see both a human sentence explaining each field and a concrete timeline of upcoming executions, which is far safer than deploying a guess.
How to use
- Paste or type a cron expression into the input field (minute, hour, day-of-month, month, day-of-week).
- Read the plain-English description that explains what the schedule means.
- Review the list of upcoming run times to confirm the cadence looks right.
- Use ranges (1-5), steps (*/15), lists (1,15) and wildcards (*) to refine the expression.
- Tweak any field and watch the description and next-run list update.
- Copy the finished expression into your crontab, CronJob, or scheduler config.
Features
- Turns any standard five-field cron expression into a readable sentence describing minute, hour, day, month, and weekday.
- Lists the next scheduled run times so you can verify frequency and timing at a glance.
- Understands ranges, step values, comma lists, and wildcards in every field.
- Catches common mistakes early — like confusing day-of-month with day-of-week — before they hit production.
- Great companion for crontab, Kubernetes CronJobs, CI/CD pipelines, and Spring scheduled tasks.
- Parses entirely in your browser with instant feedback and no server round-trip.
Frequently asked questions
What cron format does this parser expect?
It reads the standard five-field format: minute, hour, day-of-month, month, and day-of-week, each supporting wildcards, ranges, steps, and lists.
Does the tool run my cron expression on a server?
No. Parsing and the next-run calculation happen entirely in your browser. Your expression is never uploaded, so you can safely test internal schedules.
In which timezone are the next run times calculated?
The upcoming run times are computed relative to your local browser time, so what you see matches your own clock. Remember that your production scheduler may use UTC or a different zone.
What is the difference between day-of-month and day-of-week?
The third field targets a calendar day (1-31) while the fifth targets a weekday (0-7, where 0 and 7 are Sunday). Mixing them up is one of the most common cron bugs, which the plain-English description helps you avoid.
Can I use step values like */5?
Yes. Step syntax such as */5 (every five units) and ranges with steps like 0-30/10 are supported, and the description spells out exactly what they mean.