$ loading▍
$ loading▍
Type a cron expression or build it field by field. See what it means in plain English and exactly when it runs next, in your time zone or UTC.
Cron expression
In plain English
At 09:00, Monday through Friday
Presets
* any · 1-5 range · */15 every 15 · 1,15 list · JAN–DEC · SUN–SAT · @hourly @daily @weekly @monthly @yearly
Copy as
0 9 * * 1-5 /path/to/command
on:
schedule:
- cron: "0 9 * * 1-5"Next runs
local time
“*/15 9-17 * * 1-5” reads as “Every 15 minutes, between 09:00 and 17:59, Monday through Friday”.
See the next ten times it will fire, in your local time or UTC, so there are no surprises after deploy.
Copy it as a crontab line or a GitHub Actions schedule, or run the job on your own server with CID.
// faq
In order: minute (0–59), hour (0–23), day of the month (1–31), month (1–12 or JAN–DEC) and day of the week (0–7 or SUN–SAT, where both 0 and 7 are Sunday). An asterisk means “every”.
1-5 is a range (1 through 5), */15 is a step (every 15th value starting at the lowest), 10-50/10 steps within a range, and 1,15,30 is a list. They can be combined, like 0,30 9-17 * * MON-FRI.
Standard cron runs when either matches. 0 0 1 * MON runs on the 1st of every month and on every Monday, not only on Mondays that fall on the 1st.
The server's local time zone for classic crontab, and always UTC for GitHub Actions and most cloud schedulers. Switch the next-runs list to UTC to see exactly when those will fire.
It covers the standard 5-field format used by crontab, GitHub Actions, Kubernetes CronJobs and CID. Quartz and some libraries add a seconds field; drop it to use those expressions here.
Looking for something bigger? The products are full apps: an encrypted password vault, self-hosted CI/CD, and more.