How to use Cron Generator online, free

A cron expression is five fields separated by spaces: minute, hour, day of month, month, day of week. Once you know the order, most of the syntax follows - * means every value, */5 means every fifth, 1-5 means a range, and 1,15 means a list. What trips people up is the interaction between the two day fields. If you set both day of month and day of week to something other than *, most cron implementations treat them as OR rather than AND, so "15 * * 1" runs on the 15th of the month AND on every Monday, not on Mondays that happen to fall on the 15th. That surprises almost everyone the first time. The other frequent error is a missing leading zero or a wrong field count, both of which produce a schedule that runs far more often than intended - the classic being a job meant for daily that fires every minute. Building it visually avoids both. This runs in your browser.

You should not have to open an IDE to format a snippet from Slack, tidy a JSON blob, or check a hash. Paste it here, copy the result, move on.

Cron Generator is a good fit when scheduling a nightly backup, report or cleanup job.

Why this exists

Cron Generator is built around a few practical wins, not a long feature list:

• Builds the expression visually, avoiding the field-order and field-count mistakes that cause runaway jobs.
• Shows what the schedule actually means before you deploy it.
• Covers the standard five-field syntax used by crontab and most CI systems.
• Runs in your browser with no account.
• Faster than looking up the syntax every time you need a schedule.

Walkthrough

1. Pick your schedule in plain language. Choose the frequency and time rather than writing the fields by hand.
2. Read the generated expression. Five fields: minute, hour, day of month, month, day of week.
3. Check the plain-language description. Confirm it says what you meant. This is the step that catches an every-minute job intended as daily.
4. Add it to your scheduler. Linux crontab, a CI pipeline, or a cloud scheduler - note that some add a seconds field at the front.

Jobs it is built for

• Scheduling a nightly backup, report or cleanup job.
• Setting up a recurring CI pipeline run.
• Configuring a cloud scheduler or serverless cron trigger.
• Checking what an existing expression in a config file actually does.
• Building a weekday-only or monthly schedule without guessing the syntax.

Worth knowing before you start

• Read the plain-language description before deploying. A wrong field count is how a daily job ends up running every minute.
• Avoid setting both day-of-month and day-of-week. Most implementations OR them, which is rarely what anyone intends.
• Remember cron uses the server timezone, which is frequently UTC rather than your own - a job set for 9am may run at a very different local hour.
• Stagger jobs off the exact hour. Everything scheduled at 0 * * * * competes for the same resources across every system you run.
• Some cloud schedulers add a sixth field for seconds at the front. Check your platform before pasting a five-field expression.

What not to expect

• Getting the field order wrong, which silently produces a valid but completely different schedule.
• Setting both day fields and expecting AND behaviour, when cron treats them as OR.
• Forgetting the server runs in UTC, so a "9am" job fires at the wrong local time.
• Using */5 in the hour field expecting every five minutes - that is the minute field.
• Scheduling long jobs more frequently than they take to run, so overlapping instances pile up.

Privacy, in one paragraph

Cron Generator runs in your browser. The file or text you paste stays on your device. There is no account, and nothing is stored on a ToolBox server for this job.

Related tools worth opening next

If this is one step in a longer job, these usually come after it:

• UUID Generator - Generate unique UUIDs/GUIDs
• SQL Formatter - Format and beautify SQL queries
• API Tester - Send HTTP requests to any REST API and inspect the response - works with public endpoints and your localhost dev server

Short answers

What format does the generated cron expression follow?

Standard cron syntax (minute, hour, day of month, month, day of week) that's compatible with most systems using cron, including Linux crontab, many CI/CD pipelines, and cloud scheduler services.

Can I go the other way - paste an existing cron expression to understand what it does?

If the tool supports reverse-parsing, pasting an existing expression will show you a plain-language explanation of its schedule; otherwise, use the visual builder to reconstruct an equivalent schedule.

Do all systems use the same cron syntax?

The five-field core is near-universal, but some cloud schedulers and job frameworks add a sixth field for seconds at the front, and a few use different day-of-week numbering. Check your platform if a generated expression does not behave as expected.

What do the five fields mean?

In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12), day of week (0-6, Sunday is 0). An asterisk means every value, */n means every nth, a-b is a range and a,b is a list.

Why does my job run more often than expected?

Usually a field-order or field-count error - "0 2 * * *" is daily at 2am, while "* 2 * * *" runs every minute for an hour. Reading the plain-language description before deploying catches this immediately.

What timezone does cron use?

The server's, which on cloud infrastructure is very often UTC rather than your local zone. A job set for 9am can therefore fire at a completely different local hour, which is worth checking before relying on the timing.

Open the Cron Generator when you are ready. It is free, and you do not need an account.