Cron / NCRONTAB Visualizer
Paste a cron or Azure Functions NCRONTAB expression and see the next runs in your timezone, plus a plain-English description.
✓ runs 100% in your browser — no data leaves this page
Accepts classic 5-field cron and Azure Functions 6-field NCRONTAB (leading seconds).
Examples: 0 30 7 * * MON-FRI (Functions, weekdays 07:30) · */10 * * * * (every 10 min).
Times shown in your local timezone (UTC) — Azure Functions default to UTC unless WEBSITE_TIME_ZONE is set.
Runs daily at a fixed time, on selected weekdays (6-field NCRONTAB with seconds — Azure Functions format)
Next 10 runs
- Mon 2026-09-21 07:30:00 (in 33.2 h)
- Tue 2026-09-22 07:30:00 (in 2.4 days)
- Wed 2026-09-23 07:30:00 (in 3.4 days)
- Thu 2026-09-24 07:30:00 (in 4.4 days)
- Fri 2026-09-25 07:30:00 (in 5.4 days)
- Mon 2026-09-28 07:30:00 (in 8.4 days)
- Tue 2026-09-29 07:30:00 (in 9.4 days)
- Wed 2026-09-30 07:30:00 (in 10.4 days)
- Thu 2026-10-01 07:30:00 (in 11.4 days)
- Fri 2026-10-02 07:30:00 (in 12.4 days)
Frequently asked
How is NCRONTAB different from normal cron?
Azure Functions timer triggers use six fields — {second} {minute} {hour} {day} {month} {day-of-week} — where classic cron has five. `0 */5 * * * *` is every five minutes in NCRONTAB; the classic equivalent is `*/5 * * * *`. Functions accepts both forms and so does this visualizer — it detects the field count — but mixing them up in your head is how `*/5 * * * * *` (every five seconds) ends up in production.
NCRONTAB for every minute between 6am and midnight?
`0 * 6-23 * * *` — second 0, every minute, hours 6 through 23. The hour field is inclusive at both ends, so this runs from 06:00 until 23:59 and skips 00:00–05:59. For weekdays only add the day-of-week: `0 * 6-23 * * 1-5`.
Every 5 minutes during business hours, weekdays only?
`0 */5 8-17 * * 1-5` runs at :00, :05 … :55 from 08:00 to 17:55 Monday to Friday. Note the last run is 17:55, not 18:00 — if you need an 18:00 run either use 8-18 (which adds 18:05–18:55 too) or schedule a second trigger.
Which timezone does an Azure Functions timer use?
UTC by default. On Windows plans set the WEBSITE_TIME_ZONE app setting (e.g. W. Europe Standard Time) and on Linux Dedicated or Premium plans set TZ (e.g. Europe/Copenhagen); neither is supported on Linux Consumption or Flex Consumption, where you must express the schedule in UTC and handle daylight saving yourself. This visualizer shows next runs in the timezone you pick so you can check the conversion.