Build a five-field cron schedule and check upcoming dates in a time zone. This tool calculates schedules; it does not schedule or run jobs.
Choose a schedule and calculate to see the next ten dates and an explanation of each field.
Load a preset or enter five Unix fields. Edit individual fields with numbers, lists, ranges and steps.
Choose an IANA zone and an ISO date with an offset. Use now reads the current instant from your device.
Calculate up to ten dates, compare local time with UTC and review the field explanation before copying the expression.
This is a fixed example, not a forecast from today: the search excludes the starting instant and advances to the next fifteen-minute boundary.
*/15 * * * *
2026-01-01T00:15:00.000Z 2026-01-01T00:30:00.000Z 2026-01-01T00:45:00.000Z
If neither day field starts with *, they use OR: either may match. If either starts with *, including */n, both must match (AND). Minute, hour and month must always match.
Check impossible combinations, such as 31 February, and the five-year horizon. Do not add a seconds field.
A cron expression describes calendar matches. Presets cover common intervals and daily schedules, while individual fields let you adjust lists and ranges. Always inspect calculated dates before transferring an expression to another system.
The same expression yields different instants in different zones. The table separates local date, UTC offset and UTC instant so you can check seasonal changes. Your destination scheduler may apply a different daylight saving policy.
The tool requests ten matches within five years of the chosen starting instant. It does not run jobs, configure a server or send the expression to a remote service. Incomplete results are explicitly identified.
Only five Unix fields: minute, hour, day of month, month and day of week. A seconds field and Quartz syntax are unsupported.
UTC is the default. You may enter an IANA zone such as Europe/Madrid. The starting date must include Z or an explicit offset regardless of the schedule zone.
With cron-parser, daily 02:30 in Madrid becomes 03:30 on 29 March 2026. At the October transition only the first 02:30 is returned; the repeated occurrence is skipped. Check your scheduler’s policy.
If neither day field starts with *, they use OR: either may match. If either starts with *, including */n, both must match (AND). Minute, hour and month must always match.
No. It builds expressions and calculates dates in your browser. Copy the result to your chosen scheduler and configure the job there.
The search is limited to five years. There may be fewer than ten matches or none, for example for 31 February. Dates are never invented to fill the table.