Check a Weekday Cron Schedule and the Server Time Zone
Start with the task you actually need to finish
- Scheduling a nightly database backup on a Linux server.
- Setting a Kubernetes CronJob or GitHub Actions schedule.
- Running reports every Monday morning.
A practical check before you begin
The five-field schedule 0 9 * * 1-5 means 09:00 weekdays in the scheduler’s zone. Browser previews can show local time instead. Check the server’s zone and implementation before using the expression for a backup or business task.
Follow the workflow and review the result
- Type or paste a cron expression, or click a preset.
- Adjust minute, hour, day, month or weekday in the five boxes.
- Read the plain-English description to confirm the schedule.
- Check the next 5 run times in your local time.
- Copy the expression into your crontab or CI config.
Cron syntax cheat sheet
Fields: minute (0–59) · hour (0–23) · day of month (1–31) · month (1–12 or JAN–DEC) · day of week (0–6 or SUN–SAT, 7 also means Sunday). Symbols: * any value · , list · - range · / step. Examples: */5 * * * * every 5 minutes · 0 0 * * * daily at midnight · 30 2 * * 0 Sundays at 02:30 · 0 0 1 * * monthly.
Time zones
Cron runs in the time zone of the server or service. Most cloud schedulers, GitHub Actions and many containers use UTC. The next run times here use your device's local time, so convert if your server uses UTC.
5 fields vs 6 fields
Standard Unix cron uses 5 fields. Some tools such as Quartz or Spring add a seconds field at the start, and AWS adds a year field. This tool checks the standard 5-field format used by crontab, Kubernetes and most CI services.
Limits worth knowing before you rely on the output
This utility does not install or run jobs. Vendor extensions and seconds-based formats differ from standard five-field cron.