Cron Expression Builder and Visualizer
Type the schedule you want in plain English, get the cron expression — and see when it will actually fire, in your local time zone, not UTC.
5-field standard cron. Quartz / Spring / AWS EventBridge add a leading seconds field — use 0 * * * * * for “every minute at second 0”.
Next runs in your time zone
| # | Local time | UTC |
|---|
Weekends and public holidays are not excluded — cron has no concept of them.
How to use the cron builder
A cron expression is five space-separated fields. Each field describes when, not a specific date — the scheduler matches it against the clock in the time zone the scheduler runs in.
The most common mistake is putting the minute before the hour. 0 9 * * * is 9:00; 9 0 * * * means minute 9 of hour 0.
| Symbol | Meaning | Example |
|---|---|---|
* | Every value in the range | * minutes = every minute |
*/n | Every nth value | */15 minutes = :00, :15, :30, :45 |
n-m | Range | 1-5 = Monday to Friday |
n,m | List | 1,3,5 = Monday, Wednesday, Friday |
@daily | Shorthand | @daily = 0 0 * * * |
Frequently asked questions
What does 0 9 * * 1-5 mean?
It runs at 09:00 on Monday through Friday, every week.
How do I run a job every 90 seconds?
Standard cron cannot — its smallest step is one minute. Quartz, Spring and AWS EventBridge add a seconds field, giving 0 */90 * * * *.
Why does my job run at an unexpected hour?
Most schedulers run in UTC. This tool shows every upcoming run in your browser’s local time zone next to the UTC value, which is the fastest way to catch that mismatch.
Does cron skip weekends automatically?
No. 0 9 * * 1-5 is how you exclude weekends. Public holidays need a wrapper script or a scheduler with holiday support.
Is anything uploaded?
No. Every calculation runs in this page.