01 / Generator
Describe a schedule or set each field. See when it really runs, then copy it for crontab, GitHub Actions, Kubernetes, AWS and more.
Common schedules
min · hour · day · month · weekday · type here to edit
Copy then gives you the full crontab line. Use absolute paths, because cron runs with a minimal PATH.
What this does
min
hour
day
month
weekday
Every day at 00:00
Hover a tile to see what each field means.
A day on this schedule
Next runs
Calculating…
Cron uses the server's time zone. Pick it above to see exactly when your job will fire.
Use it on your platform
# m h dom mon dow command
0 0 * * * /path/to/commandAdd with crontab -e. Times are in the server's local time zone unless you set CRON_TZ.
Quick reference
Popular cron expressions you can copy and use immediately. Click any expression to copy it to your clipboard.
Runs at minute 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55
Runs at the start of every hour
Runs once every day at 12:00 AM
Runs Monday through Friday at 9:00 AM
Runs at minute 0 and 30 of every hour
Runs once a week on Sunday at midnight
Runs at midnight on the first day of every month
Runs at minute 0, 15, 30, and 45 of every hour
A cron expression consists of five fields representing different time units: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-7). Special characters like asterisk (*), comma (,), hyphen (-), and slash (/) allow you to create flexible schedules.
The asterisk (*) means "every," so * * * * * runs every minute. The slash (/) specifies increments, like */5 for "every 5 units." Hyphens create ranges, and commas separate multiple values.
Why this tool
Type "every weekday at 9am" and get 0 9 * * 1-5. Or go the other way: paste an expression and read what it does.
See the actual next runs and a month calendar, in the server's time zone rather than yours. That's where most cron surprises come from.
Copy the same schedule as crontab, GitHub Actions, Kubernetes, AWS EventBridge, Quartz, systemd or node-cron syntax.
Keep schedules with their commands and notes, group them into projects, and import or export a crontab. No account needed.
Reading
Complete beginner-friendly guide to understanding and using cron jobs effectively.
Real-world cron job examples with detailed explanations for common use cases.
Master cron syntax: asterisk, slash, comma, and hyphen operators demystified.
Learn the cron syntax once and for all with this practical reference guide.
FAQ
Use the step operator in the minute field: */5 * * * *. It fires at :00, :05, :10 and so on, 12 times an hour. To limit it to working hours, set the hour field too: */5 9-17 * * *.
0 0 * * *: minute 0 of hour 0, every day. Remember it's midnight in the server's time zone, which on most cloud machines is UTC.
Put 1-5 (Monday to Friday) in the last field and pick a time, for example 0 9 * * 1-5 for 9:00 every weekday. Leaving the minute and hour as * would run it every minute of those days.
* * * * * mean?Every minute, of every hour, of every day. Each * means "any value" for its field (minute, hour, day of month, month, day of week). It's useful for testing, but rarely what you want in production.
If you set both the day-of-month and day-of-week fields, cron runs when either matches. 0 9 1 * 1 runs on the 1st of the month and every Monday. The decoder warns you about this.
Paste it into the decoder. It validates the syntax, explains it in plain English, and lists the next run times in whatever time zone your server uses.