Free Cron Expression Generator Online: Visual Builder + Explainer

A cron expression is a five-field string — minute, hour, day of month, month, day of week — that tells a scheduler exactly when to run a task. For example, 0 9 * * 1 means 9:00 AM every Monday. The syntax is compact but unforgiving: one wrong field and your backup runs at 9 PM instead of 9 AM, or every minute instead of every hour. This guide explains how cron expressions actually work, the traps everyone falls into, and how to generate and verify them free without signing up.

What is a cron expression, exactly?

Cron is the time-based job scheduler built into Unix-like systems since the 1970s, and its expression format has become the standard way to describe recurring schedules — in crontabs, CI pipelines, Kubernetes CronJobs, and cloud schedulers. A standard cron expression has five fields, separated by spaces, read left to right from the most frequent to the least frequent unit:

The four special characters do all the work: * means “every”, , lists values (1,15 = the 1st and 15th), - defines ranges (1-5 = Monday to Friday), and / sets a step (*/15 = every 15 units). So 30 2 * * 1-5 reads as: at 2:30 AM, every weekday. Once you can read that sentence, you can read any cron expression.

Generating an expression in four steps

1. Describe the schedule in words. Decide what you actually want: “every 15 minutes”, “weekdays at 9 AM”, “the 1st of each month at midnight”. Writing the sentence first prevents the classic mistake of building the expression backwards.
2. Build it visually. In the cron generator, set each field with the dropdowns — minutes, hours, days — and watch the expression assemble itself. No memorization required.
3. Read the explanation back. The explainer translates the expression into plain English (“At 09:00 on Monday”). If the English doesn't match the sentence from step 1, fix the fields.
4. Check the next run dates. The preview lists the upcoming fire times. This is where timezone surprises and the day-of-month trap (below) get caught — before anything runs in production.

Try it now with ToolsOfWeb's free cron expression generator — builder, explainer, and next-run preview in one page, no account, everything in your browser.

Common expressions cheat sheet

The schedules people actually search for, ready to copy. Verify each one in the explainer before using it — two minutes of checking beats a 3 AM incident.

The day-of-month vs day-of-week trap

This is the single most misunderstood part of cron, and it bites even experienced engineers. When both the day-of-month and day-of-week fields are restricted (neither is *), standard cron combines them with OR logic — the job runs when either field matches. So 0 0 1 * 1 does not mean “Mondays that fall on the 1st”. It means “the 1st of every month and every Monday” — roughly five times a month instead of once or twice a year. The behavior is documented in the crontab manual, but almost nobody reads it until after the incident.

If you genuinely need the intersection (only Mondays that are the 1st), cron cannot express it directly. The standard workaround is to schedule broadly —0 0 * * 1 — and add the date check inside the script itself. The generator's next-run preview makes the OR behavior visible immediately, which is exactly why you check the dates before saving.

Standard cron vs Quartz: know which one you're writing

Not every “cron expression” is the same format. Standard Unix/Vixie cron uses 5 fields starting with minutes. Quartz — used by Java schedulers, Spring, and several cloud platforms — uses 6 or 7 fields starting with seconds, and it requires a ? (“no specific value”) in either the day-of-month or day-of-week field. A Quartz expression like 0 0 9 ? * MON (seconds, minutes, hours, day-of-month=?, month, day-of-week) is not valid standard cron, and a 5-field expression pasted into a Quartz scheduler will be rejected or misread. Before copying an expression from a blog post or AI answer, check which format your platform expects — AWS EventBridge, Kubernetes CronJobs, and GitHub Actions each document their own variant.

Three gotchas worth knowing

The impossible date. 0 0 30 2 * looks like “February 30th” — a date that never exists. Cron silently never runs it, with no error and no log entry. Any day-of-month above 28 combined with February, or the 31st with a 30-day month, has the same problem. If a job mysteriously never fires, check the calendar first.

The timezone trap. Cron runs on the server's clock, and most servers run UTC. “9 AM” in your expression is 9 AM UTC — which is 2 AM in Los Angeles and 2 PM in Karachi. Convert your local time to the server timezone before writing the expression, and be explicit in comments or documentation about which timezone the schedule assumes.

The @reboot surprise. The @reboot shortcut runs a job once at system startup — handy for services, dangerous on machines that reboot often or unexpectedly. It also isn't available in every cron implementation, so a crontab that works on your laptop may fail on a minimal container image. Prefer an explicit schedule unless startup execution is truly what you want.

FAQs

For more free developer utilities, see ToolsOfWeb's Unix Timestamp Converter and UUID Generator.