
Cron expression builder
Build or paste a cron schedule, read it in English, and preview the next runs in your timezone. Runs in your browser. Nothing is sent.
- Free
- No signup
- Nothing stored
The fields below stay in sync with this expression.
Minute: */5
Every 5 minutes
Next runs
| UTC | UTC | Relative |
|---|---|---|
| 16 Oct 2026, 10:25 | 16 Oct 2026, 10:25 | in under a minute |
| 16 Oct 2026, 10:30 | 16 Oct 2026, 10:30 | in 6 min |
| 16 Oct 2026, 10:35 | 16 Oct 2026, 10:35 | in 11 min |
| 16 Oct 2026, 10:40 | 16 Oct 2026, 10:40 | in 16 min |
| 16 Oct 2026, 10:45 | 16 Oct 2026, 10:45 | in 21 min |
| 16 Oct 2026, 10:50 | 16 Oct 2026, 10:50 | in 26 min |
| 16 Oct 2026, 10:55 | 16 Oct 2026, 10:55 | in 31 min |
| 16 Oct 2026, 11:00 | 16 Oct 2026, 11:00 | in 36 min |
| 16 Oct 2026, 11:05 | 16 Oct 2026, 11:05 | in 41 min |
| 16 Oct 2026, 11:10 | 16 Oct 2026, 11:10 | in 46 min |
Fields
| Field | Value | Meaning |
|---|---|---|
| Minute | */5 | Every 5 |
| Hour | * | Every value |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | * | Every value |
Schedule snippets
Lines wrap inside one scrolling area. Line numbers stay with each line.
How it works
- 01
Pick a preset or build fields
Start from a preset or set minute, hour, day, month, and weekday. The expression stays in sync with the fields.
- 02
Read the English and check the next runs
The sentence and the next 10 times use the timezone you pick. Compare them with UTC before you deploy.
- 03
Copy for crontab, GitHub Actions, Vercel, or Kubernetes
Each snippet is ready to paste. GitHub Actions and Vercel Cron stay on UTC.
What the five fields mean
A standard expression is minute, hour, day of month, month, then day of week. */5 * * * * fires every five minutes. When both the day of month and the day of week are restricted, standard cron runs the job if either field matches.
GitHub Actions and Vercel Cron evaluate the expression in UTC, so 09:00 in the builder is not 09:00 on those hosts unless the timezone is UTC. Quartz adds seconds and the ?, L, W, and # tokens. The Next.js Dockerfile guide is the closest deploy write-up if the schedule ships with the app.