Skip to content

Cron Expression Tool

Explain a cron expression in plain English, see its next 10 run times in any time zone, or build one. crontab, Azure Functions and Quartz formats.

Cron expressions schedule jobs with five fields: minute, hour, day of month, month and day of week. Some schedulers add a seconds field at the front (Azure Functions, Hangfire, Spring) or a year at the end, and Quartz numbers the days 1 to 7 starting on Sunday where crontab uses 0 to 6. That's how a job meant for Monday ends up running on Sunday. Paste an expression to read it in plain English and see exactly when it will run next, including what happens on the nights clocks change.

Cron expression
Examples: */15 * * * *, 0 9 * * 1-5, 0 0 12 ? * MON-FRI (Quartz), @daily
Format
Show run times in

Build an expression

Run
Hour (0–23)
Minute
0 9 * * 1-5

At 09:00, Monday through Friday

crontab format: minute hour day-of-month month day-of-week (0 or 7 = Sunday)

MinuteHourDay of monthMonthDay of week
09**1-5

Next 10 runs (UTC)

Local timeUTCFrom now
Tue 2026-10-27 09:00:00 UTC+00:00 2026-10-27 09:00:00 in 15 hours
Wed 2026-10-28 09:00:00 UTC+00:00 2026-10-28 09:00:00 in 39 hours
Thu 2026-10-29 09:00:00 UTC+00:00 2026-10-29 09:00:00 in 2 days
Fri 2026-10-30 09:00:00 UTC+00:00 2026-10-30 09:00:00 in 3 days
Mon 2026-11-02 09:00:00 UTC+00:00 2026-11-02 09:00:00 in 6 days
Tue 2026-11-03 09:00:00 UTC+00:00 2026-11-03 09:00:00 in 7 days
Wed 2026-11-04 09:00:00 UTC+00:00 2026-11-04 09:00:00 in 8 days
Thu 2026-11-05 09:00:00 UTC+00:00 2026-11-05 09:00:00 in 9 days
Fri 2026-11-06 09:00:00 UTC+00:00 2026-11-06 09:00:00 in 10 days
Mon 2026-11-09 09:00:00 UTC+00:00 2026-11-09 09:00:00 in 13 days
Daylight saving: a fixed time that doesn't exist (spring forward) runs at the next valid time; one that happens twice (fall back) runs once. Interval schedules like */15 keep running every interval through both hours. Linux cron uses the server's time zone unless CRON_TZ is set; Kubernetes CronJobs use UTC unless .spec.timeZone is set.