Ink·tab
all tools

Parse expression · preview next runs

Turn a cron line into plain English and see when it will actually fire next.

In plain English

At minute(s) 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55 of hour(s) every hour

Next runs
  • 0104/25/2026, 12:452026-04-25T12:45:00.000Z
  • 0204/25/2026, 12:502026-04-25T12:50:00.000Z
  • 0304/25/2026, 12:552026-04-25T12:55:00.000Z
  • 0404/25/2026, 13:002026-04-25T13:00:00.000Z
  • 0504/25/2026, 13:052026-04-25T13:05:00.000Z
  • 0604/25/2026, 13:102026-04-25T13:10:00.000Z
  • 0704/25/2026, 13:152026-04-25T13:15:00.000Z
  • 0804/25/2026, 13:202026-04-25T13:20:00.000Z
Common presets

Everything happens in your browser. Nothing is uploaded.

When to use it

Sanity-checking the 0 9 * * 1-5 in a GitHub Actions schedule, a Kubernetes CronJob, Airflow, or system crontab — before the thing actually runs at the wrong time.

How it works

Enter the expression at the top. A plain-English description appears, followed by a list of upcoming runs in your local time zone. The preset buttons below load common expressions.

Field rules

Five fields, in order: minute hour day-of-month month day-of-week.

  • * — every value
  • A-B — range (9-17)
  • */N or A-B/N — step (*/15, 9-17/2)
  • a,b,c — list (0,15,30,45)
  • Months accept JAN..DEC, weekdays accept SUN..SAT

If both day-of-month and day-of-week are specific (not *), they match with OR — the traditional crontab rule. So 0 0 1 * 1 fires on the 1st of every month or every Monday.

Limitations

Standard five-field cron only. Quartz/extension syntax (@reboot, seconds as a sixth field, L, W, #n) is not supported.

Where does your input go?

Cron parsing and next-run calculation happen in your browser. Your expression is never uploaded or stored. Close the tab and it's gone.