Cron Next Run Times
Paste the schedule and see the next five times it fires, on the server's clock.
Works in your browser. Nothing you type is sent to us.
Syntax
*any value5exactly 51-51 through 5*/15every 15th, from the start1,151 and 159-17/2every 2nd from 9 through 17MON-FRInames for days and months0 or 7both mean Sunday@dailyalso @hourly, @weekly, @monthly, @yearly, @reboot6 fieldsa leading seconds field is read tooWorked out in your browser. Nothing you type is sent to us.
Cron Next Run Times at a glance
- Price
- Free
- Data sent to us
- None, it runs in your browser
- Sign-up
- Not needed
- Reads
- Standard 5-field cron, 6 fields with seconds, macros
- Next runs
- Five, in local time or UTC
- Does not read
- Quartz L, W and #
How to use Cron Next Run Times
- Paste the expressionType it in the box or click one of the examples. The sentence appears at once.
- Check the fieldsThe table explains minute, hour, day of month, month and day of week one at a time.
- Check the next runsPick UTC if your server runs on UTC, as most do, and read the next five times. Copy the schedule to paste into a ticket or a comment.
Paste a cron expression and see the next five run times in UTC, the clock most servers, containers and GitHub Actions use, each with how long until it fires and the same moment in your own time. The schedule is read back in plain English and field by field, so a job that fires at the wrong hour or on the wrong days is easy to spot before it ships.
How it works
Cron Next Run Times is a web page that does its work on your own device. Everything you type or choose is worked out by your browser and never sent to a server, so nothing is stored and there is nothing to delete. There is no account, no sign-up and no limit on how often you use it.
GitHub Actions schedules
A workflow's schedule trigger takes a five-field cron line in UTC, and runs may start a few minutes late when the service is busy. Check the UTC times here, then convert in your head only once.
Questions
Why are my runs an hour off twice a year?
Your server runs on local time with daylight saving, so the clock jumps. Servers on UTC never shift; pick UTC here to see that schedule.


