Cron builder, explainer, next-run preview and platform checker
Build and inspect cron expressions with five-field Unix syntax or optional seconds, expand each field, preview upcoming run times, load common schedules, compare platform expectations and catch mistakes before adding jobs to servers, containers, uptime monitors or automation tools.
Preview uses browser date math and displays the selected timezone. Production cron still runs in the scheduler timezone configured on your server or platform.
Cron expressions are small strings with large consequences
A cron expression can start backups, reports, cleanup jobs, queues, monitors and deployment tasks. Because the syntax is compact, mistakes are easy to miss: the server timezone may not be the timezone you had in mind, day-of-month and day-of-week behavior can differ, and some platforms add a seconds field while classic Unix cron does not. A schedule that looks harmless can run hundreds of times more often than expected.
This cron expression generator is built for operational review. It expands each field, explains the schedule in plain English, previews upcoming run times, flags platform-specific syntax, supports standard five-field cron and six-field schedules with seconds, and shows common warnings before the expression is copied into a server, Docker container, Kubernetes job, GitHub workflow, uptime monitor or automation platform.
How to read a cron schedule
Read cron from left to right: minute, hour, day of month, month and day of week. In six-field systems, seconds come first. A star means every allowed value, a comma means several values, a dash means a range, and a slash means a step. The hard part is not memorizing those symbols; it is matching the expression to the platform that will actually run it.
- Five-field cron is the common Unix shape: minute hour day month weekday.
- Six-field cron usually adds seconds before minutes.
- Quartz syntax may use tokens such as
?,L,Wor#. - Timezone belongs to the scheduler, not the expression itself in most systems.
- Next run preview is the safest way to catch obvious schedule mistakes.
Common cron debugging examples
If a job runs at the wrong hour, check the scheduler timezone before editing the expression. If a task runs too often, inspect step fields such as */5. If a platform rejects an expression, confirm whether it expects five fields, six fields or Quartz syntax. If both day-of-month and day-of-week are restricted, check whether your scheduler uses OR behavior or strict AND behavior.
Common questions
Does every cron system support seconds?
No. Classic Unix cron uses five fields. Some schedulers add seconds, and Quartz-style systems can add more syntax.
What timezone does cron use?
Usually the server or scheduler timezone. Some hosted platforms let you configure it separately.
Can this preview replace production testing?
No. It catches common mistakes, but the final source of truth is the scheduler that will run the job.
What do the five cron fields mean?
In order: minute, hour, day of month, month, and day of week. An asterisk in a field means every value for that field.
What is the difference between */5 and 5 in a cron field?
*/5 means every five units, such as minutes 0, 5, 10 and so on. A plain 5 means exactly at value 5.
How do I run a job every day at midnight?
Use 0 0 * * *. The tool builds and explains any schedule and previews the next run times so you can confirm it.
