Next Run Calculator
Cron next run calculator online. Show next 10 scheduled runs with timezone support. DST-safe cron schedule preview—free cron calculator.
📅
Cron Expression
Enter expression to see schedule
🌍
📊 Show 10
MIN HOUR DAY MON DOW
* = any • , = list • - = range • / = step
Features
- Calculates and lists the exact dates and times for the next upcoming executions
- Full interactive Timezone support (Convert UTC to local time instantly)
- Preview up to 100 future occurrences
- Highlights time-deltas (e.g., "happens in 2 hours")
- Safely evaluates edge cases around Daylight Saving Time (DST) and leap years
Common Use Cases
- Aligning server maintenance tasks with low-traffic timezone hours
- Ensuring a monthly billing script fires on the correct calendar day
- Debugging jobs that seemed to skip a run over a holiday or DST shift
- Proving to QA/Stakeholders exactly when an automated email campaign will trigger
Timezones and Next Runs
A cron expression itself is timezone agnostic—it only knows hours and minutes, not global geography. The actual execution relies entirely on the server's local clock.
If you write 0 12 * * * (noon) and deploy it to a server running in UTC, it will trigger at 12:00 UTC. If you intended for it to run at noon EST (Eastern Standard Time), it will fire 5 hours earlier than you wanted!
Using a Next Run Calculator with timezone projections is crucial when orchestrating cloud-native architectures that span globally distributed clusters.
Examples
Valid - Weekly Midnight UTC
0 0 * * 0 Valid - Quarterly Task
0 0 1 1,4,7,10 * Valid - Leap Year Edge Case
0 0 29 2 *Frequently Asked Questions
Why did my cron skip an execution today?
If your cron was scheduled between 2 AM and 3 AM during a "Spring Forward" Daylight Savings Time shift, that hour never existed localized to the server clock, causing the daemon to skip the job.
How do I handle leap years?
If you schedule a job for February 29th (`0 0 29 2 *`), the next-run calculator will confirm that this job will only trigger on leap years (e.g. 2024, 2028).
Can cron run every few seconds?
Standard Unix cron can only run as frequently as every 1 minute (`* * * * *`). If you need sub-minute resolution (e.g. every 10 seconds), you must use an application-level generic scheduler or sleep loops.
💡 Tips
- When using cloud providers like AWS or Vercel, pretend the server is ALWAYS in UTC and do the mental math backwards for your chron expressions.
- Use the Next Run list to verify the exact behavior of jobs that run on the 31st of restricted months.