Type a cron expression. See the next five runs.
Five-field POSIX. Step values, ranges, lists, named months and weekdays. Human-readable translation updates as you type. Nothing leaves your browser.
Presets
In English
—
Next five runs
Syntax cheatsheet
*— every value*/5— every 5 (e.g. minute 0, 5, 10…)1-5— range, inclusive1-5/2— range with step (1, 3, 5)1,3,5— list of explicit valuesJAN,FEBorMON-FRI— named months and weekdays0 9 * * 1-5— 9:00 AM every weekday*/15 * * * *— every 15 minutes0 0 1 * *— first of every month at midnight
FAQ
What is Cron for?
When you have a cron expression and you need to know what it actually does, or you want to write one and need a sanity check. Type the expression, read the translation, scan the next five runs, paste it into your scheduler.
Which cron dialect does it support?
Standard five-field POSIX: minute, hour, day-of-month, month, day-of-week. Supports asterisks, step values (*/5), ranges (1-5), lists (1,3,5), and named months (JAN-DEC) and weekdays (SUN-SAT). It does not support non-standard extensions like L (last), W (weekday), # (nth weekday), or seconds.
How are day-of-month and day-of-week combined?
Standard cron rule: when both day-of-month and day-of-week are restricted (neither is *), the job runs when either matches. When only one is restricted, only that one is checked. This matches POSIX cron behavior.
What timezone are the next runs in?
Default is your browser's local timezone. You can switch to UTC with the toggle. The cron expression itself is timezone-neutral; the preview just shows you when those times land on your wall clock.
Why no L, W, or # support?
Those are Quartz or Jenkins extensions, not POSIX. They are useful but they would confuse a tester aimed at standard crontab. If you need them, the human-readable translation will tell you the syntax was rejected.
Does it track me or use cookies?
No. There are no ads, no analytics, no third-party scripts. Your expression stays in your browser, persisted to localStorage so it survives a page reload.