Free Cron Generator Online

Build or paste a 5-field cron expression to see it in plain English, list the next 10 run times in your time zone or UTC, and catch mistakes. Free.

No login. Files processed for your request and discarded. Free to use. Files processed & discarded →

Compress PDF — it's free or choose from 130+ tools

130+ Free Tools
— Files Processed
— Happy Visitors
— Pages Explored
0 Files Stored

Cron Expression Generator and Explainer

Part of Text tools: See all Text tools.

What is Cron Generator?

Cron Expression Generator builds and explains standard 5-field cron schedules, the format used by crontab on Linux and macOS, Kubernetes CronJobs and GitHub Actions. Start from a preset such as every 15 minutes or weekdays at 09:00, or fill in the minute, hour, day of month, month and day of week fields yourself. You can also paste an expression you found in a server, a CI file or a colleague's code. The tool describes it in plain English, lists the next 10 times it will run in your time zone or in UTC, and tells you exactly what is wrong when a field is out of range or uses syntax that standard cron does not understand.

How to use Cron Generator

  1. Pick a preset, or type values into the five fields. Each field takes *, a number, a range (1-5), a list (1,15) or a step (*/10). Month and day of week also take names such as JAN or MON.
  2. Click Build expression. The expression appears in the box below and is checked straight away.
  3. To understand an existing schedule, paste it into the cron expression box. A full crontab line with the command after it works too; the command is ignored.
  4. Read the plain-English description and the next 10 run times. Switch Show run times in to UTC if the server or service runs on UTC.
  5. Click Copy expression and paste it into your crontab, CronJob or workflow file.

Why use this tool?

A cron mistake is easy to make and slow to notice: * 9 * * * runs 60 times between 09:00 and 09:59, not once, and 0 9 1 * 1 runs on the 1st of the month and on every Monday, not only on Mondays that fall on the 1st. Seeing the schedule in words and the actual next run dates catches these before the job goes live. The tool also flags expressions that never fire, such as 30 February, and Quartz or AWS syntax (?, L, W, #, a seconds field) that a normal crontab will reject.

Cron Generator — In-Depth Guide

A cron expression is five fields separated by spaces: minute, hour, day of month, month and day of week. A * means every value, so * * * * * runs every minute. A number fixes the value: 30 2 * * * runs at 02:30 every day. A range such as 1-5 covers several values, a list such as 0,30 picks specific ones, and a step such as */15 means every 15th value starting from the lowest, so */15 in the minute field gives :00, :15, :30 and :45. Steps work on ranges too: 9-17/2 in the hour field gives 09:00, 11:00, 13:00, 15:00 and 17:00.

The two most common mistakes are a * left in the minute field and the day-of-month and day-of-week rule. 0 9 * * * runs once a day at 09:00, while * 9 * * * runs every minute from 09:00 to 09:59. And when both day fields are set, cron treats them as either-or: 0 0 13 * 5 runs on every 13th and on every Friday, not only on Friday the 13th. The explanation and the list of next runs make both problems obvious before you deploy.

Where you paste the expression matters. In a crontab file the expression is followed by the command, and /etc/crontab also has a user name before the command; this tool reads only the first five fields. Kubernetes CronJobs take the expression in the schedule field and accept the @hourly style shortcuts. GitHub Actions takes it under on: schedule: - cron:, always runs in UTC and does not run more often than every 5 minutes, and scheduled runs can start late when GitHub is busy. Quartz, Spring and AWS EventBridge use a different, longer format, so convert an expression before moving it between systems.

Before you rely on a new job, check the time zone the server uses, look at the next few run times here, and make the command log its start time so you can confirm the first run. Jobs that run often should be safe to run twice and should not overlap: if a run can take longer than the gap between runs, use a lock (for example flock on Linux) so a slow run does not pile up behind the next one.

Frequently asked questions

What cron format does this tool use?
Standard 5-field cron: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or JAN-DEC) and day of week (0-7 or SUN-SAT, where 0 and 7 are both Sunday). It also understands the shortcuts @yearly, @annually, @monthly, @weekly, @daily, @midnight, @hourly and @reboot. This is the format of crontab on Linux and macOS, Kubernetes CronJobs and GitHub Actions schedules.
Does it support Quartz, Spring or AWS cron?
No. Quartz and Spring add a seconds field at the start, AWS EventBridge adds a year at the end, and all three use ?, L, W and # for things like the last day of the month or the second Monday. Standard crontab has no equivalent, so the tool tells you which part is not standard instead of guessing what you meant. To check a Quartz or AWS expression here, remove the extra field and change ? to *.
Why does my job run on more days than I expected?
When both day of month and day of week are restricted, standard cron runs the job when either one matches. 0 9 1 * 1 runs at 09:00 on the 1st of every month and on every Monday. If either field starts with *, both must match instead, so 0 9 */2 * 1 runs only on Mondays that fall on an odd-numbered date. The tool follows the same rule and shows a note when it applies.
Which time zone does cron use?
Crontab uses the server's local time zone unless you change it; some versions, such as cronie, accept a CRON_TZ= line. GitHub Actions schedules always run in UTC. Kubernetes CronJobs use the controller's time zone unless you set the timeZone field. Pick Your time or UTC above to see the next runs in the zone that matches where the job runs.
What happens around daylight saving time changes?
The preview skips a time that does not exist on the day the clocks go forward (for example 02:30 in New York in March). Real cron daemons differ: Vixie cron and cronie usually run such a job once, right after the change, and avoid running it twice when the clocks go back. If a job must run exactly once a day, schedule it outside 01:00 to 03:00 or run the server on UTC.
Why does the tool say my expression never runs?
Every field is valid on its own, but no real date matches them together, such as 0 9 30 2 * (30 February) or 0 0 31 4 * (31 April). The tool searches the next 28 years and reports it when nothing matches. Cron accepts these silently, so the job simply never starts.
Can I run the job on the last day of the month?
Not with standard cron syntax alone, because L is Quartz-only. A common workaround is to run it on days 28-31 and let the command check whether tomorrow is the 1st before doing any work.
Is anything uploaded?
No. Building, explaining and calculating run times all happen in your browser. Your expressions are not sent to our server.

Also try

Related tools that work well with this one: