Cron Expression Generator
Create cron schedules without guesswork. Edit the five fields (or pick a preset like “weekdays at 9:00”), read the schedule in plain English, and see the next eight run times in your time zone or UTC. Paste any existing expression to check and explain it.
Type or build an expression such as 0 9 * * 1-5. The generator validates each field (minute, hour, day of month, month, day of week — plus optional seconds), explains it in words, and computes upcoming runs following standard Vixie cron rules, including @daily-style shortcuts, names like MON and JAN, ranges, lists and steps.
“At 09:00, Monday through Friday”
Minute
0–59
Hour
0–23
Day of month
1–31
Month
1–12
Day of week
0–6 (Sun=0)
Common schedules
Next runs
Servers usually run cron in UTC — check your server or scheduler's time zone.
Syntax
* — every value
, — list: 1,15
- — range: 1-5
/ — step: */10 = every 10
@daily, @hourly… — shortcuts
6 fields — first field is seconds (node-cron, Spring)
When both day-of-month and day-of-week are set, standard cron runs when either matches. Quartz (Java) expressions use ? and 6–7 fields and aren't supported here.
Zero Server Uploads
Files process in local RAM
Instant WASM Speed
No waiting queues or lags
Unlimited Batching
Convert files without limits
Suggest a Feature or Improvement for Cron Expression Generator
Need custom options, higher limits, or extra format support? Let our engineering team know!
How to use Cron Expression Generator
- 1Enter an expression, or pick a common schedule.
- 2Adjust individual fields.
- 3Read the plain-English description.
- 4Check the next run times, then copy the expression.
Cron syntax
Five fields: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC) and day of week (0–7, where 0 and 7 are Sunday, or SUN–SAT). * means every value, a,b a list, a-b a range, and */n every n. Some schedulers (node-cron, Spring) add a leading seconds field.
A classic gotcha: if both day-of-month and day-of-week are set, cron runs when either matches — “0 0 13 * 5” runs on every 13th and every Friday.
Time zones
Cron runs in the server's time zone — often UTC on cloud servers, GitHub Actions and Kubernetes. Check the UTC view before deploying, and remember daylight-saving changes can skip or repeat runs in local time. Test timestamps with the JWT Expiration Checker's converter.
Frequently Asked Questions
Does it support Quartz cron (? and L)?
No — it targets standard Unix/Linux cron, which is what crontab, GitHub Actions, Kubernetes CronJobs and most cloud schedulers use. Quartz syntax is detected and reported.
What does */5 * * * * mean?
Every 5 minutes, at :00, :05, :10 and so on.
Is my code or data uploaded?
No. Everything runs in your browser; nothing you paste is sent to a server or stored.